RDP Initiating Remote Connection SLOW!!!!

[Matt_Brfc]

Hi All,

 

Strange question but one that is doing my head in at the moment!

 

Every time I RDP to 2003 server, XP Pro, Windows 7, Windows 8 host on our LAN RDP seems to hang for ages saying "initiating remote connection" at first I suspected this could be a DNS issues although Im informed that this is not the case as stale DNS records for my machine have been removed. However there only seems to be me with this issues (Windows 7 Pro host).

 

Any suggestions welcome?

 

Cheers

 

Matt

[MatthewL]

In the local resources tab uncheck the printers tab and see if that makes a difference also try it on a machine without the firewall on see if that makes any difference.

[Matt_Brfc]

Tried this earlier as in the past there have been issues with previous versions of RDP and the mapping of printer drivers but still having the problem.

[Tsonga]

Tried to RDP via IP instead of FQDN?

[Matt_Brfc]

Tried this before posting, both with host name and IP address still the same issue.

[Tsonga]

I assume you have tried multiple hosts?

[adrianjones]

Try This:

 

Remote Desktop slow problem solved

[Matt_Brfc]

I had come across this last week and gave it a try, unfortunately still no joy I'm afraid.

[Liam]

Have you seen the reg key disablerootautoupdate? Google it.. It speeds up rdp connections considerably Well initiating connection that is from a win 7 host.

I have the reg file if you want it

[Matt_Brfc]

Yeah if you could send me the reg file that would be good, cant rally find much relating to this and RDP.

 

Thanks

 

Matt

[Michael]

If it's just you with the problem there are several possibilities -

 

Something specific with your workstation. Logon as someone else and re-try RDP. If the problem's still there re-image your workstation if possible.

 

When you logon to another workstation, does the problem follow you around? If yes, it could well be a profile issue. Allocate yourself a new local or roaming profile.

[Matt_Brfc]

Hi Guys, tried the registry key fix which didn't resolve the the issue as well as creating a new user profile. This issue is also present using a different accounts both domain user and domain admin.

 

Matt

[andydis]

my first thought is try an alternative RDP client first to see if that sorts out the problem ( royal tS , remote desktop connection manager)

next i would rest all the options back to default on mstsc (in the advanced tab, connect from anywhere), make sure do not use an RD gateway is set.

Next i would run some networking tests ( are you on wifi or LAN)? ping , traceroute

[Matt_Brfc]

All of the above has already been done with no joy Im afraid.

[andydis]

are you on wifi or LAN

 

Hi Matt, wifi or LAN?

[Matt_Brfc]

LAN 100Mbps via Cisco switch to backbone of network tracert and ping responses seem fine.

[andydis]

i know its random but try a different ethernet port 1)on the cisco swicth 2) any other switch?

(eek running out of ideas) assuming your pc has no spyware / virii / nastys / enough RAM / network utilization is 99% lol

[Michael]

If it does the same with other domain accounts, you could try demoting the workstation and re-promoting to the domain. Failing that, it's imaging time I think!

[Matt_Brfc]

One of this firsts things i did was remove the PC from the domain and re-added it, still no joy.

[mac_shinobi]

Delete bitmap cache on your pc, ensuring to close down Remote Desktop / Terminal Services ( as in the app you use ) before doing the below :

 

is the person(s) windows username

 

If Windows 7 :

 

Navigate to the below directory ( need hidden files and folders showing as AppData is a hidden directory, obviously )

 

C:\Users\\AppData\Local\Microsoft\Terminal Server Client

 

Delete the folder named Cache

Windows XP :

 

C:\Documents and Settings\\Local Settings\Application Data\Microsoft\Terminal Server Client

 

Same again Delete the Cache Directory

 

Shot in the dark but thought it worth a try

 

Maybe check your Computer as far as

 

1. Flushing and re-registering DNS ( through command prompt run as admin )

2. Check hosts file and if need be reset to defaults

3. Last resort but maybe reset tcp/ip stack and winsocks ?

 

When you say a win 7 pro host, is this a windows 7 pc you are trying to rdp to or is the windows 7 pro host your pc ?

