Cannot reconnect to server after logging off...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I am hoping that someone can help me get this seriously irritating issue
solved.

I have two Windows 2000 servers. One is a web server and the other is a
mail server. I can log on to both servers via remote desktop just fine.
But, if I lose my connection or just log off like I am supposed to, when I go
to remote back in, I get the following error:

"The client could not establish a connection to the remote computer"

So, in order for me to remote back in, I need to reboot the servers as
needed, or shutdown/restart which seems to work.

This is really bad and it's getting frustrating rebooting the server every
time I need to remote in to do something, not to mention all my customers for
both web and mail that see it unavailable as it's rebooting.

Oh, I also wanted to mention that I have had these servers running for about
2 years without any problems using remote desktop. I do, however, remember
installing a Windows 2000 Server update sometime prior to this problem
arising.

I am in serious need of help, so if anyone has any suggestions, please bring
em' on...

Thanks,
Ken
 
Reports of this problem have recently started to show up here.

A couple of days ago someone posted that he had been into contact
with Microsoft Support, who said that it is caused by one of the
hotfixes contained in the MS04-032: Security update for Microsoft
Windows (November 2004), KB 840987.

Uninstalling this hotfix solved the problem.

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

"=?Utf-8?B?S2VuIENyb25pbg==?=" <Ken
 
Vera, thank you very much for the information. I uninstalled this particular
security update and it fixed the problem. I am so glad I came to this site
and decided to post. I've been dealing with this issue for at least 1 month
now.

Do you know if Microsoft is going to issue something to fix this? Because
I'm sure this update will continue to ask me to install it, right?

Thanks again!
Ken
 
I'm glad that your problem is solved for the moment, Ken!
I have no more information at the moment, but since Microsoft is
aware of the problem, I'm sure they are working on a new version
of the hotfix.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Vera,

Could this also be Armando's problem after installing SP4? If I translate his Spanish (and that's what I think it is), then it looks like a possible.

Armando posted 'dont connect TS from install SP4'.

Just a thought.

--

Always try the MS KB first before posting.
MS KB: http://support.microsoft.com/default.aspx?scid=fh;EN-US;KBHOWTO
And the answer could have already been posted, so try searching this and other newsgroups first.
----
Mark-Allen Perry
ALPHA Systems
Marly, Switzerland
mark-allen_AT_mvps_DOT_org

I'm glad that your problem is solved for the moment, Ken!
I have no more information at the moment, but since Microsoft is
aware of the problem, I'm sure they are working on a new version
of the hotfix.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---
 
Mark-Allen Perry said:
Vera,

Could this also be Armando's problem after installing SP4? If I
translate his Spanish (and that's what I think it is), then it
looks like a possible.

Armando posted 'dont connect TS from install SP4'.

Just a thought.
Click to expand...

Depends on how he installed SP4. If he downloaded SP4 as a separate
installation package, then he has a different problem.
If he ran Windows Update, he got a lot more than SP4, including the
specific hotfix that causes this problem.

The only way to be sure is to check for the error message in
EventLog, which I have never encountered before with any other
connection problem, so it's a good diagnostic.

Event Source: TermService
Event ID: 55
Description: Attempt to send a message to a disconnected
communication port

Hotfix involved: 840987
 
Back
Top