Remote desktop stopped working

[Guest]

I have been using remote desktop for quite some time without problems.
Suddenly it stopped working, instead giving an error message similar to this
(translated into english):

"The remote desktop has been disconnected

The client could not establish a connection to the remote computer.
Possible causes:
1) Remote connections maybe isn't activated on the remote computer.
2) No more connections can be made to the remote computer.
3) A network error occurred when the connection was about to be established."

However, I have checked the remote computer and connections are indeed
allowed and, as far as I know, there is no upper limit on the number of
connections that you can make to the remote computer. I don't know what could
be a network error though. The internet connection works just fine.
Does anyone have any idea what could be the problem?

 

[Justin Jeffries]

Check on both computer & Make sure your firewall accepts remote connections,
especially if running SP2. Also, make sure that TCP Port 3389 is enabled for
allowing incoming/outgoing connections in order to work remotely. These
setting could have evenly been changed.

 

[Guest]

The firewall accepts remote connections and TCP 3389 is enabled.

 

[dilbonzo]

I had the same problem just a week ago, about the same time you did.
have been using remote desktop for a long time just fine, and then i
just stopped working. I get the same error.

Doing a netstat -a shows that svchost.exe is running and listening o
TCP port 3389. I can't figure it out. I am on an internal network an
so my router is out of the picture, it is all behind the route
firewall. I am running XP, SP1, no firewall on this box. I don't kno
why it suddenly stopped working.

Any other suggestions I could try to look at to see what is wrong?

*I have been using remote desktop for quite some time withou
problems.
Suddenly it stopped working, instead giving an error message simila
to this
(translated into english):

"The remote desktop has been disconnected

The client could not establish a connection to the remote computer.
Possible causes:
1) Remote connections maybe isn't activated on the remote computer.
2) No more connections can be made to the remote computer.
3) A network error occurred when the connection was about to b
established."

However, I have checked the remote computer and connections ar
indeed
allowed and, as far as I know, there is no upper limit on the numbe
of
connections that you can make to the remote computer. I don't kno
what could
be a network error though. The internet connection works just fine.
Does anyone have any idea what could be the problem?

-
dilbonz

 

[TechConSwe]

I can just confirm the problem.

My customer have two Windows 2000 Servers with TS enabled. One of the
is in Application mode, and the other one is in Remote Administratio
Mode. However, the one in App. Mode work abolutly fine, but not the on
in R.A. Mode.

It doesn't mather if I try to connect to the server via Termina
Service Client from ether Windows 2000 or Windows XP (i.e. RDP Client)
I've also tried to connect to it from a Windows NT 4.0 WKS, with n
luck.

Last week, I found a thread like this were a guy recommended
reinstalltion of TS, wich I did. It worked for about a week after that
but now the problem have reocurred.

I've also tried to connect to it from the intranet as well as from th
Internet. It doesn't mather.

Now, the interesting thing is that everone with the problem has notice
it the last couple of weeks. This particular thread was created in th
middle of december 2004. Is there maybe some security patch we'v
installed that creates this problem? I've searched a lot o
support.microsoft.com, but without finding anything about this.

Please add your comments to this post so that we have a chance t
figure out what causes this problem.

Regards,
Anders

*I had the same problem just a week ago, about the same time you did
I have been using remote desktop for a long time just fine, and the
it just stopped working. I get the same error.

Doing a netstat -a shows that svchost.exe is running and listening o
TCP port 3389. I can't figure it out. I am on an internal networ
and so my router is out of the picture, it is all behind the route
firewall. I am running XP, SP1, no firewall on this box. I don'
know why it suddenly stopped working.

Any other suggestions I could try to look at to see what is wrong?

-
TechConSw

 

[PaulS_III]

*I can just confirm the problem.

My customer have two Windows 2000 Servers with TS enabled. One of
them is in Application mode, and the other one is in Remote
Administration Mode. However, the one in App. Mode work abolutly
fine, but not the one in R.A. Mode.

It doesn't mather if I try to connect to the server via Terminal
Service Client from ether Windows 2000 or Windows XP (i.e. RDP
Client). I've also tried to connect to it from a Windows NT 4.0 WKS,
with no luck.

Last week, I found a thread like this were a guy recommended a
reinstalltion of TS, wich I did. It worked for about a week after
that, but now the problem have reocurred.

I've also tried to connect to it from the intranet as well as from
the Internet. It doesn't mather.

Now, the interesting thing is that everone with the problem has
noticed it the last couple of weeks. This particular thread was
created in the middle of december 2004. Is there maybe some security
patch we've installed that creates this problem? I've searched a lot
on support.microsoft.com, but without finding anything about this.

Please add your comments to this post so that we have a chance to
figure out what causes this problem.

Regards,
Anders *

Quite interesting indeed. For I have been experienceing the same
problem since right around Christmas.

I use remote desktop and terminal services (which by the way does not
work as well) to connect between a windows 2000 box and windows 2000
server box.

Now I did some searching in the add/remove programs on my windows 2000
sever and found 3 or 4 hot fixes that were dated december 21, 2004. I
did the stupid thing and uninstalled those hot fixes, but it did no
good.

Now I am wondering if I should do the stupid thing and uninstall the
same hot fixes on my windows 2000 box as well and see if that makes a
diference.

I take it no one has come up with a solution yet.

My two cents
Paul

 

[dilbonzo]

I figured out the problem. I installed norton antivirus 2005 and th
new internet worm security feature is blocking me from remoting into m
box. I had to go into options, then under specific program, open u
svchost.exe, and add a rule to allow port 3389 through and then i
worked.

Good luck.

*Quite interesting indeed. For I have been experienceing the sam
problem since right around Christmas.

I use remote desktop and terminal services (which by the way does no
work as well) to connect between a windows 2000 box and windows 200
server box.

Now I did some searching in the add/remove programs on my window
2000 sever and found 3 or 4 hot fixes that were dated december 21
2004. I did the stupid thing and uninstalled those hot fixes, but i
did no good.

Now I am wondering if I should do the stupid thing and uninstall th
same hot fixes on my windows 2000 box as well and see if that makes
diference.

I take it no one has come up with a solution yet.

My two cents
Paul

-
dilbonz

 

[TechConSwe]

You've maybe solved your own problem, but for us other it's not quit
that simple I'm afraid.

But I did discover another thing. Is there anybody besides me that use
Dame Ware 4.x to the servers that are affected with this problem?

Anders

*I figured out the problem. I installed norton antivirus 2005 an
the new internet worm security feature is blocking me from remotin
into my box. I had to go into options, then under specific program
open up svchost.exe, and add a rule to allow port 3389 through an
then it worked.

Good luck.

-
TechConSw

 

[Chad A. Smith]

Try rolling back termsrv.dll in the systm32 directory. It fixed the problem
for me.

The one I went back to came with SP1. 196K dated 8/29/02.

HTH,

Chad