Remote desktop connection failing - no error message

  • Thread starter Thread starter Dirk
  • Start date Start date
D

Dirk

Hi all,

I've got a weird one. Local network, 2 machines running XP Pro SP2.
Up until a few days ago, regularly used remote desktop to connect from
one to the other.

Now, suddenly, the connection fails. If I try to connect, after I
enter the connection info & click the 'connection' button, the button
& info grey out for ~1 second, and then are re-enabled. There's no
connection made, and no error message at all.

I've verified that RD is running is running on the destination
machine. There's no firewall active on it that I know of, and the
only recent change to the machine is a different video card. I've re-
started the machine - no change. I've tried connecting to it from a
different computer, and it shows the exact same behaviour.

Anyone have any ideas?
Thanks,
Dirk
 
Yes - telnetting to port 3389 succeeds - I get a connection.

netstat -a shows port 3389 as listening.

Dirk
 
I have the exact same scenario. WinXP pro. INSTALLED A NEW GRAPHICS CARD.
Now Remote Desktop connection on Port 3389 have no effect. The Remote client
just acts like nothing happens when you press "connect" button.

I can ping port 3389, telnet to it.. etc
 
What new graphics card? There seem to be a lot of issues with new iNvida
drivers lately.

--

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

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375
 
It's an old nVidia 7300GS that's a temporary replacement for the
previous card that died.

I suppose I could try digging out an older driver version, & see what
happens.
 
I have been experiencing the same issue recently. Thursday I could RDP from work to home, Friday I couldn't, and couldn't even RDP from within my home network. Same symptoms. Telnet is OK, RDP doesn't error with an "unable to connect", it just pops back to an active "connect" button.

I upgraded an nVidia 7900GT to a new nVidia 8800GT card on Saturday. Prior to that I updated to the latest nVidia GPU drivers. I can't remember exactly when I updated the driver, but it could have been Thursday evening. When I get home today I'll try rolling the driver back and see what happens.
 
I have the exact same scenario. WinXP pro. INSTALLED A NEW
GRAPHICS CARD.
Now Remote Desktop connection on Port 3389 have no effect. The
Remote client
just acts like nothing happens when you press "connect" button.
Click to expand...

Try to set "Hardware Acceleration" to None (Display Properties ->
Settings -> Advanced -> Troubleshoot -> Hardware Acceleration -> None)

Recently, i updated ATI video drivers to the latest version and Remote
Desktop stopped working with exactly the same symptoms. Looks like
ATI/nVidia drivers are being developed by the same intern in his spare
time. Extremely crappy software. Try to stick to the version that
worked.
 
I have the same problem. I found out that when you reset your computer you
can login with mstsc. But when you logged on localy once, the rdp stops
working (wont connect at all, without a error message).

I tried all the versions forceware for my GeForce 8800 GTE, but none solved
the problem. Has anyone have any other idea?

Thanks in advance!
 
Thanks for the pointer - I've confirmed with nVidia that this is a
problem with the latest driver rev, and I've reverted to an older
version - problem solved.

Dirk
 
Thanks for the feedback...

--

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

Please post *ALL* questions and replies to the news group for the
mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
How to ask a question
http://support.microsoft.com/KB/555375

****************************************
Thanks for the pointer - I've confirmed with nVidia that this is a
problem with the latest driver rev, and I've reverted to an older
version - problem solved.

Dirk
 
Back
Top