Printing problem from remote server via remote desktop

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I tried to access Window printer setup in a remote server to print from the
server to local printer via Remote desktop. The remote server and the local
print server are in the same domain so sharing printing resources are not an
issue because it had been tested before and worked fine. However, two days
ago, I saw the following error message(please see end of message). Also today
I see all printers in the setup of the remote server gone missing and when I
tried to add new printer,I see the following error message(please see end of
message). The error message did not appear at local server or via local
desktop but it only occur via remote connection from remote clients.
Can you please advice what is the root cause of the problem? Thanks in
advance.

The error message appear in the remote server (via Remote desktop) is

Out of Resources
 
Sounds like your printer spooler crashed.
Anything in the EventLog on the server?
Have you tried to restart the Spooler service?
Did you install 3rd party printer drivers on the server?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
Vera,

Thanks for your clue and suggestion. The root cause is due to the printer
spooler service having problem. Restart it has solved the problem.

Vera Noest said:
Sounds like your printer spooler crashed.
Anything in the EventLog on the server?
Have you tried to restart the Spooler service?
Did you install 3rd party printer drivers on the server?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
OK, I'm glad that the immediate problem is solved.
However, if the printer spooler crashed because you installed a 3rd
party printer driver, I expect it to happen again.

If so, uninstall any 3rd party printer driver, and map your
printers to a native driver, by creating a custom ntprintsubs.inf
file.
Details here:

239088 - Windows 2000 Terminal Services Server Logs Events 1111,
1105, and 1106
http://support.microsoft.com/?kbid=239088

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
 
Back
Top