Edited January 23, 2013 by mac_shinobi

[Matt_Brfc]

thanks for this, unfortunatley still the same issue, Windows 7 is my PC

[mac_shinobi]

thanks for this, unfortunatley still the same issue, Windows 7 is my PC

 

Try this

 

 

http://blog.tmcnet.com/blog/tom-keating/microsoft/remote-desktop-slow-problem-solved.asp

 

In any event, I discovered that Vista's (Windows 7 as well) Receive Window Auto-Tuning could have issues on some networks. I really didn't want to disable Receive Window Auto-Tuning due to it's QoS, bandwidth speed/throughput, and VoIP quality benefits, but I had no choice. I use Remote Desktop all the time to manage 30+ servers. After disabling Receive Window Auto-Tuning, the "slowness" problem with mouse-clicks, keystrokes, and screen redraws went away. Problem solved! Woo-hoo!

Here is what you need to do if you have the same issue:

 

- Run a command prompt (cmd.exe) as an Administrator

- Type: netsh interface tcp set global autotuninglevel=disabled

Disable the autotunning feature in Vista completely, and fit and lock the RWIN receive window to default value 65536 bytes.

 

If you want to to re-enable it:

- Type: netsh interface tcp set global autotuninglevel=normal

 

In some cases you may need to use this command in addition to the above, but I didn't have to:

- Type: netsh interface tcp set global rss=disabled

 

Update! This command makes your network connection EVEN FASTER

Type: netsh interface tcp set global autotuninglevel=highlyrestricted

 

The reason is that this command will still "auto tune" your TCP connections, but not as drastically as 'normal' mode. It will allow the receive window to grow beyond the default value, but again it will do so very conservatively. In this mode, Vista will by default use RWIN (receive window) of 16,384 bytes with a scale factor of 2. I was browsing computers in my Network Neighborhood and trying to get to \\computername\c$ which was taking forever to load. I changed it to highlyrestricted and it was much faster. 'highlyrestricted' mode is my recommendation for the fastest network performance whether you are using Remote Desktop, Internet browsing, or doing SMB file copies across your network.

 

Now, because Receive Window Auto-Tuning increases network utilization of high-BDP transmission paths, the use of Quality of Service (QoS) or application send rate throttling is important for networks that are operating at or near capacity. So I'd like to get this feature working, which will require some network topology examination. I did read that Windows Vista supports Group Policy-based QoS settings that allow you to define throttling rates for sent traffic on an IP address or TCP port basis. So perhaps I can just disable auto-tuning for the RDP port 3389 and leave it on for all other ports.

 

I'm headed over to Microsoft's site which has some excellent resources on policy-based QoS. From my initial research it looks like you can configure some pretty nifty QoS policies. For example, you can specify a QoS policy with a DSCP value of 46 for a VoIP application, allowing routers to place those packets in a low-latency queue, or you can use a QoS policy to throttle a set of servers' outbound traffic to 512 KBps when sending from TCP port 443 (HTTPS port). In theory, I can set Remote Desktop to have "top" priority and give it all the bandwidth it needs. Heck, maybe I'll set just my IP address and my Remote Desktop port to have top priority on our network. To hell with the rest of my fellow co-workers! They don't need no stinkin' bandwidth. It's mine! All mine! http://blog.tmcnet.com/mtstatic/FCKeditor/emoticons/devil_smile.gif Now that I solved the slowness problem with Remote Desktop, it's time to head over to Amazon to check out their top Bluray deals of the week!

 

Edited January 24, 2013 by mac_shinobi

[rodsco]

Try this....

 

Fixing Remote Desktop Annoyances ~ What the.....?

[mac_shinobi]

@Matt_Brfc - Curious how you are getting on with this ?

[m25man]

Curious to know how you set up your LAN connections to the RDP server?

 

Do you use NIC bonding on the RDP Servers?

Do you use one NIC for LAN use by the RDP server and a second just for client incoming connections? A sort of in on one, out on the other sceanrio.

The latter has proven to be a much faster solution in some places.

Then there is the binding method Use Remote Desktop Services on multi-homed server: RDP, dual NIC