1. Windows 10 Home Remote Desktop Not Working

Mar 06, 2018  RDP was initially working when connected at HQ location however the computer was not able to RDP from itself to other computers, after moving to a branch office with RODC we were not able to RDP to the Windows 10 computer. I am currently having issues with sound redirection while using remote desktop connecting to a Windows 10 Pro Creators update host. I am able to connect using RDP, however the hosts sound is not transmitted to the RDP session. Legacy of the void campaign units 2. I can see the 'Remote Sound' icon in the tray, and it shows when audio is playing with the volume bar. Things I have tried.

Remote Desktop wasn't working for me here all the things I did to troubleshoot and get it working:. Enable remote desktop in settings.

Control PanelSystem and SecuritySystem, Click 'Remote Settings' on the left side. Verify my port forwarding settings were properly forwarding to my computers local IP address.

Windows 10 Home Remote Desktop Not Working

run 'cmd.exe' and then type 'ipconfig'. Find your IP from that list. Make sure your firewall settings are open. Go to 'Control PanelSystem and SecurityWindows FirewallAllowed apps'. On the left, click 'Allow an app or feature through Windows Firewall'. Click 'Change Settings'. Find 'Remote Desktop' in the list and make sure both 'Private' and 'Public' is checked.#3 is what ultimately got it working for me.

I was finally able to get mine working. Not sure if it was one of the updates that got it working or, I saw under settings there was another area to activate Remote Desktop connections, not just under device manager like in previous OS's.In my case it was under ALL SETTINGS - NETWORK & INTERNET, then I had to click on ETHERNET, then in window click my ETHERNET CONNECTION ICON, then you will see an option to allow your device to be discoverable, once I turned that on I was able to doRemote Desktop connection to my system.Hope this helps.

Hi bc,Let's confirm some situation.Did you talk about one computer installed Windows 10?And at HQ location, this Windows 10 cannot connect to another computer via RDP, right? What if reverse?In the RODC office, other computer cannot connect to this Windows 10 via RDP, right?Please follow this general guide to troubleshoot by yourself firstly:Frequently asked questions about the Remote Desktop clientsPlease remember to mark the replies as answers if they help.If you have feedback for TechNet Subscriber Support, contact. Yes, the workstation is windows 101. When at HQ I was able to RDP from domain, however the workstation could not rdp outdomain PC - Windows 10, Windows 10 -/domain PCDid they in the same network?Did Windows 10 join domain?2. When at branch office with RODC we are not able to RDP from HQ.HQ computer -/ Windows 10 in RODCChecked everything in the guide you referred me to.

Is it possible there is an issue with a certificate?Please be aware that they must be in the same network to connect with RDP or using VPN.Please remember to mark the replies as answers if they help.If you have feedback for TechNet Subscriber Support, contact. Hello,I recently had a lot of problems trying to connect with RDP.Used to work fine until I updated to a new work computer, then couldn't connect to it remotely.

I could get to the login screen, but failed credentials.After trying all suggestions here and elsewhere, the solution came down to a simple one (Doesn't it always.) - during setting up the new PC, rather than creating myself up as a new user, I just renamed the default 'User' account to 'MyName', set the password,and proceeded to install programs etc.This worked perfectly fine for everything; except RDP it seems. Trying to remotely log in as user 'MyName' eternally failed.Then I eventually noticed under c:users there was no c:usersMyName profile.

My whole profile was still under the original c:usersuser directory.So I tried logging in as 'User', but with 'MyName' password. Worked perfectly.Then it became a bit of a process, having to create a new user MyName, shift all data files for mail etc. Over to the 'new' user, but at least I can now remotely log in as 'MyName', and possibly prevent other quirky situations in future.Also another check is to define what is remote - if you are remoting on the same LAN (Say via wifi with your mobile) then the ip address is the local ip of the 'remote' pc. If you are WAN (From home say) 'remote', then you need the WAN address of your remotePC, and port forwarding through the modem to the local ip.I'm no pc expert but hope these comments help.Mr swas.