RDP to XP disconnects immediately

I have a serie PC's XPSP2, all the same (AMD VIA KM400) mainboards. All get
the same GPO from AD and all have the same videodriver. To some of these PC's
I can not connect with RDP. It disconnects me immediately: I get a black
screen, with an error message: The remote PC's disconnected the connection.
Ports are all open, tested with different tools: no firewall.

To other PC's with same hard- and software I CAN connect with RDP.
On One of the "bad" PC's I updated the videodriver, but this didn't help.

What else can be the problem?

Thanks in advance,
Hennie.

Greetings!

I have the same problem although I am not using AD. Here are a few things I
have discovered.

- If I am initially logged into the console and then try to RDP in (either
while on the local network or from my home with VPN established) I cannot
make an RDP connection. I get the login prompt for the remote system but once
clicking OK I either get immediately disconnected or I get a blank blue
screen. The remote system goes to the welcome screen and eventually my client
machine drops the RDP session (times out).

- If I logoff the console session, I am able to RDP into the machine. I can
continue to RDP into the system from either the local network or my home over
the VPN. There are no problems. However, as soon as I reconnect directly at
the console, I am no longer able to establish an RDP session until I logoff
the console.

- In some situations, I am not even able to get the login prompt, the client
flashes on the screen and immediately disconnects. My console session does
not seem to be impacted in any way.

- I have tried closing down the applications I always run doing so one at a
time and then establishing an RDP session. I have found that once I close
down any office 2003 apps and explorer windows (not IE just open folders or
drives), I have been able to connect but not consistently.

- My system is running an NVidia 6600 GT video card with an older driver
(10/2005). I have DVI to a viewsonic 20" screen running 1600x1200 resolution.
My RDP sessions are also always run at full screeen on systems that also run
at 1600x1200 resolution. I have noticed that the newer nvidia drivers seem to
mention support for multiple desktop functionality in remote desktop
sessions. Based on this, I thought perhaps the video driver might be the
issue.

Yesterday I attempted to update the driver to Nvidia's latest WHQL driver,
91.47_forceware but upon rebooting I get the windows XP logo and then a blank
screen. After using safe mode to roll the driver back, my machine works fine.
I tried another driver direct from the video card mfc, 84.21 Forceware, with
the exact same result.

Doing some research I have found where there might be an issue with DVI
support @ 1600x1200 resolution and the nvidia drivers. I can't get any real
substantial details on this but have been making posts to the card MFC and
will also do the same to Nvidia directly. For the record, if I adjust my
video resolution to 1280x1024 I get the same end result (blank screen on
boot). I also get the same result if I use a VGA connection.

Are there any known issues with RDP and immediate disconnects? is there any
other information that I've not supplied in my little novel here that would
be of assistance in resolving this issue? The need to logoff and close all of
my existing work every night is driving me nuts as it never used to happen on
my older systems.

I am willing to provide any other additional information that is necessary
to resolve this problem.

Thanks!
-Scott K.


"Hendrik" wrote:

> I have a serie PC's XPSP2, all the same (AMD VIA KM400) mainboards. All get
> the same GPO from AD and all have the same videodriver. To some of these PC's
> I can not connect with RDP. It disconnects me immediately: I get a black
> screen, with an error message: The remote PC's disconnected the connection.
> Ports are all open, tested with different tools: no firewall.
>
> To other PC's with same hard- and software I CAN connect with RDP.
> On One of the "bad" PC's I updated the videodriver, but this didn't help.
>
> What else can be the problem?
>
> Thanks in advance,
> Hennie.
>
>