Answer the question
In order to leave comments, you need to log in
An interesting case with the terminal server?
Good afternoon, gentlemen,
Today I encountered a strange problem with the customer. They asked to look at their servers (two win 2003 R2 domain controllers), the terminal server that users accessed suddenly stopped working. And I didn’t let anyone in either the admin or the users, of course I checked everything, the activation of the terminal server, the configuration of terminal services, I checked both domain controllers through dcdiag. Everything was in chocolate, there were no problems in events either, except for a couple of warnings for printers.
After making sure that all the services are working fine, I got to the point where I started checking the ports, it turned out that none of the services was listening to 3389 ...
In general, the solution turned out to be terrible ... as I guessed before, probably out of desperation.
Manually rebooted the print manager service, and everything worked!!!
Attention to the question, how is it possible?
Thank you in advance
PS I don't have certificates from Microsoft myself, to be honest, I don't have anyone to ask, competent people or engineers specializing in Windows can help.
Answer the question
In order to leave comments, you need to log in
I wonder what does the print manager service have to do with it?
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question