Disappearing printer port mappings

[ShackDaddy]

I've been creating local printers on my Windows2003 TS for several remote users. I have them log on, I add the printer, I set up the driver and I point it to the appropriate TS## port. The printer will then work properly for months. Until the server is rebooted. Once the server is rebooted, the printer I created is nowhere to be found and I have to create it again.

I'm also having this problem on a server that is not primarily a terminal server, but is running the same OS. I create six new printers mapped to TCP/IP ports, they work fine until the server is rebooted, and then the TCP/IP ports that I created are completely gone and the printers are "offline" until I recreate those ports.

Anyone know why reboots are clearing this sort of information from the server?

ShackDaddy

 

[djtech2k]

Try the con2prt.exe. It is a utility that you can put in a login script to reinstall the printer on the network on each login.

-DJ

 

[ShackDaddy]

Thanks, djtech, but con2prt is only good for mapping network printers, things that require UNC paths. I'm dealing with local ports in both of the described scenarios:

TS ports
TCP/IP ports

Both get installed by choosing "Install local printer" when setting them up.

The problems I described shouldn't be happening at all, and don't happen on my other servers. There has to be some sort of fix out there or known cause.

 

[djtech2k]

Iunderstand that it shouldnt be happening, but if you need an immediate fix, these utils may work. Besides, thats why most of us have jobs

Anyway, if its local printer management that you want, here is something that may help instead of con2prt, it is prnmngr.exe

http://www.ss64.com/nt/prnmngr.html.

That may work for you.

BTW, is this problem happening on a 2000 Terminal Server? If so, printing issues are well-known with it.

-DJ