Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

On Friday at the end of the day we updated our in-house servers to run the newer McAfee SaaS Endpoint Protection Suite, which involved restarting the servers. This morning (Monday) our Windows XP machines cannot access printers shared from those servers. They can still log on (the server with the printer in question is also the Active Directory server) and access file shares. I haven't been able to find any relevant entries in the Event Viewer on the server.

The server is Windows Server 2003. The printer is an HP LaserJet M2727nf. The error text in Windows is

"Windows cannot connect to the printer. Either the printer name was typed incorrectly, or the specified printer has lost its connection to the network."

The message comes up when logon scripts run, and when I try to open the printer from the Printers and Faxes area of Control Panel. Windows 7 computers seem to be fine. I don't see any errors in the Network Summary page from the printer.

The firewall installed by McAfee is not a factor. Is there anything else it could have changed to affect printer sharing to Windows XP only? I'm also not 100% sure it's the McAfee installation that's causing the problem, but it's the most significant change that's happened since the last time printing worked.

UPDATE 2/22/2011: I tried updating the HP drivers on the XP machines. The executable "installer" for the new drivers did not actually install anything, it just extracted files to an unspecified location. As per the instructions I removed the printer and re-added it. This seemed to solve the problem, but this morning when users logged on, the problem came back.

share|improve this question
1  
@Moab - in this case, that's a bad idea. You can't install security essentials on Windows Server. –  Joel Coehoorn Feb 21 '11 at 22:08
1  
@ Joel, yup, but I stick with the McAfee comment, junk software. –  Moab Feb 21 '11 at 23:01

1 Answer 1

up vote 0 down vote accepted

Solved it. The server in question had two Ethernet ports, and one was disabled. Enabling it stopped the errors. We're not sure how that worked, but it did.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.