Robert Perez-Corona
asked on
Terminal Services unavailable after reboot due to Event ID 5378
Hello,
I am in the process of migration a terminal services server in my production environment. Unfortunately, it is still running Windows 2003. Hopefully for just another week or so.
However, at the moment this is production and they need to be online asap.
The server was working fine this past friday. Until this morning that users are reporting they cannot connect. However, I can RDP into as admin.
I notice that the Encryption level is low on the admin port and set to client compatible on the applicatin production side. However, no one has changed anything on the server. So I can say this has been like this all along
Any reason why users receive an error stating the "Remote desktop cannot be initialized...server could be off, or network problem.." typically RDP error?
I am in the process of migration a terminal services server in my production environment. Unfortunately, it is still running Windows 2003. Hopefully for just another week or so.
However, at the moment this is production and they need to be online asap.
The server was working fine this past friday. Until this morning that users are reporting they cannot connect. However, I can RDP into as admin.
I notice that the Encryption level is low on the admin port and set to client compatible on the applicatin production side. However, no one has changed anything on the server. So I can say this has been like this all along
Any reason why users receive an error stating the "Remote desktop cannot be initialized...server could be off, or network problem.." typically RDP error?
ASKER
rebooted the server and it now works. Users are able to connect.
Yet, the TS error messages persist from event viewer
Yet, the TS error messages persist from event viewer
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER