Losing All Network Printers In Windows 2000 TS

[Dan]

I am running Windows 2000 Terminal Services. When i login
to the terminal server from 2 specific workstations and
try to print from the Terminal Server ALL THE NETWORK
PRINTERS ON THE SERVER DISSAPPEAR FOR ALL USERS AND I
HAVE TO REBOOT THE SERVER TO GET THEM BACK, now all other
workstations work fine and we can't seem to find anything
on this issue but heres another kicker if i use either
one of the 2 Terminal Server desktop logins from any
other desktop computer in the company printing works
fine. Its almost like the combination of the 2 specific
workstations and Terminal Server Desktop logins cause the
issue. I can even Login from the workstation with my
administrator login and the printing is fine.....HELP
PLEASE

 

[Guest]

Do you happen to have non-Microsoft print drivers loaded on your TS, i.e. ones you added to support new printers that aren't supported by built-in drivers that shipped with Windows 2000 Server

If so this could be your problem, as 3rd party print drivers are known to cause instability and even BSOD on a Terminal Server

Printing FAQ here
http://www.workthin.com/tsp.ht

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Dan wrote: ----

I am running Windows 2000 Terminal Services. When i login
to the terminal server from 2 specific workstations and
try to print from the Terminal Server ALL THE NETWORK
PRINTERS ON THE SERVER DISSAPPEAR FOR ALL USERS AND I
HAVE TO REBOOT THE SERVER TO GET THEM BACK, now all other
workstations work fine and we can't seem to find anything
on this issue but heres another kicker if i use either
one of the 2 Terminal Server desktop logins from any
other desktop computer in the company printing works
fine. Its almost like the combination of the 2 specific
workstations and Terminal Server Desktop logins cause the
issue. I can even Login from the workstation with my
administrator login and the printing is fine.....HELP
PLEAS

 

[Dan]

We have mapped printers from the server to workstations
and installed an HP driver on the server for windows 2000
server to try to fix the issue.

-----Original Message-----
Do you happen to have non-Microsoft print drivers loaded

on your TS, i.e. ones you added to support new printers
that aren't supported by built-in drivers that shipped
with Windows 2000 Server?

If so this could be your problem, as 3rd party print

drivers are known to cause instability and even BSOD on a
Terminal Server.

 

[Guest]

Installing 3rd party drivers, even from HP can cause these kind of problems. The supported method is here

http://support.microsoft.com/default.aspx?scid=kb;EN-US;23908

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Dan wrote: ----

We have mapped printers from the server to workstations
and installed an HP driver on the server for windows 2000
server to try to fix the issue

-----Original Message----
Do you happen to have non-Microsoft print drivers loaded

on your TS, i.e. ones you added to support new printers
that aren't supported by built-in drivers that shipped
with Windows 2000 Serverdrivers are known to cause instability and even BSOD on a
Terminal Server

 

[Guest]

Patrick

My problem only happens from 2 specific workstations logging onto the terminal server with specific usernames and passwords, and the HP driver was installed after the problem began to try to fix it. When the user first logs in the available printers on the server are all there then you try to print to any printer on the network from that users login and the printers completely dissapear for everyone accessing that server and it requires me to reboot to get the printers to reappear this is not a an issue of connecting the workstations printers at login they connect fine. I have several networks i manage with terminal servers this is the first time i have ever seen this.

 

[Guest]

Dumb question, but I must ask it nonetheless

Are you running SP4 + Hotfixes

Are the users running the latest RDP client

What (if any) errors are in the System & Application Event Logs of the TS when these users logon, or when this happens

Does it happen when printing from any application, i.e. even a test print

Are these client machines special in any way, and can you re-image them to see if the problem goes away (after trying the other options)

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- dan wrote: ----

Patrick

My problem only happens from 2 specific workstations logging onto the terminal server with specific usernames and passwords, and the HP driver was installed after the problem began to try to fix it. When the user first logs in the available printers on the server are all there then you try to print to any printer on the network from that users login and the printers completely dissapear for everyone accessing that server and it requires me to reboot to get the printers to reappear this is not a an issue of connecting the workstations printers at login they connect fine. I have several networks i manage with terminal servers this is the first time i have ever seen this.

 

[Guest]

all updates are current, rdp client is on winxp all updates current, i would have to reformat and reinstall xp which i may do just wanted to see if anyone else experienced this and what they found to be the cure

 

[Matthew Harris [MVP]]

When all the printers on the server disappear, can you
check the status of the spooler service? Can you verify
that it is up and running correctly?

Maybe try this...can you remove the printers on those two
troublesome computers, then reinstall the printers using
different drivers, like HP LaserJet 4 drivers?

-M

-----Original Message-----
all updates are current, rdp client is on winxp all

updates current, i would have to reformat and reinstall xp
which i may do just wanted to see if anyone else
experienced this and what they found to be the cure

 

[Guest]

I have the luxury of having only 4 standard images that I deploy with RIS to anyone in my offices who doesn't have a thin-client, so I guess it makes me lazy because I can rebuild their machine in 30 minutes

Matthew may have hit the nail on the head with his comment

Patrick Rous
Microsoft MVP - Terminal Serve
http://www.workthin.co

----- Dan wrote: ----

all updates are current, rdp client is on winxp all updates current, i would have to reformat and reinstall xp which i may do just wanted to see if anyone else experienced this and what they found to be the cure