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?
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?
ASKER
I posted to another forum and was told to delete the .spl and .shd files and this fixed the problem
ASKER
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.
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.
Wow.. Ill have to look that up.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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:
"FixPrinter.bat"
net stop spooler
del %systemroot%\system32\spoo
del %systemroot%\system32\spoo
net start spooler
exit
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:
"FixPrinter.bat"
net stop spooler
del %systemroot%\system32\spoo
del %systemroot%\system32\spoo
net start spooler
exit
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?