W2K Terminal Services Drops Printers

We are running Windows 2000 SP4 Terminal Services with Windows XP SP2 clients.  About once a week the server keeps dropping all of our printers and we must reboot to get them back.  Is there any way to stop this from happening?

Thank you
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

I don't know about rebooting, but all you may have to do is restart the Printer Spooler service. If the service fails/stops no printers will be listed.
Hi ubicon - I've seen this many times and as craylord says it usually sorts itself out with a restart of the print spooler.

In fact, this is the service I have to manually restart most on a TS so much so that I made a very simple batch file to speed the process. Just put

net stop spooler
net start spooler

in a batch file and call it when you need to.

I'd also recommend making sure all your service packs are up to date.

Finally though, I would highly recommend rebooting any terminal server once per day regardless of whether you are experiencing difficulties. With the number of potential users logging on and all the different software they may be running, you can't be sure that there are no memory leaks etc which would quickly build up and impair performance.

I do an auto reboot of every one of my terminal servers every night as part of their backup and maintenance plan. Once the backup is complete the servers reboot, do a variety of tasks (such as chkdsk and temporary files cleanup) and run fine for the rest of the following day.


I have compiled a troubleshooting list below for troublshooting ts / citrix printing issues...  vera is excellent, start with his list...

Autocreation problems

    * 239088 - Windows 2000 Terminal Services Server Logs Events 1111, 1105, and 1106
    * Download Microsofts Printer Driver Redirection Wizard
    * Client Printer Autocreation Matrix - by PrintingSupport
    * 276532 - Windows 2000 Terminal Server Reports Event ID 1103 in the System Event Log
    * Event 1103 - An internal communication error occurred. Redirected printing will no longer function
    * 302361 - Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal Services Session
    * 329756 - Remote Desktop Connection Software May Cause an Access Violation If FilterQueueType Is Set - XP preSP2 hotfix
    * 843041 - FIX: The default printer for the RDP terminal client is not set as the default printer in a terminal session in Microsoft Windows CE .NET 4.2 - hotfix

this may be the same info http://www.tokeshi.com/modules.php?op=modload&name=News&file=article&sid=3233&mode=thread&order=0&thold=0

Autocreation of Client Printer will Fail if a Comma exists in the Client Name
     Posted by: RATokeshi on Sunday, April 04, 2004 - 09:25 PM
     Citrix MetaFrame 1.8 Tips and Tricks      Citrix states in their article: CTX955432
        CTX955432 - Autocreation of Client Printer will Fail if a Comma exists in the Client Name
        This document was published at: http://support.citrix.com/kb/entry.jspa?externalID=CTX955432
        Document ID: CTX955432, Created on: Aug 11, 2000, Updated: Apr 23, 2003
        Products: Citrix MetaFrame 1.8 for Microsoft Windows 2000, Citrix MetaFrame 1.8 for Microsoft NT 4.0 Server Terminal Server Edition, Citrix WinFrame 1.8
        If a user creates or changes the ICA client name and places a comma in that name, autocreation of printers will no longer function for that client.
        The Comma must be removed for Client Printer Autocreation to work.



New User
Joined: 16 Dec 2004
Posts: 1
PostPosted: Thu Dec 16, 2004 2:32 am    Post subject: Problems with autocreation and print spooler failures      Reply with quote
We've been having troubles on our Citrix Servers with them eventually failing to map client printers and receiving errors trying to restart the print spooler service. We believe it's the driver that we have installed. After doing some research on the net, we discovered that we need the HP LaserJet 1200 print driver version 4.27.1200.410 but we've been having a tough time finding it. Can anyone help us out?
Back to top      
View user's profile Send private message            
New User
Joined: 01 Mar 2005
Posts: 2
PostPosted: Tue Mar 01, 2005 2:57 am    Post subject:      Reply with quote
Hi, i had a similar problem, i installed the following patches from microsoft and it resolved my problem!


you may have seen all of these hints by now http://citrixforum.com/modules.php?name=Content&pa=showpage&pid=883

From the Readme for Hotfix XE101W028
While autocreating a client printer, the application event log may return the following error message when using the Universal Print Driver (UPD):
“Event ID 1106, Client printer autocreation failed.
The driver could not be installed. Possible reasonsfor the failure: The driver is not in the list of drivers on the server. The driver cannot be located.The driver has not been mapped.”
To prevent this error message from appearing, you need to edit the registry.
WARNING! Using Registry Editor incorrectly can cause serious problems that may require you to reinstall youroperating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
Navigate to the following registry key:
Add the following:
Value Name: DisableError
Type: DWORDValue: 1

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
ubiconAuthor Commented:
How does one do an auto reboot in W2K?  Do I set it up as a scheduled task?
I simply use a batch file as follows and yes, set it up as a scheduled task.

tsshutdn /REBOOT

You could get it to do a chkdsk while it's rebooting too although this requires an additional file ...

chkdsk c: /f /x <Y
chkdsk f: /f /x <Y ' add for as many drive letters as you have
tsshutdn /REBOOT

There are lots of options for tsshutdn - I suggest you have a look.

the Y is a piped in Y char followed by an enter key press which is used to bypass the need to agree to check the disks at next boot up. You need to create the file in the same folder as your reboot batch command.

You can't just create a file with a Y and an Enter press though. To do this, at the command prompt, type the following ...

copy con Y

Type the first line then press enter, then press Y, then hold down the alt key and press 013 (the code for Return) - finally (without pressing anything else), press the Ctrl Z key which will write the file to disk.

Now when you pipe this in to a function in a batch file it will give you a Y followed by an enter key press. Very handy for automating things.


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
Windows 2000

From novice to tech pro — start learning today.