Remote Desktop Connection issue

[edj002]

I recently upgraded my machine from Vista Ultimate to Windows 7 Ultimate and since then have been having issues connecting to any machines on my network via a remote desktop connection. Prior to the upgrade, there were no issues and I could connect just fine.

I am able to browse the other machines via windows explorer and can ping them as well, so it doesn't seem to be a connection issue. The machines that I am attempting to remote into are windows server 2003 and 2008.

Essentially what happens is once I open the remote desktop client, enter the name of the machine, then hit connect, the client says "configuring remote session", the new window opens, then nothing happens. The window for the remote connection freezes, and I have to kill it with the task manager.

Any ideas what the issue could be, or anyone else have similar problems?

 

[sup3rsprt]

so this is maybe due to the fact that you did upgrade rather than a clean install.

try another remote desktop client such as UltraVNC, TightVNC, or Dameware NT utilities.

 

[Skyman]

Configuring Remote Session

I'm seeing the same problem here. UltraVNC works OK.

Connection is riding a Cisco AnyConnect pipe.

Don't see the problem all the time. I can ping the remote servers with no problem.

Connecting via UltraVNC and opening TS manager shows that others have successfully connected.

 

[septprince]

I recently upgraded my machine from Vista Ultimate to Windows 7 Ultimate and since then have been having issues connecting to any machines on my network via a remote desktop connection. Prior to the upgrade, there were no issues and I could connect just fine.

I am able to browse the other machines via windows explorer and can ping them as well, so it doesn't seem to be a connection issue. The machines that I am attempting to remote into are windows server 2003 and 2008.

Essentially what happens is once I open the remote desktop client, enter the name of the machine, then hit connect, the client says "configuring remote session", the new window opens, then nothing happens. The window for the remote connection freezes, and I have to kill it with the task manager.

Any ideas what the issue could be, or anyone else have similar problems?

Beside entering the computer name you also have to enter the username and password( if available)....

 

[lavanyanaren]

Same problem. I am able to ping the servers. Using sonicwall vpn. Downloaded the latest version of the client software with no luck. Please help.

 

[BulletproofSean]

I too am having this issue. Fresh install of Windows 7 Ultimate x64, only started happening today. No clue what may have happened.

I rebooted, I was able to RDP into other hosts on my network for a little while, then it quit again.

 

[BulletproofSean]

I too am having this issue. Fresh install of Windows 7 Ultimate x64, only started happening today. No clue what may have happened.

I rebooted, I was able to RDP into other hosts on my network for a little while, then it quit again.

My issue turned out to be sound drivers of all things, more accurately an IDT Sound driver utility that I installed from the Dell website for my Latitude XT2 laptop.

It was a funny problem, but in the end was causing all of the following:

1) anything flash-based to crash
2) any game requiring sound would crash
3) the sound mixer applet would hang each time I clicked the volume icon
4) RDP client would hang at "Configuring Remote Session", possibly because during that process the RDP client would attempt to connect the sound device with the remote machine, causing it to hang...or something?

Anyway, since removing this sound driver-related utility, all of the above problems have gone away.

 

[superdave]

Great catch on the sound driver. I think there's a bug here somewhere.

I have a fresh install (x64), no sound driver issues (at least non apparent), and was running into this same issue. On a hunch from the post above I disabled remote audio (via the local resources tab), and the hang went away.

Hope this helps others...

Dave

 

[LordGlencairn]

Guys

Any resolution here of the original issue, seems very similar two my own problem and would be grateful to learn from the experience?

Julian.

 

[grkelsey]

I resolved the issue by disabling remote audio as well.

 

[Aneesh]

Issue solved

When I choose the option 'do not play' in Remote Audio Play back, I was able to connect to remote machine without any issue.

Thanks for the hints.

 

[Seth Wegner]

Another possible cause

When searching for a cause for the following condition, I found the following. For the next hapless searcher: Connecting to a Windows 2003 Terminal Server from Windows 7 or Vista, 32 or 64 bit, and the screen hangs during login. Remote Desktop Freezes When Connecting Through Windows Vista | i.nconspicuo.us -through-windows-vista/ 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: 1. I had to create a new shortcut on the desktop. Enter the command "cmd" as the shortcut command. 2. Right-click on the shortcut and select "Run as Administrator". This will open up a DOS window. 3. Enter the following command netsh interface tcp set global autotuninglevel=disabled Here's another version of how to disable auto-tuning as seen on ComputerBits 1. Open up an Elevated Command Prompt 2. Enter the following command to disable auto-tuning netsh interface tcp set global autotuninglevel=disabled And if you find that disabling auto-tuning doesn't fix your problem, you can turn it back on as follows: 1. Open up an Elevated Command Prompt 2. Enter the following command to enable auto-tuning netsh interface tcp set global autotuninglevel=normal And if you'd like to just view the states of your current TCP parameters, you can use this command: netsh interface tcp show global

 

[haridsv]

My issue turned out to be sound drivers

Thanks for the tip, mine turned out to be sound as well. Once I disabled remote sound, I was able to get the desktop.

 

[spindrift]

When I choose the option 'do not play' in Remote Audio Play back, I was able to connect to remote machine without any issue.

Thanks for the hints.

I also was able to resolve this problem by disabling remote sound. Thanks to everyone who posted the solution.

The strange thing is, though, I think the problem was with the local pc's sound, rather than that of the remote computer. Once I had got the remote desktop working with no sound, I thought I would just check the local PC's sound by double clicking on the Speakers icon in the bottom right-hand corner. For some reason, that program hung and it appeared that there was a problem with the sound driver. I restarted the local pc, having to force close a background task, after which local sound was ok again. I was then able to change the RDP sound options to "Play on this computer" and the RDP connected ok.

I've had the occasional problem with sounds not playing on my Dell Studio 17 laptop, particularly following Windows updates, and I know there was an auto update when I switched off last Thursday evening (I hadn't tried the RDP since then).

 

[coqui3l]

dang digiddy

I had this same issue and refused to believe that the fix was to turn off sound setting. Incredibley, it worked! I created a user account with 7forums just to share the joy!!! Tks.

c.

 

[seth500]

It does work but all be damned. I still prefer teamviewer though I can do more with it.

 

[Layback Bear]

Thanks dang digiddy !! I have no idea how that solved the problem. How and where did you change the sound settings?

 

[coqui3l]

@LayBack Bear

Hey Bear,

It's somewhere on the first page of this thread.

 

[coqui3l]

spoke 2 soon

The thing is hanging again and that's with the sound setting off. I've even disabled some other stuff but no dice.