Link to home
Start Free TrialLog in
Avatar of EdMacFly

asked on

ISA 2006 VPN Connection

I've set-up a VPN connection using ISAs wizards and have managed to connect my laptop to the VPN and obtain an IP address via DHCP. I cannot however access any machines on the internal network nor has the DHCP given out the correct default gateway of the internal network, IPCONFIG shows default gateway as Any ideas what could be wrong?
Avatar of EdMacFly


As a further note, the machine that is connecting is a Windows 7 machine. Also, within the ISA Alerts, it appears that the VPN connection has triggered an IP spoofing warning.
Avatar of Mohamed Khairy
Did you create the firewall policy that enable the communication from VPN network to Internal network?

Also, Go to networking and tell me what is the network rule relation on the VPN network rule.

Both the rule and policy look the same as your screenshots.
Ok, make confirm that you can ping the internal network from the localhost.

Also, try to change the DHCP option on the ISA server to be taken from static address range.

I cannot ping from the VPN client. Should I try setting a static address or has that revealed the problem?
Avatar of Hisham_Elkouha
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
That's done it! Excellent. After connecting I could ping the ISA box using it's name but I could not ping the DC using it's name nor could I connect to it without using it's IP address. Any idea why that information is not getting through?
I can see from the previous steps that the error may be in the DHCP, you said that you can successfuly taking an Ip address from the DHCP and the error in the default gateway so we can make one more check on the DHCP options as follow:

Go to the DHCP and open the scope that you were assigned before to the VPN users and check the scope option for router ( optionn 003 ) and make confirm that the correct GW is available.

Also check the DNS setting on the DHCP scope options.
Right! I've checked those points and everything seems fine. I can now access internal resources so that is good and have also found that I can make an rdp connection to the DC using it's FQDN rather than just it's name which is fine.