Vpn

[n8236]

So here's the scenario:

You have a main office and a remote office. The remote office user has his machine setup for vpn'ing and mapping network drives when working away from the office.

The problem occurs when when he is vpn'ed in. It's tunneled into the main office, not the remote office he works in. So he's not able to map any of the remote office drives since the main and remote office is on two different subnets.

Main office network ID: 192.168.1.x
Remote office network ID: 192.168.4.x

So how does one fix this problem?

 

[varmit]

So here's the scenario:

You have a main office and a remote office. The remote office user has his machine setup for vpn'ing and mapping network drives when working away from the office.

The problem occurs when when he is vpn'ed in. It's tunneled into the main office, not the remote office he works in. So he's not able to map any of the remote office drives since the main and remote office is on two different subnets.

Main office network ID: 192.168.1.x
Remote office network ID: 192.168.4.x

So how does one fix this problem?

Might want to setup DNS server of the 192.168.1.x network to point the server name he is trying to connect to on the 192.168.4.x network. Or instead of the server name, use the IP address of the server. I'm also guessing that the Remote office is connected to the main office in some way, via Point-to-Point or something, otherwise its pointless. Otherwise there is not pathway from the main office to the Remote office.