Go Premium for a chance to win a PS4. Enter to Win

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

Remote desktop does not work with windows 10 upgraded computers

We have a single 2011 small business server, which is working fine. We use remote desktop both from outside the building and locally also.

All are working fine, apart from a couple of workstations we have just upgraded to windows 10 pro.

I cannot connect to either pc, internally or externally using remote desktop or OWA.

All of the settings seem to have come across OK from the Windows 7 config that we had in place, We can connect to OWA to check e-mail, but the remote connection option, displays the correct computer, but says it cannot find it when we try to connect.

I have tried using remote desktop locally with both the pc name and local IP address, and it still fails

I can see that many other people have had exactly the same problem, but I can find no fix for this.

Can anyone help, as we are desperate to be able to provide remote access for the couple of workers who access the computers we have upgraded to windows 10.

Any help would be very much appreciated.

1 Solution
Cliff GaliherCommented:
If you are on SBS 2011 then you need to instruct users to turn on compatibility mode in IE11 *and* add RWA to the "trusted sites" zone. BOTH of these steps are required for RWA to work on windows 10 (and 8.1 and 8.0.)
Michael ChisholmCommented:
1. Make sure your server is configured to accept remote access from clients with Network authentication.

2. It wouldn't hurt to check the firewall also as it may have been turned on during the upgrade. If you have it on turn it off for testing.

3. Test an RDP connection to a windows 7 system from a windows 10 system and make sure it is not only a windows 10 problem.  

4.  Post results
nigelbeatsonAuthor Commented:
This was FULLY working before we installed the windows 10 upgrade to 2 of our workstations. The rest still running on windows V7 pro, still work perfectly.

I have change site https://remote.comainname.co.uk to compatibility mode, and I have also added the url for the site to the internet  op[tions > security > trusted sites

I have tested it, but it still produces the following error >

screenshot of error
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

nigelbeatsonAuthor Commented:
I presume the above changes should be made to the client initiating the remote connection, and not the computer we are trying to remote into?
nigelbeatsonAuthor Commented:
do you mean on the client side?

I know how to add trusted sites to internet explorer, but how do we add rwa? I usually add a url

many thanks
nigelbeatsonAuthor Commented:
I can confirm that locally I can connect from a windows 10 computer to a windows 7 computer, but not from a windows 7 or 10 computer to a windows 10 PC.

windows 10 does not allow a remote connection either locally or externally using owa

many thanks
Cliff GaliherCommented:
Based on your screenshot, the site is not in compatibility mode. That is easily identifiable in the title bar by a "torn page" icon. As I said, *both* must be done for RWA to work.  And yes, it working perfectly in Win7 is completely normal. This is a result of RWA being written for older browsers, and when win8 (and newer) shipped, the new browser doesn't like the older site, hence the need for compat mode.

nigelbeatsonAuthor Commented:
I am sure you are right about this, but when I select the compatibility view settings to include the site remote.domainname.co.uk it just adds domainname.co.uk to the list, and no torn page appears in the address bar.

what am I missing?
nigelbeatsonAuthor Commented:
I seem to think that the compatibility mode torn page icon is not now displayed in IE11?? I can see our domain name is in the compatibility mode list, and the https://remote.domainname.co.uk is also in the trusted sites list, but It still produces the same error.

Any other ideas?

Thanks for your help.
David AtkinIT ProfessionalCommented:
Can you check on the client machines firewall to make sure that 'Remote Desktop- user mode (TCP-In)' and 'Remote Desktop- user mode (UDP-In) are allowed in the inbound rules.
nigelbeatsonAuthor Commented:
that was it! many thanks. not sure why this setting in particular would not be taken from windows v7 during the upgrade, but we are all working now.

many thanks to all.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

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