Remote Desktop works for my local network but not outside my local network

Anonymous
2023-11-07T19:26:56+00:00

My old home computer worked fine with remote desktop both in and out of my local network. I bought a new home computer with 11 pro, set up the remote desktop the same as in past and exactly as instructed and it works in my network, but does not work outside my network. I have the correct computer name and correct Pv4 IP address. When I try to connect outside my network with my computer name it says it can't find that name in the network. When I try to connect with my pv4 IP address it says I have been disconnected because another user has accessed my computer error code 0x516.

I know remote desktop is enabled, I know I have the correct ipv4 address and computer name, I know my firewall will allow remote desktop. I have the same wifi router with port forwarding 3389 that still works with my old computer outside my network, but not my new computer outside my network.

Please help.

Windows for home | Windows 11 | Accessibility

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

19 answers

Sort by: Most helpful
  1. Anonymous
    2023-11-07T20:02:41+00:00

    Hi, I'm Elise, a fellow user like yourself and I'd be happy to help with your issue.

    It sounds like you need to also setup port forwarding for the new PC on your router, in this case you will need to use a different external port so you can tell the difference between the new and old PC.

    Then when you connect from outside the network, you would use the external IP address of the router with the new external port you have assigned in port forwarding.

    There is an article here which gives a bit of background on the process:

    https://learn.microsoft.com/en-us/windows-serve...

    If you are unsure on any of this, please let me know if you need any further assistance.

    Kind Regards,

    Elise

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-11-08T22:48:54+00:00

    Please let me know if you need any further assistance.

    If you let me know if you have made any further changes to our router config or firewall to account for the new PC, I can help further if needed.

    Kind Regards,

    Elise

    0 comments No comments
  3. Anonymous
    2023-11-09T04:01:50+00:00

    Hi Elise,

    Thanks for the reply. What you are writing does not make sense to me. I deleted my port forwarding settings for my old computer, and my old computer is no longer connected to the internet. My port forwarding specifies the exact name of my new computer and the exact ipv4 address for my new computer. That is how it will be specifically identified. Why would I need to use 3390 instead of 3389? Nothing is currently using 3389 and that port is used for remote desktop. I attached the error message I get when I use the remote desktop app. I get a slightly different and less descriptive message when I use the remote desktop that is built into the 11 operating system.Imageect.

    0 comments No comments
  4. Anonymous
    2023-11-09T09:29:04+00:00

    OK I understand, I was under the impression you were using both the old and new PC with port forwarding. In this case you are correct you don't need to change that configuration on the router.

    When you are connecting from external, you are using the external IP address for your connection?

    If that is all ok the first step I would take is to just disable and then re-enable Remote Desktop on your PC. This is often all that is needed to clear a lot of errors.

    0 comments No comments
  5. Anonymous
    2023-11-09T15:21:38+00:00

    I'm using the ipv4 address. I think that is the right one to use.

    I read the disable option online somewhere yesterday and tried that. I disabled my remote desktop, then restarted my new computer, then re-enabled remote desktop. No change. It gave me the error message I attached to previous reply.

    0 comments No comments