Printers keep changing ports in a terminal server environment

We have an SBS 2003 domain with a Windows 2003 Server used as a terminal server.  One particular account connects to the terminal server and is having a bizarre printing problem.

She has an HP laserjet printer  (ts004 - Raleigh HP Printer) and a kyocera (ts009 - Raleigh Kyocera.)  setup for printing on the remote server.  However whenever she disconnects from the the terminal server, the printers hop to a different port.  

For example, after logging out and logging back on, the port will still be checked beside ts004 but the printer will be set to inactive port and the raleigh hp printer will now be located beside ts003.  The same thing will happen to the kyocera.

1.  Does anyone know why the printers would hop ports on the terminal server after logging out and logging back in?

2.  Is there any afforable printing software for terminal servers thats more reliable and more elegant to use.

TIA
 
southrayAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

cedarghostCommented:
Try mapping the printers to the user using the net command.
Example:   net use lpt#  \\servername\printername  /persistent:yes
0
southrayAuthor Commented:
We are not getting the net use command to work.

The printer name is shophp.  The share name is hplaserj.  The server is S.   The domain is domain.local and the workstation is moncure.  We are trying to make the printer be persistent on ts0004.

When we type the command: net use  ts0004 \\s1\shophp, it responds "Network name cannot be found."  If we use the share name it gives us the same message.

What are we doing wrong?

Thanks
0
southrayAuthor Commented:
We got it!
It seems Windows will automatically map the printers but because the drivers on the local machine and the drivers on the server were not exactly the same it wouldn't re-map after logging off and back on.

The printer was a HP Laserjet 3390 and drivers for XP were readily available, but the only drivers available for 2003 were "HP Universal Printing" so I changed the drivers on the local machine and it works.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.