NT Logon Kills Network Printer

Kenn's
Tech
Notes

19980104: NT Logon Kills Network Printer

January/1998
Tech Note #4

Keith B found this interesting "feature" of Windows NT. He was working in a lab where the student workstations could not print to the network printer (connected to the NT Server), so long as a user was logged on locally on the server. If he went to the server, and simply logged off (not shut down, obviously), all the print jobs would then print.

If he logged on to the server, opened Print Manager there, and then sent one print job from a workstation, he would see that print job appear, followed immediately by a host of additional "Remote Print Job" entries. These entries would fill the screen of Print Manager over and over, in fact, endlessly. Until he logged off. At which time, the single print job would print.

What Keith discovered was that LPT1 had been mapped to the network share of the printer which actually was connected to LPT1. Network connections such as this are stored in user profiles, so when he logged off, that connection was severed. When logged on, though, any print job that was received for LPT1 was immediately remapped to the network connection, which would then be received again as a print job for LPT1 and be immediately remapped to the network connection, and that would again be received again, etc. etc. This is an endless loop, and that's what was filling up the Print Manager screen.

What Keith had to do was remove the network connection. Normally, you can do this in Print Manager but, for some reason, the connection did not show. Fortunately, he discovered that by removing the printer, and logging off and then on again, he was given the chance to remove the connection. At the logon screen, a dialog box came up informing him "Unable to connect to \\server\printer", with the choice whether or not to try to reconnect in the future. He clicked on NO, recreated the printer, and it worked fine ever since. (Note: He had to do that with all users. That is, delete the printer, then log off and then log on as each different user that ever logs on locally to the server. The network connection is stored for each individual user. Therefore, it must be removed for each individual user.)

Please see the next tech note for a related issue.


DISCLAIMER: This document is intended for the reference of computer support personnel within Winnipeg School Division No. 1. There is no warranty or liability if procedures recommended here have an adverse affect on any systems. Use them at your own risk. Any trademarks mentioned are the property of their owners, none of whom have certified any information provided here. Opinions expressed here are personal only and do not represent the policy of Winnipeg School Division No. 1 or any other organization anywhere.


Got a Tech Note to share? Submissions are most welcome! [Click here.]

To return to the Tech Notes home page, click here.

To download a copy of all the January/1998 Tech Notes in Rich Text Format, click here.
Click here to visit the Information "Super-Cul-De-Sac". This page was updated
2001 June 9


This page hosted by
Get your own Free Homepage
Check out my neighbours here in Silicon Valley Peaks by clicking here.