10 Apr
Posted by i.nconspicuo.us as Tech/Web
So ever since I installed Windows Vista, I’ve been having problems connecting to our Windows Server 2003 workstation through terminal services. Looks like I finally found an answer to the problem. After connecting to the server, I am able to see the desktop, but the connection typically freezes on this screen for about a minute with the following message:
The connection has been lost. Attempting to reconnect to your session…
Connection attempt: x of 20
Apparently this problem is because Windows Vista has a low initial setting on it’s Auto Tuning feature. What Auto-Tuning does is continually adjusts the TCP/IP receive windows size based on current (and changing) network conditions. It seems that many people have reported problems with auto-tuning causing various network timeout issues with some applications and routers. If you’re experiencing any of these problems, you can turn off Auto Tuning as described below.
Here’s what I did to fix this Remote Desktop Connection problem:
netsh interface tcp set global autotuninglevel=disabledHere’s another version of how to disable auto-tuning as seen on ComputerBits
netsh interface tcp set global autotuninglevel=disabledAnd if you find that disabling auto-tuning doesn’t fix your problem, you can turn it back on as follows:
netsh interface tcp set global autotuninglevel=normalAnd if you’d like to just view the states of your current TCP parameters, you can use this command:
netsh interface tcp show global
27 Responses
Petunia
April 14th, 2007 at 4:22 pm
1Wanted to drop a ‘thank you’- I work from home, haven’t been able to connect to the office w/my laptop since my Vista upgrade. Surfed around a bit this afternoon to see what I could find. Quick, easy fix, outstanding!
frank s.
May 16th, 2007 at 12:29 pm
2worked like a charm. thanks!
JLA
June 26th, 2007 at 5:58 pm
3You have restored my sanity! Thank you!
Jaye
July 9th, 2007 at 3:24 pm
4What was weird is that to some servers (win2k3), it was working fine, and I had no trouble, but certain ones I did.
This fixed the problem. THanks muchly.
Jayden
July 19th, 2007 at 1:05 pm
5I see this same problem with Windows XP. You know how I can resolve it
Robert
September 8th, 2007 at 6:13 am
6I have the same issue when connecting from Windows XP -> Vista Ultimate, and a wireless Dlink router between.
Brian Mair
October 1st, 2007 at 5:13 am
7Excellent results here. I’ve been coming very close to removing Vista in favor of XP over this and a couple of other annoying problems. Many thanks. Unfortunately, we remote desktopers will have for forfeit the benefits of Auto Tuning, whatever they might have been.
i.nconspicuo.us
October 1st, 2007 at 1:10 pm
8I haven’t yet missed out on any “benefits” of having autotuning enabled.
Let me know if you come across anything that is lost by disabling it.
Solved: “The connection has been lost. Attempting to reconnect to your session…” when attempting to access a Windows 2003 server from a Windows Vista Remote Desktop Session « the back room tech
October 8th, 2007 at 2:17 pm
9[...] when I thought all hope was lost (and dinner was on the table), I came across this post, which said to run the following from an elevated command [...]
Håkan
November 15th, 2007 at 7:27 am
10Fantastic, this has bather me a long time now and this solved the remoted desktop to win2k3 prob.
Thanx.
rob
November 16th, 2007 at 1:12 pm
11I had to stop and say thank you for this. Worked beautifully!
Tony
December 10th, 2007 at 3:45 pm
12Thank you so much. This totally fixed my problem, haven’t been able to connect since the new laptop came with Vista.
Peter
February 11th, 2008 at 7:05 am
13Thanks worked for both my connect to our server and to the windows xp workstation..
Thanks
Ed
February 20th, 2008 at 8:21 pm
14This did not work for me. I still get the: The connection has been lost. Attempting to reconnect to your session…
Connection attempt: x of 20
Any more options
Thanks
i.nconspicuo.us
February 20th, 2008 at 8:56 pm
15You know what… this doesn’t work for me either. I think it could either have to do with a networking issue (either at your location, or at the location of the remote computer) or someone has suggested to me that it is due to a lack of resources on the remote computer. Either way, I have not yet found a solution to my problem and I am getting very frustrated.
Marcel M.
March 18th, 2008 at 10:48 am
16For me a similar solution worked, see:
http://www.vesic.org/english/blog/networking/vpn-remote-desktop-vista-and-mtu/#comment-6827
netsh interface ipv4 set subinterface “Wireless Network Connection” mtu=1440 store=persistent
(presuming your wireless interface is called Wireless Network Connection
Rich S.
March 24th, 2008 at 8:34 pm
17Thanks a lot. This fix worked great!
Ed
March 25th, 2008 at 11:40 am
18I tried Marcel M.’s suggestion and still the same outcome…..
Mike Laskey
April 4th, 2008 at 3:06 am
19Thank you Marcel. It was driving me round the bend. Vista Remote Desktop would work wired connection to XP , but not via Wireless. Changing the MTU size of the wireless connection worked great. This should be a technet article…
Alex Chun
May 3rd, 2008 at 2:47 pm
20I started having this problem after I installed D-Link Xtreme N Gigabit Router Dir-655 ver 1.02. Above solution does not work for me. Could someon help? Thanks.
Randall F
August 26th, 2008 at 7:30 am
21Thanx much… you have no idea how long i’ve been pounding on my machine looking for a solution! Worked like a charm.
HF
September 3rd, 2008 at 2:54 am
22many thanks buddy – I was almost going to uninstall the “Vista” resources-hungry-beast and go back to xp, you saved me a lot of hours and the money I invested in the worthless vista pro
cheers
H
ecards
October 29th, 2008 at 8:45 am
23This is the best post I have read all year.
If I had one dollar for every minute I sat waiting out the freeze in remote desktop I’d be rich.
Thanks
Brian
January 9th, 2009 at 2:23 pm
24You saved me, and my client. thanks
miki
July 31st, 2009 at 12:30 am
25THANKS A MILLION !!!!!!
Jackson
January 17th, 2010 at 6:56 am
26THANK YOU SOOOOOO MUCH!
THIS WAS BOGGLING MY MIND, BUT YOUR TRICK FIXED IT PERFECTLY.
Ali Aziz
February 21st, 2010 at 11:00 pm
27Hi there,
well.. i do have the same issue.
am using Vitsa as a client to access the TS Win2003 Server ent edition.
in my case, whenever i try to connect to the TS, it takes long time until the user name n password window appears!
i tried the above mentioned way and it didnt work….
Other servers can be accessed easily without any trouble! AND without implementing the above??!!
PS. sometimes it works fine without any delay and sometimes it takes time.. , its not stable!
RSS feed for comments on this post · TrackBack URI
Leave a reply
Subscribe
Pages
i.nconspicuo.us friends
Meta
Sponsored Posts
Categories
Archives
Recent Entries
Recent Comments
Most Commented