Remote desktop imtermitantly fails to connect

[raffelm]

My server is Windows 20003 Server, called niobe. My desktop is WinXP
Pro. And I use remote desktop application mstsc.exe to connect to
niobe.

Every other day, I have to reboot niobe before I can use remote
desktop to connect. On the day it works, everything is fine. On the
day it fails I get the error:

the client could not establish a connection to the remote
computer.
the most likely causes for this error are:
1) remote connections might not be enabled at the remote
computer.
2) the maximum number of connections was exceeded at the
remote computer.
3) A network error occurred while establishing the
connection.

Here's some things I have already tried for diagnosing the problem:

1) I can telnet to port 3389.

2) I've browsed around in the server event logs. Nothing seems
obvious (what should I look for?).

3) I've gone into the terminal services manager (on niobe) and reset
the connections, but that doesnt seem to correct the connectivity
problem.

4) I've never have a license file appear in the MSLicensing registry
key.

Only a reboot of niobe seems to fix the problem. This doesnt seem
right.

Any ideas about what the problem is or what I can do to fix it?

Thnx
Matt

 

[jsteffen]

I've had that problem and it's due to the SMS Advanced Client problem.
If you use that also, try these patches in this order:

KB831962
KB831648

*My server is Windows 20003 Server, called niobe. My desktop i
WinXP
Pro. And I use remote desktop application mstsc.exe to connect to
niobe.

Every other day, I have to reboot niobe before I can use remote
desktop to connect. On the day it works, everything is fine. O
the
day it fails I get the error:

the client could not establish a connection to the remote
computer.
the most likely causes for this error are:
1) remote connections might not be enabled at the remote
computer.
2) the maximum number of connections was exceeded at the
remote computer.
3) A network error occurred while establishing the
connection.

Here's some things I have already tried for diagnosing the problem:

1) I can telnet to port 3389.

2) I've browsed around in the server event logs. Nothing seems
obvious (what should I look for?).

3) I've gone into the terminal services manager (on niobe) and reset
the connections, but that doesnt seem to correct the connectivity
problem.

4) I've never have a license file appear in the MSLicensing registry
key.

Only a reboot of niobe seems to fix the problem. This doesnt seem
right.

Any ideas about what the problem is or what I can do to fix it?

Thnx
Matt

-
jsteffe