• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 991
  • Last Modified:

Remote Desktop Freezes after a few seconds

Hello. Whenever I connect to remote server through Remote Desktop Connection, it connects but after a few seconds it freezes. I have tried connecting to it on two different computers but the same thing happens. I can connect to other remote computers but this specific one has this problem. What's odd is that I can connect to it through an Android phone app called RD Client, but just not through Remote Desktop Connection.

I have tried disabling the audio and printers in the Local Resources tab, lowered the resolution and changed the connection settings (I have a 50mbps connection so that shouldn't be an issue), but nothing has worked so far. Any help will be greatly appreciated!

Both my server and my local computer uses Windows 10 x64.
0
Naeem Khan
Asked:
Naeem Khan
  • 9
  • 8
1 Solution
 
McKnifeCommented:
So you tested this from 2 different win10x64 (let me call those A and B), both tried the same target (call it C) and both freeze?
I use RDP win10->win10 very frequently. Never ever froze.
Please retry with clean machines or from A to B this time.

Most probably it's some weird effect that is due to 3rd party software or driver problems.
0
 
Naeem KhanAuthor Commented:
Hello McKnife. I have tested it from 3 different machines. My own laptop that didn't manage to stay connected after initial connection. Then 2 more machines (A and B) didn't manage to stay connected to the target (machine C) either.

I must clarify that I have updated to the latest version of Windows on my Laptop and the target (machine C), after which this problem has started. I can connect to ANY other machine using RDP on all these computers (my own laptop, machine A and machine B). The only problem I'm getting is when connecting to the machine C.
0
 
McKnifeCommented:
Well, either something is broken on C (speaking of windows' internals) or you have some software on C that is simply malfunctioning/interfering with RDP.

I would try and do an inplace upgrade to 1607 (like you already did) again in order to repair it.
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
Naeem KhanAuthor Commented:
Thank you for your answer.  I do think so that might be the case, since I restarted the target machine when it was taking a long time to update (I didn't realize it was still updating).

I must clarify that I do not have direct access to the target machine. The only way I can access it is through RDP. Will I still be able to do an in-place upgrade?
0
 
McKnifeCommented:
Sure, you will. I upgraded many machines using RDP. Even Bitlocker (if enabled) will be automatically suspended. The machine will of course reach a point when it has to reboot and then, depending on the speed and size of your installation, it might take up to an hour until you can reconnect to it. If it is still an hdd, it might take even longer.
0
 
Naeem KhanAuthor Commented:
Alright, that sounds wonderful! I'll give it a shot. Thanks a lot!
0
 
Naeem KhanAuthor Commented:
Well, even after that it's still the same. It's freezing after a few seconds of connection.
0
 
McKnifeCommented:
Update drivers, especially graphics driver. Uninstall all network protection software (AV, firewalls) and restart.
1
 
Naeem KhanAuthor Commented:
Hello. All the drivers are up to date and there are no 3rd party anti virus or firewall softwares installed. I have double checked it but still there's no progress towards the solution.
0
 
McKnifeCommented:
It is very rare that I have to surrender, but this time, I would. Do you have a backup/image of a working state?
0
 
Naeem KhanAuthor Commented:
I checked the device manager and there was some sort of "sensor" device that had no drivers. I deleted that and now it's working fine. Thanks for all the help!
0
 
Naeem KhanAuthor Commented:
I checked the device manager and there was some sort of "sensor" device that had no drivers. I deleted that and now it's working fine. Thanks for all the help!
0
 
McKnifeCommented:
You deleted it and on next reboot, it didn't get re-detected? That would be strange. Please do a reboot and report the behavior to me.
0
 
Naeem KhanAuthor Commented:
I did a reboot just now and it didn't detect that device. I am able to use RDP as normal now though after I deleted it. If I knew it'd fix the error, I'd have taken a screenshot of it.
0
 
McKnifeCommented:
:-) What a killer device...
1
 
Naeem KhanAuthor Commented:
Haha indeed. Well at least my issue is resolved. Thanks a lot for all the help. I didn't have to reinstall the Windows and start from the beginning. You are a life saver. I appreciate the help!
0
 
McKnifeCommented:
Very welcome. I see strange issues like this very often. Everyday a new big laugh. Or big outcry :-|
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 9
  • 8
Tackle projects and never again get stuck behind a technical roadblock.
Join Now