Jazzysmooth
IS-IT--Management
Hi,
I've been asked to come in and finish a networking project that another consultant left. The company has a Watchguard Firebox (I apologize, I don't know which model) and their local LAN is using 10.136.X.X addressing. The Firebox was initially handing out 10.136.X.X VPN addresses, but I changed it to private class B (172.16.X.X) to fix a problem getting to Windows 2000 machines. While the VPN IPs were in the same class A address as the local network, the VPN users were able to reach the Internet while VPNed in - they can't anymore. Even though I asserted that allowing this is basically creating a gateway into their internal network for hackers, they still want to allow it.
So my question is, does anyone know what needs to be done on the firebox to allow VPN users to access the internet?
I've been asked to come in and finish a networking project that another consultant left. The company has a Watchguard Firebox (I apologize, I don't know which model) and their local LAN is using 10.136.X.X addressing. The Firebox was initially handing out 10.136.X.X VPN addresses, but I changed it to private class B (172.16.X.X) to fix a problem getting to Windows 2000 machines. While the VPN IPs were in the same class A address as the local network, the VPN users were able to reach the Internet while VPNed in - they can't anymore. Even though I asserted that allowing this is basically creating a gateway into their internal network for hackers, they still want to allow it.
So my question is, does anyone know what needs to be done on the firebox to allow VPN users to access the internet?