I confirmed I could ping the DNS server on the domain from the remote computer. I configured it like so:įrom here, I connected to the user through Teamviewer's VPN and via Remote Control.

So I set a persistent route on the remote computer to route all traffic to the 10/8 network to the VPN ip on *my* (the local) end 'route add 10.0.0.0 mask 255.0.0.0 7.154.200.11 -p'Ĥ) Add a DNS entry on both the Teamviewer and ethernet adapter of the remote computer to the DNS on one of the computers in the Domain (a 10.X.X.X address).ĥ) I downloaded and installed NAT32 onto the local computer. Since this user was in Victoria BC and I was in Calgary AB, I needed to find a way to connect their computer to our domain network so they could authenticate against our DC and then I could add their account to the local admin group.ġ) Using the local administrator account on the remote computer, install TeamViewer and set it to launch on Windows Startup.Ģ) Setup unattended access through TeamViewer and install the VPN client on the remote computer and my local computer.ģ) The network the remote computer was on was a .X and our network is a 10.X.X.X. Without the user account being from the domain and a local administrator account, Network Connect will not connect to our network. I did have the local administrator account password and could login with it, but the VPN technology we use (Juniper's Network Connect) requires local administrator rights to install it (which I was able to do) but is setup to verify that the user account is a domain user account.

We could not though, as the user was a domain user and the computer was not on a network with a domain controller. This should be an easy fix, just add the user to that group. We recently had a workstation that was sent to a user that didn't have the user in the local administrator group.

Teamviewer vpn not turning on