J
jshapiro
For the second time in a couple of months, I've had a user call with an
IP address conflict. He is currently situated at a hotel, and his
hotel network connection gives him an IP of 192.168.2.x It just so
happens that one of our subnets is in the same range. When the VPN
tunnel is open, he can get to everything on our network but that
subnet. Although he gets correct DNS resolution from our DNS server,
anything bound for 192.168.2.x will route to the hotel network.
Unfortunately, our mail server and some other important resources, are
there.
It is obviously not practical for us to ask the hotel to change their
network addressing, and it isn't very easy for us to do it here. Short
of making a change at one end or the other, is there anything I can do
to work around this type of problem?
IP address conflict. He is currently situated at a hotel, and his
hotel network connection gives him an IP of 192.168.2.x It just so
happens that one of our subnets is in the same range. When the VPN
tunnel is open, he can get to everything on our network but that
subnet. Although he gets correct DNS resolution from our DNS server,
anything bound for 192.168.2.x will route to the hotel network.
Unfortunately, our mail server and some other important resources, are
there.
It is obviously not practical for us to ask the hotel to change their
network addressing, and it isn't very easy for us to do it here. Short
of making a change at one end or the other, is there anything I can do
to work around this type of problem?