Couple of things come to mind.
#1. Play with adding/removing the public IP from the VPN interface. If you don't have it in there the logs may show ip spoof attacks and you can't get traffic across. #2. Make sure under Network Rules the vpn network on both sides is set to route not nat #3. Make sure you have a rule, I like to start with all outbound traffic, put both sides of the tunnel in from and to. #4. Goto logging and you will see real quick what the problem is. From: John A. Shaw-Miller [mailto:[email protected]] Sent: Sunday, July 12, 2009 2:07 PM To: NT System Admin Issues Subject: ISA Woes! Hi all, Wonder if any of you can help me with an ISA related issue (or point me in the right direction of what to do as I have now exhausted my google-fu) Site A: "STC" Internal Range: 172.16.50.0 - 172.16.50.255 Subnet: 255.255.255.0 External IP: 82.153.xxx.xxx Site B:"BUD" Internal Range: 172.16.100.0 - 172.16.100.255 Subnet: 255.255.255.0 External IP: 82.203.xxx.xxx STC can ping ANY machine on the BUD network not a problem and AD can do what it needs to so that it can replicate BUD cant ping ANYTHING on the STC network Both fresh installs of ISA 2006 Enterprise in their own Arrays I have followed the items on isaserver.org and multiple other places, but they just don't appear to want to route. Any clues? Thanks in Advance. John ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
