H
Have_I_Mentioned_I_Use_Arch
Guest
I have a new workstation running Windows 10 64 build 19041.508. I am unable to use RDP to connect to other workstations. I have attempted to connect to multiple different servers, all of which I am able to connect with from other devices on the same network using the same RDP file/settings. Upon clicking connect the dialogue box hangs on "configuring remote session" before stating "This computer can't connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator".
I am certain it is not an issue with the firewall/VPN/server, as I have other devices with the same configuration functioning properly, using the same user account for the VPN. This issue occurs prior to authentication, as if I do not provide a username I am never prompted for one.
I have followed all of the troubleshooting on this page and all I could find online.
Continue reading...
I am certain it is not an issue with the firewall/VPN/server, as I have other devices with the same configuration functioning properly, using the same user account for the VPN. This issue occurs prior to authentication, as if I do not provide a username I am never prompted for one.
I have followed all of the troubleshooting on this page and all I could find online.
- Attempted to connect to multiple servers
- Uninstalled all antivirus and disabled windows firewall
- Disabled all shared resources, including disabling audio
- Lowered resolution to 640x480 with 16 bit color
- Ensured there were no saved credentials
- I have ran all available windows updates
- SFC /SCANNOW
- CHKDSK
- I am on a "private network"
- Disabled persistent bitmap caching
- If server auth fails it is set to warn me
- Uninstalling all vendor software (Lenovo Vantage)
- Uninstalling Realtek drivers
- Deleting the certificate, restarting service, confirming certificate was re-created.
- Renamed C:\ProgramData\Microsoft\Crypto\RSA rename "MachineKeys" to "MachineKeys_backup", then restarted the service as before
- Ensured \AppData\Local\Microsoft\Terminal Server Client\Cache was empty
- Created a new windows profile
- Succesfully can telnet to the IP addresses that I am unable to use RDP to connect to
- Ran PS command Test-NetConnection <device_ip> -Port 3389 -InformationLevel Quiet which returned "True"
- Verified port number in "Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" is 3389/d3d
- Created DWORD value 1 at HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\RDGClientTransport
- Checked registry key Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\fDenyTSConnections and ensured value was set to 0
- Running netstat -ano | find "3389" to see if there are conflicts. There are none. Note: While I am connecting I can see a connection established withe the remote server, however, RDP still gives me the error and the connection is broken/no longer shows up in netstat
- Appended the line "enablecredsspsupport:i:0:" to the RDP file
I am sure I have attempted a handful of other fixes, any input would be appreciated.
Continue reading...