permanent vpn connection or tunnel
I have a client pc that would like to login to a domain at the main office. I got the vpn working. . And was able to join the domain but the problem is now that when the computer starts up of course the vpn isnt connected.
I have a client pc that would like to login to a domain at the main office. I got the vpn working.. And was able to join the domain but the problem is now that when the computer starts up of course the vpn isnt connected. So it cant see the domain. It can only see the domain controller when connected with the vpn. I have tons of reading material im just not exactly sure which is the best solution for my problem.. Before using vpn i tried resolving the domain to the wan ip of the domain. Something about this bothered me.. and when trying to do so it complained about a missing srv record. Which makes sense because active directory is tightly integrated into dns.. and unless the client computer is using the proper dns server it wont work properly. Any tips on where to go with this would help me. Im not afraid to read up on it. The best solution would be to have a permanent secure network connection between the client and the domain controller that allowed it to "see" everything on the network. Like a vpn.
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.