Hello everyone, I have a shared printer connected to a Linux box (I know this is a Windows support forum but, please, bear with me) and this printer is accessible from any computer on the network but one. I am 100% sure that everything is set up properly on the print server because all WinXP (x32 and x64), Win2000 and WinVista machines can print to it (considering WinVista, I have tested x32 only, since no x64 Vista box is present in the network). Any Linux box can print to this printer as well with no problems at all. However, there is an x64 Win7 machine that can add the printer and send it a print job, but then it starts complaining about not being able to connect to the printer and/or that there is no queuing service running (I am sorry if my translation to English isn't exactly what this service is called originally). I tried to add the printer in a variety of ways: Browse to the server through network neighbourhood, double-click it and follow the Add printer wizard. Add printer using the wizard by selecting it in the list of available network printers. Add printer manually using the wizard by typing printer's address "\\server_name\printer_name". Add printer manually using the wizard by typing printer's address "\\server_ip\printer_name". Add printer manually using the wizard by typing printer's address "http://server_name:631/printers/printer_name". Add printer manually using the wizard by typing printer's address "http://server_ip:631/printers/printer_name". Add LOCAL printer and create a new LOCAL port "\\server_name\printer_name" (or "\\server_ip\printer_name") -- it usually works, but not this time. :( All of the above methods led to the printer being added successfully, but any job sent there caused the printer to be inaccessible. Considering the Windows driver, I have always been using the WHQL one available therein (no matter the actual Windows edition that I've been printing from). What puzzles me is that the printer is accessible to such a large number (30+) of different machines running different OSs, while an x64 Win7 machine gets confused when I ask it to communicate with the printer. It seems to me that there must be something wrong with the Win7 machine, because otherwise there would be problems arising elsewhere as well. Firewall is out of the question, since printing to other shared network printers works fine (I did manually check the spool server permissions in firewall's settings as well). I have even tried to enable the LPR print monitor and LPD print service in Programs and Features -> Turn Windows features on or off -> Print and Document Services. Nothing good came out of that either... :( So, is there anything else I could try? Any help would be much appreciated. nvx

nvx wrote: Hello everyone, I have a shared printer connected to a Linux box (I know this is a Windows support forum but, please, bear with me) and this printer is accessible from any computer on the network but one. I am 100% sure that everything is set up properly on the print server because all WinXP (x32 and x64), Win2000 and WinVista machines can print to it (considering WinVista, I have tested x32 only, since no x64 Vista box is present in the network). Any Linux box can print to this printer as well with no problems at all. However, there is an x64 Win7 machine that can add the printer and send it a print job, but then it starts complaining about not being able to connect to the printer and/or that there is no queuing service running (I am sorry if my translation to English isn't exactly what this service is called originally). I tried to add the printer in a variety of ways:   1. Browse to the server through network neighbourhood, double-click it and follow the Add printer wizard. 2. Add printer using the wizard by selecting it in the list of available network printers. 3. Add printer manually using the wizard by typing printer's address "\\server_name\printer_name". 4. Add printer manually using the wizard by typing printer's address "\\server_ip\printer_name". 5. Add printer manually using the wizard by typing printer's address "http://server_name:631/printers/printer_name". 6. Add printer manually using the wizard by typing printer's address "http://server_ip:631/printers/printer_name". 7. Add LOCAL printer and create a new LOCAL port "\\server_name\printer_name" (or "\\server_ip\printer_name") -- it usually works, but not this time. :(   All of the above methods led to the printer being added successfully, but any job sent there caused the printer to be inaccessible. Considering the Windows driver, I have always been using the WHQL one available therein (no matter the actual Windows edition that I've been printing from). What puzzles me is that the printer is accessible to such a large number (30+) of different machines running different OSs, while an x64 Win7 machine gets confused when I ask it to communicate with the printer. It seems to me that there must be something wrong with the Win7 machine, because otherwise there would be problems arising elsewhere as well. Firewall is out of the question, since printing to other shared network printers works fine (I did manually check the spool server permissions in firewall's settings as well). I have even tried to enable the LPR print monitor and LPD print service in Programs and Features -> Turn Windows features on or off -> Print and Document Services. Nothing good came out of that either... :( So, is there anything else I could try? Any help would be much appreciated. nvx Have you tried to use net use from the command line? There you can specify a username and password to use to connect. This helps in many cases as Win7 has problems printing as guest without authentication. Wolfgang

Dear Wolfgang, Thank you for your response -- I will check the documentation. In any case, I'll post the result here as soon as I test it. nvx

I am afraid that even NET USE is of no help to me. I tried to add the printer without user and password information and with it (in both cases it was added successfully but did not print). I also tried to redirect (currently unused) LPT2 to \\server\printer with no luck -- printer set up manually with connection to LPT2 behaved the same as those set up before using one of the previously mentioned methods (no activity of the printer upon sending a print job + subsequent inaccessibility). Sigh. A clean install of Win was performed last week on this computer so the OS should be fine. Any other tips, anyone? nvx

I am afraid that even NET USE is of no help to me. I tried to add the printer without user and password information and with it (in both cases it was added successfully but did not print). I also tried to redirect (currently unused) LPT2 to \\server\printer with no luck -- printer set up manually with connection to LPT2 behaved the same as those set up before using one of the previously mentioned methods (no activity of the printer upon sending a print job + subsequent insaccessibility). Sigh. A clean install of Win was performed last week on this computer so the OS should be fine. Any other tips, anyone? nvx

Dear Alex, Thank you for the suggestion. This morning (sorry, I had not time to post the info sooner) I tried to connect to the printer with my 32-bit Windows 7 laptop. Nevertheless, it was not possible to print anything (the problem was not caused by the firewall). I am pretty sure it is something in Windows 7 that causes the trouble. If not, how come any non-Win7 computer can print without the slightest problem? Could it be that Win7 applies some kind of a strict network policy when PCs are in a domain? This seems to be the only difference between our work setup and what I have at home - no domain, just a simple workgroup with a Linux print server and Windows (XP x32, XP x64, Vista x32, Win7 x32, Win7 x64) and Linux computers. nvx

Hi, I notice that your printer server is Linux, based on my research, you need install 64-bit driver on printer server for your 64-bit version of Windows 7, regarding how to achieve this, it is recommended to query this problem in the Linux forum, here as a reference, I would like to share a link about Windows printer server with you: Update and Manage Printer Drivers Hope it helps. Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Currently, I suggest you change the NTLM authentication level in Windows 7 to check how it works: Network security: LAN Manager authentication level Please change the NTLM authentication level to “Send LM & NTLM - use NTLMv2 session security if negotiated”. Alex ZhaoPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Dear Alex, Thanks for your reply. I am afraid that changing authentication level is not the solution to my problem. :( After a careful examination of one of the log files on the print server I have noticed a few unexpected differences between entries produced by sending a print job from WinXP x64 and Win7 x64. These point to a possible driver problem, although I wonder why an auxiliary Win x64 driver on a Linux print server should be different for XP and 7. I guess it's time to read CUPS documentation thoroughly... ;) Thanks again for your help. nvx

So, I finally got it working. It seems that there is a bug in the 64-bit Win7 version of the driver provided by Windows Update, since every time I tried to print anything the spooler crashed. After a bit of searching I stumbled upon this (http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/cannot-print-under-64bit-versions-of-vista-or/865c9e95-64dd-4f32-8aec-1c5f80ab8ad3) thread and from that moment on it was just a matter of finding my x64 Win2003Server installation medium. With drivers taken from there it works just fine. :) After replacing also the x32 version of the driver on the server even print jobs sent from x32 Win7 get printed correctly. nvx