Jeremy Hansen
Level 4 (1,914 points)
Servers Enterprise

Q: ARD cannot see remote clients over VPN

Hi all. I've found not been able to find an answer to this that works. I appreciate the help.

 

I have two networks, home and office, both online through a Time Machine router. I have set up a VPN server in the office. I can connect to it successfully from home, and can mount servers and can control the server computer in ARD. But, I cannot see any other machines on the office network unless I enter their IP directly, and even then I can't control them. I can control the server, and it can see and control the other remote machines. If I am in the office, I can see and control all the machines on that network.

 

The office network router is set to distribute addresses from 10.0.1.2-200. The home network is set to distribute addresses from 10.0.1.201-250. The VPN server reserves addresses from 10.0.1.250-255.

 

What am I missing? Thanks much.

Posted on Jun 10, 2016 6:49 PM

by Jeremy Hansen,Solvedanswer
Jeremy Hansen Jeremy Hansen
Level 4 (1,914 points)
Servers Enterprise
A:

I've found the answer. It turns out that it is merely the scanner in Remote Desktop that can't see any machines. If I switch over to searching by network range, they are all there.

Posted on Jun 22, 2016 3:29 PM

Close
Jeremy Hansen

Q: ARD cannot see remote clients over VPN

  • All replies
  • Helpful answers

  • by iToaster,

    iToaster iToaster Jun 12, 2016 5:30 PM in response to Jeremy Hansen
    Level 3 (739 points)
    Jun 12, 2016 5:30 PM in response to Jeremy Hansen

    for VPN to work correctly normally your networks need to be in different IP ranges

    you have everything in 10.0.1 range

    eg office network 10.0.1.xxx

    home network 10.0.1.xx

     

    This may be the reason you can't control machines.

    VPN usually requires the remote LAN to be on a different subnet/ip range

    if they aren't routing etc can get screwed up as VPN/router can't figure out where things are

     

    Try changing your home network to a different subnet/ip range e.g. 192.168.1.xx

  • by chocolate elvis,

    chocolate elvis chocolate elvis Jun 20, 2016 10:52 AM in response to iToaster
    Level 1 (8 points)
    Servers Enterprise
    Jun 20, 2016 10:52 AM in response to iToaster

    also check the ports TCP 3283 (management) and remote desktop TCP 5900 are open.

  • by Jeremy Hansen,Solvedanswer

    Jeremy Hansen Jeremy Hansen Jun 22, 2016 3:29 PM in response to Jeremy Hansen
    Level 4 (1,914 points)
    Servers Enterprise
    Jun 22, 2016 3:29 PM in response to Jeremy Hansen

    I've found the answer. It turns out that it is merely the scanner in Remote Desktop that can't see any machines. If I switch over to searching by network range, they are all there.