asked on
Gateway conflict - when VPNing in
Small Business gateway IP conflict when VPNing in
We have a client that started out about 18 years ago with 7 employees, and peer to peer. At that time using a VPN client was not that common, at least not for this client and often cost prohibitive. Since then they have grown to 50 employees, 5 virtual servers an vSphere 5.x host, possibly VOIP (I have to find out), and a few devices with static IP addresses. The Internet service providers in the area at the time were not using the same gateway on their devices for the home networks, in fact most individuals had to provide their own routers and the ISP only put the modem in place.
What we have in the office is a gateway of 192.168.1.1. Over the years the hardware provided by the ISPs (their default gateway ip address for the home networks is often the same.
We have been using Netgears FVS-336V series devices for router/and for VPN. We are phasing these out, and no longer supported, going to Sonicwall it looks like.
We have remoted into a few employee’s homes and changed the default gateways on their home network to I would say technically a class B address 172.16.120.1 with a 24-bit mask. When we have done so, it eliminates the conflict with the gateway in the office. Needless to say, VPN works fine when it is changed.
My first question is - is there a way to prevent the routing conflict if both the internal gateway at the office is the same as the home user's gateway? I am thinking not.
That being said would you guys agree with going with say 10.170.1.1 with a 24 bit mask? If we implement a new router Sonicwall, change it to the new addressing scheme, does anyone foresee any issues changing the address on the Windows 2012 Domain controllers, file servers etc DNS/DHCP range,
Thoughts/ideas? Thanks guys!
We have a client that started out about 18 years ago with 7 employees, and peer to peer. At that time using a VPN client was not that common, at least not for this client and often cost prohibitive. Since then they have grown to 50 employees, 5 virtual servers an vSphere 5.x host, possibly VOIP (I have to find out), and a few devices with static IP addresses. The Internet service providers in the area at the time were not using the same gateway on their devices for the home networks, in fact most individuals had to provide their own routers and the ISP only put the modem in place.
What we have in the office is a gateway of 192.168.1.1. Over the years the hardware provided by the ISPs (their default gateway ip address for the home networks is often the same.
We have been using Netgears FVS-336V series devices for router/and for VPN. We are phasing these out, and no longer supported, going to Sonicwall it looks like.
We have remoted into a few employee’s homes and changed the default gateways on their home network to I would say technically a class B address 172.16.120.1 with a 24-bit mask. When we have done so, it eliminates the conflict with the gateway in the office. Needless to say, VPN works fine when it is changed.
My first question is - is there a way to prevent the routing conflict if both the internal gateway at the office is the same as the home user's gateway? I am thinking not.
That being said would you guys agree with going with say 10.170.1.1 with a 24 bit mask? If we implement a new router Sonicwall, change it to the new addressing scheme, does anyone foresee any issues changing the address on the Windows 2012 Domain controllers, file servers etc DNS/DHCP range,
Thoughts/ideas? Thanks guys!
Windows Server 2012VPNSonicWall
Last Comment
Seth Simmons