Avatar of Frogworks
Frogworks asked on

Windows Server 2008 Standard Terminal Server Woes

Good Afternoon Experts,

I'm having an issue that is very puzzling.  Until recently everything has been working fine with users logging in via a terminal server session to access applications. This week, suddenly all applications hang when attempting to print.  Even trying to stop the print spooler seems to take ages where last week it was a snap.  I also can't seem to connect to a printer that is shared on the DC, Windows says it is connecting but the printer never does connect nor does it time out.  I can literally walk away for hours and it will still be trying to connect to the printer.  

The other thing, even trying to open printers from the start menu takes almost 5 minutes, as it gradually shows the progress bar going up and then as it reaches the end just freezes and I'm forced to close it via task manager.

Any idea as to what could have happened to alter the characteristic of the terminal server so drastically?
Microsoft Legacy OSRemote Access

Avatar of undefined
Last Comment

8/22/2022 - Mon
Ben Hart

Much missing info here..

What is the typical resource load on this server during the height of usage?
Have you sifted thru the Event Viewer looking for errors?
Does the printing and printer control panel applet behave the same for a locally logged in user versus one thru RDP?

I won't go into the reasons for not using a DC as a printer server, but have you tried manually setting the printer up on the server running Remote Desktop Services?

I posted to another forum and was told to delete the .spl and .shd files and this fixed the problem

I've requested that this question be closed as follows:

Accepted answer: 0 points for Frogworks's comment #a39471928

for the following reason:

This resolved the issue, and I had not received any comments from anyone on my question.
Experts Exchange is like having an extremely knowledgeable team sitting and waiting for your call. Couldn't do my job half as well as I do without it!
James Murphy
Ben Hart

Wow.. Ill have to look that up.

Log in or sign up to see answer
Become an EE member today7-DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform
Sign up - Free for 7 days
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
See how we're fighting big data
Not exactly the question you had in mind?
Sign up for an EE membership and get your own personalized solution. With an EE membership, you can ask unlimited troubleshooting, research, or opinion questions.
ask a question

I feel that the fact that this fixed the issue despite it being knowledge that was imparted to me outside of Experts Exchange should be made aware to all those that could be experiencing the same problem.  

The sage IT professional who gave me the fix  would also recommend creating a .bat file like below for those having continual issues with their printers:


net stop spooler
del %systemroot%\system32\spool\printers\*.shd
del %systemroot%\system32\spool\printers\*.spl
net start spooler