Guest Evan Kaye Posted August 18, 2008 Posted August 18, 2008 I know Remote Desktop isn't strictly speaking "Terminal Services", but it seemed to be the closest match. After installing Windows XP Service Pack 3 on my home system, I cannot connect to it by Remote Desktop. The client seems to be trying to connect for a moment, and then automatically cancels less than a second later, with no error message (whereas I DO get an error if I try to connect to the wrong machine or port). I have tried connecting from outside my home network, from another PC on my network over the router's WAN interface, from the other PC directly to the local network address, and from the PC in question itself to the WAN interface (it won't let me try to connect to its own local address); same result every time. Remote Desktop worked fine before I installed SP3. I have rebooted my system, disabled and re-enabled Remote Desktop in System Properties, and added accounts explicitly to those allowed to logon over Terminal Services using secpol.msc (they were already members of Remote Desktop Users). I used to connect over a non-standard port for security reasons, which was mapped to 3389 by the router. I changed it so the non-standard port is passed straight through the router, and changed the PC's RDP port in the registry; issue unchanged. Windows Firewall was and is disabled. Using Wireshark, I can confirm that the RDP client packets are reaching the serving PC. If I post the capture here, will someone be able to look into it and tell me what's wrong?
Guest jolteroli Posted August 18, 2008 Posted August 18, 2008 Re: Cannot Remote Desktop to home PC after installing XP SP3 hey evan, edit the rdp connection and look on the last register "performance". there is a option which controls the behaviour when the security constrains are not met. im from germany so i can't tell you the exact text. the dropdown box should have selected to something analogous to "connect und don't show a warning" instead to "do not connect". this is new in the rdp-6.1 client. -jolt
Guest Vera Noest [MVP] Posted August 18, 2008 Posted August 18, 2008 Re: Cannot Remote Desktop to home PC after installing XP SP3 Is the PC listening on the rdp port? When you type "netstat -an" (without the quotes), do you see something like: Prot. Local address Ext. address Status TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING or whatever port you have configured for rdp? Are there any Events in the EventLog on the PC which can't be reached? Are you connecting from a client which runs rdp 6.x? What are the settings under Advanced - server authentication? _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ =?Utf-8?B?RXZhbiBLYXll?= <Evan Kaye@discussions.microsoft.com> wrote on 18 aug 2008 in microsoft.public.windows.terminal_services: > I know Remote Desktop isn't strictly speaking "Terminal > Services", but it seemed to be the closest match. After > installing Windows XP Service Pack 3 on my home system, I cannot > connect to it by Remote Desktop. The client seems to be trying > to connect for a moment, and then automatically cancels less > than a second later, with no error message (whereas I DO get an > error if I try to connect to the wrong machine or port). I have > tried connecting from outside my home network, from another PC > on my network over the router's WAN interface, from the other PC > directly to the local network address, and from the PC in > question itself to the WAN interface (it won't let me try to > connect to its own local address); same result every time. > Remote Desktop worked fine before I installed SP3. > > I have rebooted my system, disabled and re-enabled Remote > Desktop in System Properties, and added accounts explicitly to > those allowed to logon over Terminal Services using secpol.msc > (they were already members of Remote Desktop Users). I used to > connect over a non-standard port for security reasons, which was > mapped to 3389 by the router. I changed it so the non-standard > port is passed straight through the router, and changed the PC's > RDP port in the registry; issue unchanged. Windows Firewall was > and is disabled. > > Using Wireshark, I can confirm that the RDP client packets are > reaching the serving PC. If I post the capture here, will > someone be able to look into it and tell me what's wrong?
Guest Evan Kaye Posted August 18, 2008 Posted August 18, 2008 Re: Cannot Remote Desktop to home PC after installing XP SP3 I found the problem. Apparently the latest nVidia drivers break Remote Desktop unless a registry tweak is made. I'll give it a try and report back if it doesn't work. "Vera Noest [MVP]" wrote: > Is the PC listening on the rdp port? When you type "netstat -an" > (without the quotes), do you see something like: > > Prot. Local address Ext. address Status > TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING > > or whatever port you have configured for rdp? > > Are there any Events in the EventLog on the PC which can't be > reached? > Are you connecting from a client which runs rdp 6.x? What are the > settings under Advanced - server authentication? > _________________________________________________________ > Vera Noest > MCSE, CCEA, Microsoft MVP - Terminal Server > TS troubleshooting: http://ts.veranoest.net > ___ please respond in newsgroup, NOT by private email ___ > > =?Utf-8?B?RXZhbiBLYXll?= <Evan Kaye@discussions.microsoft.com> > wrote on 18 aug 2008 in > microsoft.public.windows.terminal_services: > > > I know Remote Desktop isn't strictly speaking "Terminal > > Services", but it seemed to be the closest match. After > > installing Windows XP Service Pack 3 on my home system, I cannot > > connect to it by Remote Desktop. The client seems to be trying > > to connect for a moment, and then automatically cancels less > > than a second later, with no error message (whereas I DO get an > > error if I try to connect to the wrong machine or port). I have > > tried connecting from outside my home network, from another PC > > on my network over the router's WAN interface, from the other PC > > directly to the local network address, and from the PC in > > question itself to the WAN interface (it won't let me try to > > connect to its own local address); same result every time. > > Remote Desktop worked fine before I installed SP3. > > > > I have rebooted my system, disabled and re-enabled Remote > > Desktop in System Properties, and added accounts explicitly to > > those allowed to logon over Terminal Services using secpol.msc > > (they were already members of Remote Desktop Users). I used to > > connect over a non-standard port for security reasons, which was > > mapped to 3389 by the router. I changed it so the non-standard > > port is passed straight through the router, and changed the PC's > > RDP port in the registry; issue unchanged. Windows Firewall was > > and is disabled. > > > > Using Wireshark, I can confirm that the RDP client packets are > > reaching the serving PC. If I post the capture here, will > > someone be able to look into it and tell me what's wrong? >
Guest Vera Noest [MVP] Posted August 19, 2008 Posted August 19, 2008 Re: Cannot Remote Desktop to home PC after installing XP SP3 OK, nVidia again, eh? I would appreciate it if you could post the exact registry key and the version of the nVidia driver which is causing this problem! _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net *----------- Please reply in newsgroup -------------* =?Utf-8?B?RXZhbiBLYXll?= <EvanKaye@discussions.microsoft.com> wrote on 19 aug 2008: > I found the problem. Apparently the latest nVidia drivers break > Remote Desktop unless a registry tweak is made. I'll give it a > try and report back if it doesn't work. > > "Vera Noest [MVP]" wrote: > >> Is the PC listening on the rdp port? When you type "netstat >> -an" (without the quotes), do you see something like: >> >> Prot. Local address Ext. address Status >> TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING >> >> or whatever port you have configured for rdp? >> >> Are there any Events in the EventLog on the PC which can't be >> reached? >> Are you connecting from a client which runs rdp 6.x? What are >> the settings under Advanced - server authentication? >> _________________________________________________________ >> Vera Noest >> MCSE, CCEA, Microsoft MVP - Terminal Server >> TS troubleshooting: http://ts.veranoest.net >> ___ please respond in newsgroup, NOT by private email ___ >> >> =?Utf-8?B?RXZhbiBLYXll?= <Evan Kaye@discussions.microsoft.com> >> wrote on 18 aug 2008 in >> microsoft.public.windows.terminal_services: >> >> > I know Remote Desktop isn't strictly speaking "Terminal >> > Services", but it seemed to be the closest match. After >> > installing Windows XP Service Pack 3 on my home system, I >> > cannot connect to it by Remote Desktop. The client seems to >> > be trying to connect for a moment, and then automatically >> > cancels less than a second later, with no error message >> > (whereas I DO get an error if I try to connect to the wrong >> > machine or port). I have tried connecting from outside my >> > home network, from another PC on my network over the router's >> > WAN interface, from the other PC directly to the local >> > network address, and from the PC in question itself to the >> > WAN interface (it won't let me try to connect to its own >> > local address); same result every time. Remote Desktop worked >> > fine before I installed SP3. >> > >> > I have rebooted my system, disabled and re-enabled Remote >> > Desktop in System Properties, and added accounts explicitly >> > to those allowed to logon over Terminal Services using >> > secpol.msc (they were already members of Remote Desktop >> > Users). I used to connect over a non-standard port for >> > security reasons, which was mapped to 3389 by the router. I >> > changed it so the non-standard port is passed straight >> > through the router, and changed the PC's RDP port in the >> > registry; issue unchanged. Windows Firewall was and is >> > disabled. >> > >> > Using Wireshark, I can confirm that the RDP client packets >> > are reaching the serving PC. If I post the capture here, >> > will someone be able to look into it and tell me what's >> > wrong?
Guest micah pfaffe Posted September 18, 2008 Posted September 18, 2008 [PLAIN]Cannot Remote Desktop to home PC after installing XP SP3- Vera Noest [MVP][/PLAIN] Cannot Remote Desktop to home PC after installing XP SP3- Vera Noest [MVP] Here's the registry key: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management] Edit/create the DWORD Value: "SessionImageSize" set it to 20 (which equals 32MB). If that doesn't work, try increasing the size... 20 = 32MB 40 = 64MB 60 = 96MB 80 = 128MB
Guest Vera Noest [MVP] Posted September 19, 2008 Posted September 19, 2008 [PLAIN]Re: Cannot Remote Desktop to home PC after installing XP SP3 - Vera Noest [MVP][/PLAIN] Re: Cannot Remote Desktop to home PC after installing XP SP3 - Vera Noest [MVP] Thanks, micah! I'll keep that for later reference, I've seen a few more posts about nvidia drivers causing rdp connections to fail. _________________________________________________________ Vera Noest MCSE, CCEA, Microsoft MVP - Terminal Server TS troubleshooting: http://ts.veranoest.net ___ please respond in newsgroup, NOT by private email ___ micah pfaffe wrote on 18 sep 2008 in microsoft.public.windows.terminal_services: > Here's the registry key: > > [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session > Manager\Memory Management] > > Edit/create the DWORD Value: "SessionImageSize" > set it to 20 (which equals 32MB). > > If that doesn't work, try increasing the size... > 20 = 32MB > 40 = 64MB > 60 = 96MB > 80 = 128MB
Recommended Posts