Windows server 2008 can not access when the we remote it the deatails of the Error ID is below
I checked the error logs as below attached files TCP/IP failed to establish an outgoing connection because the selected local endpoint was recently used to connect to the same remote endpoint. This error typically occurs when outgoing connections are opened and closed at a high rate, causing all available local ports to be used and forcing TCP/IP to reuse a local port for an outgoing connection. To minimize the risk of data corruption, the TCP/IP standard requires a minimum time period to elapse between successive connections from a given local endpoint to a given remote endpoint. The process C: Windows system32 winlogon.exe (SHAI187A) has initiated the power off of computer SHAI187A on behalf of user NT AUTHORITY SYSTEM for the following reason: No title for this reason could be found Reason Code: 0x500ff Shutdown Type: power off Comment: The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. Client IP: xxx.xx.xxx.xx. The Terminal Server security layer detected an error in the protocol stream and has disconnected the client. Client IP: xxx.xxx.xxx.xxx. when we got this erro message some services idel can not working, and we alos can not log in it seem the explor also can not working
September 26th, 2012 4:14am

Hi, According to your description, please refer the following steps: 1. Whether you installed all the updates in the client computer and TS server. 2. Make sure you have installed the latest version of the Remote Desktop Connection in client computer or thin client. The Remote Desktop Connection 7.0 client update for Remote Desktop Services (RDS): http://support.microsoft.com/kb/969084/en-us 3. Please update the client and TS server's NIC driver to the latest version. Try to change client to automatically obtain IP address to see whether the issue still exists. 4. Please check whether too many users connect to the TS server and the performance loading is too heavy. 5. Changing the remote desktop setting on the target machine to allow connections from computer running any version of Remote Desktop (less secure) to see whether the issue still exists. regards, Clarence Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
September 27th, 2012 5:55am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics