Windows Vista - Issue with RDP connection after XX minutes.
Hi.So, this is possibly the strangest problem I've ever met, and I can't seem to solve it.The issue is as follows:I have one server running on Windows XP, which is located hundreds of miles away from me. Here at home, I have my workstation with Vista Ultimate 64 and my trusty server with Win2k8. So, from a number of reasons I would sometime need to access my XP server. And this is where the problem start. If I've just rebooted my workstation, I can connect with RDP (and for example, Telenet) with no problem. And as long as I keep the connection open, there is no problem. If I however try to close the connection, and then try to reconnect for example, 15 minutes later - it doesn't work! Neither does Telenet/SSH/Whatever. From my 2k8 server though, everything still works fine - and all my mates can connect to the XP-machine as well. So, I think it's safe to conclude that the problem is on my workstation.So, after a number of hrs I have found something that might be related to the problem. With the help of Network Monitor I've found that while the connection work, "source" is listed as my IP-address, for example:Process name: Microsoft RDPSource: 10.10.10.50 (My IP)Destination: myip.dnsalias.comHowever, when I try to reconnect later, it says (when it doesn't work):Process name: Microsoft RDPSource: Khadgar (Which is my computer's name).Destination: myip.dnsalias.comI can also menition that it does not help if I type the IP-adress to the XP-machine, instead of the DNS-name. I can however (if its relevant) connect to the LAN where the XP-machine is at, by HTTP.So, does anyone know how to solve this? I would be forever grateful.Thanks a lot in advance.
November 25th, 2008 5:15pm

Hi, I am a bit unclear about the exact issue there. May I know the following first? 1. Please confirm whether my understanding regarding the issue is correct: a. After reboot, the first time of the RDP connection to the remote Windows XP computer always works. b. If you disconnect the RDP connection and then try to connect to it again, it always fails, no matter via IP address or computer name. c. Everything works well on other computers. d. The computer where you used locally is Khadgar/10.10.10.50 and it is installed with Windows Vista. e. The network traces you mentioned were collected from the local Windows Vista computer. The above information is quite important. Please confirm. 2. What error was received when the Windows Vista computer failed to re-connect to the remote Windows XP computer? 3. Are these computers in the same domain? How are they connected physically? Please let me know your network topology in detail. 4. Check the event logs on both computers. Are there any related error messages? 5. If possible, please send me the network traces at nicolesli@hotmail.com. Meanwhile, please try the following suggestions: 1. When disconnecting the first RDP session, please use the following method as a test: Click Start and then click Log Off (do not just close the RDP window, or click Start->Disconnect). Then, connect it again and see how it works now. 2. I suspect the issue can be caused by the factor that the session on the Windows XP is reach the limit or broken. And we need to change settings on the Windows XP side for when a session limit with the following instructions: 1) Open Group Policy. 2)In Computer Configuration, Administrative Templates, Windows Components, Terminal Services, Sessions, double-click the Terminate session when time limits are reached setting, and do one of the following: a)To ensure that users are always disconnected from the session, allowing the session to be reconnected (default behavior), click Disabled, and then click OK. b)To configure Terminal Server to terminate sessions rather than disconnect them, click Enabled, and then click OK. See the policy explain text for more information. 3. Try to upgrade Remote Desktop Connection (Terminal Services Client)on both of the computers. If you are running Windows XP SP2, please refer to: http://support.microsoft.com/kb/925876 If you are running Windows Vista SP1 and Windows XP SP3, please refer to: http://support.microsoft.com/kb/951616 More information for your reference: Session Time Limits http://technet.microsoft.com/en-us/library/cc753112.aspx Changes to remote administration in Windows Server 2008 http://support.microsoft.com/kb/947723 Thanks!
Free Windows Admin Tool Kit Click here and download it now
November 27th, 2008 1:24pm

Hi.Thanks a lot for your reply, I'll try to answer as best as I can.1.a) Yes, that is correct. The first time I try to connect, both the RDP and Telnet/SSH connection works.b) Yes, in a way. Sometimes, I'm able to connect even two or three times, before the connection is refused. This goes for both the RDP and Telnet/SSH. It's almost like it's on a timer, but I can't see a pattern in the times (sometimes 10 minutes, others just 5 minutes). No difference between IP and DNS.c) Yes, that is correct. From my Windows 2k8 Server which is on the same LAN as my workstation, it always works. Again, this goes for both the RDP and Telnet/SSH. Also, I've had some of my mates to try it, they can also connect each time. Hence, I believe the problem lies somewhere with my workstation ...d) Yes, that is correct. My workstation is called "Khadgar", and runs on Windows Vista Ultimate 64bit with the IP-address 10.10.10.50.e) Yes, also correct. I used the beta of Network Monitor 3.1 to monitor the traffic that leaves my workstation.2. I get the standard "This computer can't connect to the remote computer" error message.3. My Vista workstation and my 2k8 Server is on the same LAN (and Workgroup), where the 2k8 server is running as DHCP/DNS. All traffic goes trough a D-Link router.The XP-computer (the one I'm trying to connect to) is in another part of the country, and not on the same domain (I only run Workgroups). It too is on a LAN behind a D-Link router, but here the router also acts as DHCP/DNS-server. I have full access to both routers, in case something needs to be changed here. I have however tried to connect without the router, and in DMZ, with the same result.4. No error messages, and I wasn't able to find anything that looked of intrest.5. I'll be more then happy to send you the logs from Network Mointor, if that was what you were thinking of?... I'm sending them anyway No luck with either solutions. Also, unfortunaly both the RDP clients were up to date, hence a update didn't change much.
November 27th, 2008 6:05pm

Minor update: After a restart on the XP-machine, it now logged the following error in the event log: An incorrect X.224 protocol error message is logged - screen shot.Which then lead me here: http://support.microsoft.com/default.aspx/kb/312313/enAccording to the knowledge database, a hotfix should fix the problem. However, this seems to apply for PC's with Win 2k, hence I'm still stuck.
Free Windows Admin Tool Kit Click here and download it now
November 27th, 2008 7:24pm

Hi, Thank you for your response. After checking the network traces, I found that RDP worked fine in the works.cap, however, RDP was found failed the connection in the dontwork.cap since there was no response from the remote computer. I also understand that the following error was found in the Event Log on the Windows XP computer: Event ID:50 Event Source:TermDD Event Description:The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client. Based on the current situation, please perform the following steps to continue troubleshooting the issue: NOTE: please ensure that the registry has been successfully backed up. 1. Start Registry Editor. 2. Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\Parameters 3. On the Registry menu, click Export Registry File. 4. Type exported-parameters in the File name box, and then click Save. NOTE: If you have to restore this registry subkey in the future, double-click the Exported-parameters.reg file that you saved in this step. 5. Under the Parameters registry subkey, right-click each of the following values, click Delete, and then click Yes to confirm the deletion: Certificate X509 Certificate X509 Certificate ID 6. Quit Registry Editor, and then restart the computer. Hope this helps. Thanks!
November 28th, 2008 12:20pm

Hi again, and thanks for your reply.I got a bit confused regarding what to delete, since I did not find the keys you mention above. So I tried to delete every key under the "parameters" folder (there were only two). I'm guessing this wasn't what I was supposed to do, as it still doesn't work. However, if it makes any sense - it did now take an full hour before I was refused connection, against the normal 10 or 15 minutes.I'm starting to think my computer is haunted Also, I discovered something that might be of importance. If I only open the SSH tunnel via putty, I can connect and reconnect for as many times I want, and for as long as I want. So it seems that the RDP-connection somehow blocks my connection towards the XP-server.I see that I have forgot to mention that I can always connect to my 2k8 server by RDP, but as mentioned, it's on the same LAN as my workstation.Again, thanks a lot for your time.
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2008 2:30pm

http://technet.microsoft.com/en-us/library/cc775262.aspxSeems to have fixed the issue. It's more or less what you say above, only that the fix was on the client side - not the server. Thanks again for your time Edit: No it hasn't. I'm going nuts here, all logic has failed. 2nd edit: Well, now I was suddenly able to connect again. So, it works - sort of.3rd edit: Okay, so - it does not work. However, I discovered that my laptop with Vista Home don't connect either. Hence, it seems it's a issue with Vista to XP connection.
November 28th, 2008 10:18pm

Hi, Based on the current situation, please try the following suggestions: 1. Please ensure that all the latest updates has been applied on the Windows XP computer. 2. This issue can also be resulted by the factor that some third party security software or firewall blocked the Windows XP being accessed. Lets perform a Clean Boot to check our issue. Clean boot on Windows XP ================ 1) Click "Start", click "Run", and in the "Open" line, type in "MSCONFIG" and click "OK". 2) Under the "Service" tab, check "Hide All Microsoft Services", and then click the "Disable All" button. In this way, we can disable all the services which belong to third-party programs. 3) Under the "Startup" tab, click the "Disable All" button. 4) Click "OK". 5) Choose "Yes" to restart the computer. 6) Check "Don't show this message or launch the system configuration utility when Windows starts". NOTE: we can go back to normal boot by running msconfig again and checking on Normal Startup in the General tab. In the Clean Boot Environment, the third party services and applications are disabled, please try to access the Windows XP computer from the Windows Vista computer again to see if it helps. If the issue persists after the suggestions above, please also check our issue and collect the needed information: 1. Please use another computer which is not installed with Windows Vista to re-connect the Windows XP computer to see if it works. If it works, please go back to the problematic Windows Vista computer and try again. 2. Please execute the following from elevated command prompt on the Windows Vista computer: telnet XXX.XXX.XXX.XXX 3389 (Note: The XXX.XXX.XXX.XXX is the IP Address of the Windows XP computer) After running the command, please let me know if it is successful. If any error receives, please give me the exact error message. 3. Please capture a screenshot on the error message when re-connecting the RDP session via the Windows Vista computer fails. Thanks!
Free Windows Admin Tool Kit Click here and download it now
December 2nd, 2008 2:41pm

Hello again.Tried the suggestions above, none succesfull. I tried to connect to the XP-server from a computer running Ubuntu 8 today, worked fine - hence, it's becoming clear that this is a issue with Vista to XP only.Error msg from RDP connection is the same, "Can't connect to the remote computer (...)" - so no point in a scrn shot.Telnet is the same: Connecting to myip.dnsalias.com ... Could not open connection to the host, on port 3389: Connect failed.
December 4th, 2008 6:09am

Hi, I checked the thread again and noticed that the RDP works when only opening the SSH tunnel via putty. Therefore, I suspect that this may be related to this issue. May I know how you connect the local computers to the remote Windows XP computer and if there are some specific settings? Meanwhile, please also check the following at this time: 1. Please try to connect to the Windows XP computer without using the SSH tunnel. 2. If possible, please take the problematic Windows Vista computer to the network where the Windows XP computer locates, and then test if everything works. Please let me know the results. Thanks!
Free Windows Admin Tool Kit Click here and download it now
December 5th, 2008 1:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics