Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 483
  • Last Modified:

Attempt to send a message to a disconnected communications port / Terminal Services not working


We are running a Windows 2000 Terminal server, and every day at about 4 oclock it seems we are unable to connect to our Terminal Server using Remote Desktop. There are numerous events in the event log saying "Attempt to send a message to a disconnected communications port" with Event ID 55. We find that a reboot of the server fixes the problem. There are no inactive sessions, and I have set a limit to end sessions after 10 minutes. Has anyone come across this problem before?

Daniel Murfitt
1 Solution
HotFix KB840987 can cause this issue.  (as listed through Add/Remove programs)

At least on servers with Win2K SP4.  
Just note: When you remove this HotFix using Change/Remove which immediately reboots the server
when you click Finish at the end of the uninstall process.  I heard elsewhere that A tech
acknowledged that MS had an article on this exact issue in their
"internal KB".  

As of today that article has obviously not been
published to the public KB.

Hope this helps,

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now