Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


VPN - How does the client become a part of the private network?

  • Please log in to reply
1 reply to this topic

#1 kaidranzer


  • Members
  • 1 posts
  • Local time:06:35 PM

Posted 06 April 2016 - 12:44 PM

I don't think this question has been asked here before because I've searched for an answer but couldn't find it:


Assuming we have a VPN connection (site-to-site or client-to-site) from site A to site B - if a machine in site A connects to site B, is it necessary that it becomes a part of the site B network? i.e. can it access the same local resources like shared drives, printers, etc that local machines in site B can?


If so, how does this work? Nothing that I know about VPN covers this aspect of it. VPN is supposed to provide you a safe/secure route from site A to site B through the internet so that you don't need to use a leased line to transfer data securely. Where does local machines in Site A getting the same network level access as local machines in Site B come in? Don't see any VPN protocols having anything in their specifications/implementation to support this? How does this happen?


Also, do local machines in Site A get a site B IP address assigned to them like site B local machines do?


BC AdBot (Login to Remove)


#2 Kilroy


  • BC Advisor
  • 3,461 posts
  • Gender:Male
  • Location:Launderdale, MN
  • Local time:11:35 AM

Posted 06 April 2016 - 01:54 PM

Here are the basics. We'll consider machine A is a VPN client. It will use VPN to connect to network B.

Machine A will have a multiple IP addresses. It will have an IP address for its network card that is on its current network, for example. Then it will have an IP address for its VPN adapter when it is connected to network B, that IP address will be on network B, for example. If you went to WhatIsMyIP.com while connect to network B via the VPN you would get the public IP address for Network B, 216.583.192.99 for example

Once you connect machine A to network B with the VPN it is as if the machine is on network B, so you will have all of the rights and privileges you would have if you were directly connected to network B.

You can take a listen or read of Security Now! - Virtual Private Networks (VPN): Theory - Episode 14. I've found Steve Gibson's explanations very good and most, especially the early episodes of Security Now!, lay a good foundation for understanding how things work. There are a couple more VPN related podcasts on that page that you might be interested in also.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users