RDP Intermittent

[Steve]

Hello,

I've been nagged by this problem for a while now and can't seem to find any
solutions for it.

I have several users in the office who intermittently receive the "cannot
connect to remote machine" error. Each time this occurs port 3389 is not
listening on the host machine.

The problem does resolve itself after time.

1) TS Service is running
2) No Windows Firewall
3) No other firewall

Any thoughts out there?

 

[Sooner Al [MVP]]

When this happens can you verify if the Terminal Services service is still
running on the Remote Desktop [RDC] host?

http://theillustratednetwork.mvps.o...pSetupandTroubleshooting.html#Troubleshooting

You also might look at the event logs to see if there are any clues.

http://support.microsoft.com/kb/308427

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

This posting is provided "AS IS" with no warranties, and confers no
rights...
The MS-MVP Program - http://mvp.support.microsoft.com

 

[Steve]

TS is running under Services.
Port 3389 is not listed in netstat report
Cannot telnet <ip> 3389
Event log does not appear to have any information related to TS

When this happens can you verify if the Terminal Services service is still
running on the Remote Desktop [RDC] host?

http://theillustratednetwork.mvps.o...pSetupandTroubleshooting.html#Troubleshooting

You also might look at the event logs to see if there are any clues.

http://support.microsoft.com/kb/308427

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

This posting is provided "AS IS" with no warranties, and confers no
rights...
The MS-MVP Program - http://mvp.support.microsoft.com

Hello,

I've been nagged by this problem for a while now and can't seem to find any
solutions for it.

I have several users in the office who intermittently receive the "cannot
connect to remote machine" error. Each time this occurs port 3389 is not
listening on the host machine.

The problem does resolve itself after time.

1) TS Service is running
2) No Windows Firewall
3) No other firewall

Any thoughts out there?

 

[Sooner Al [MVP]]

If the RDC host is not listening on TCP Port 3389 then the telnet test will
definitely fail.

Are you running anything like Norton Anti-virus or OneCare Live on the RDC
host? There have been reports of those blocking RDC incoming connections.

Do you have this problem when you try to connect over the local LAN versus
from a remote location?

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

This posting is provided "AS IS" with no warranties, and confers no
rights...
The MS-MVP Program - http://mvp.support.microsoft.com

 

[Steve]

We use McAfee.
The problem exists whether local or remote.

 

[Sooner Al [MVP]]

Well, you could try using a system restore point made prior to the problem
occurring to see if that fixes the issue.

Otherwise you just need to figure out what is blocking RDC intermittently.
It may be worth a try removing McAfee as a test.

Good luck...

--

Al Jarvi (MS-MVP Windows – Desktop User Experience)

This posting is provided "AS IS" with no warranties, and confers no
rights...
The MS-MVP Program - http://mvp.support.microsoft.com

 

[Steve]

The netstat -ant shows no port 3389 open. How would something be blocking it?
Wouldn't this be a TS issue?