ISA 2004 behind VPN router can't browse remote network
Posted on 2009-05-08
A client of mine has D-Link 804HV VPN routers in 5 locations. The tunnels were established and working fine until we started adding ISA 2004 onto the servers at each location. There is still a need for the users to browse the remote networks, mainly just to copy some files occasionally.
Each location has different subnets on the external NIC's, I.E. main branch has 2 NICs (192.168.2.x for WAN and 10.0.0.x for LAN). The 192.168.2.x comes from the Dlink router. DHCP is not enabled on the Dlink..this is passed along from the DSL connection, rather than the public IP. There is no apparent way to have the public IP directly entered onto the WAN NIC. I believe this is the main cause of all the trouble, by the way.
One branch location has 192.168.7.x for WAN and again 10.0.0.x for LAN. The idea would be for a user at main office to be able to browse to 192.168.7.10 (server IP). Pings to any 192.168.7.x address from the main office don't ever go through.
RDP works fine thanks to some rule tweaking in ISA, but I can't seem to get network browsing functioning correctly.
Can anyone help me out here? I'd rather keep the D-Link's in place as added security.