Firebox X Edge MUVPN help needed

[aristobulos]

I am the network administrator for a church and am in need of assistance. It appears that Watchguard isn't willing to help me any further. We have a Windows 2003 internal network running active directory. All internet is directed through a gateway on a proxy server with an internal and external NIC card. The proxy server is on an XP professional box and is Win Proxy. The external NIC card is connected to the firebox which in turn is connected to the cable modem. After having set up the MUVPN settings for a user on the firebox itself we have installed the MUVPN client software and set it up. We are able to establish a successful connection allowing us to ping the firebox and the external NIC card. However we are unable to join the network or access any network resources or ping the internal network at all. I am desperate for some sort of idea here. Please help.

 

[MichaelDell]

If you can ping the external NIC on the Windows box that is behind the WatchGuard from an MUVPN client, but not any internal addresses that are behind the Windows box, then the problem is with the Win Proxy software.

Have you configured Win Proxy to pass the traffic you intended or all traffic since it is behind the WatchGuard?

 

[aristobulos]

I configured Win Proxy to allow IPSEC traffic through. Is there some other form of traffic that I should allow such as https?

Thank you greatly for your input.

 

[MichaelDell]

Please list your IP address configuration for all of the interfaces on the Firebox and the Win Proxy PC. On the public addresses, hide the first octet (Example: x.10.109.30 255.255.0.0) This will help to explain what is going on.

 

[aristobulos]

Firebox external interface is x.89.37.126
Firebox trusted interface is x.168.111.1
Win Proxy external NIC card is x.168.111.2
Win Proxy Internal NIC is x.168.0.15

thanks much

 

[MichaelDell]

You have two NAT devices working here. The MUVPN client reaches the x.168.111.0 subnet, but that is as far as it goes. Unless you were to establish a rule within Win Proxy (and I am not familiar enough with it to say on way or another) to route all inbound traffic from the MUVPN client's address that hits goes to x.168.111.2 inside to the internal network, you won't get anywhere.

If the Firebox has a built in DHCP, or better yet, just configure the Win2k3 box to be the DHCP server and get rid of Win Proxy. I don't see why you need it.

 

[pankajchawla]

You wil have to add a static route in the firebox
The gateway ip would be the x.168.111.2
Network for the route would be x.168.0.15 network