• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

windows10 wont RDP to work PC.

OutHouse

Lifer
ok this is stupid and i cant find anything on the MS blogs. I was able to establish a VPN connection to our sonicwall VPN at work, authenticated, and enterened in my token. even have the connected icon in the taskbar. so i know i am connected.

but when I kick off a RDP session to any machine i get the error that that the remote machine is not available. :thumbsdown::thumbsdown::thumbsdown:

i know there is nothing wrong with vpn, i can get in with my droid and my laptop.

has anybody experienced this and know of what stupid setting i need to enable to get RDP connected?

firewalls are turned off.
 
Can you ping your workstation @ work? I've experienced cases with Windows 7 (not yet using 10 for work) where it would establish a connection, but not pass data through it properly. When it would happen, I wouldn't be able to ping an IP address on the inside of my work network.
 
Using Sonicwall VPN here too - worked fine for me though.

Did it prompt you to upgrade your VPN client? I got a prompt but haven't upgraded. I think if the client is too much newer than the VPN server, that can cause problems.
 
I'm having the opposite problem. Upgraded Win8 Pro + WMC to Windows 10 Pro, now I can't access my computer via RDP.

Tried from the stored profile on the official Microsoft Remote Desktop app for iOS. Tried from my Win7 Pro workstation. Can't connect. I routinely connected from my iPad and Win7 workstation multiple times per day and it worked fine before I installed Win10 on the host machine.

Remote Desktop is still enabled. I tried disabling and re-enabling. I made sure there was still an exception in the Windows Firewall. I haven't tried completely disabling the Windows Firewall.

Checked it out again when I got back home. Windows started treating the wired connection to my PC as a public network. Fixed that by toggling the "find devices..." option and it's working fine now.
 
Last edited:
Back
Top