Unable to ping internal LAN after VPN
- This topic has 10 replies, 5 voices, and was last updated 9 years, 6 months ago by .
Viewing 1 post (of 1 total)
Viewing 1 post (of 1 total)
You must be logged in to reply to this topic.
Home › Forums › Server Operating Systems › Windows Server 2008 / 2008 R2 › Unable to ping internal LAN after VPN
OS: Windows Server 2008 R2 SP1
Role: RRAS
NIC: 1
Domain: No (Standalone)
Hello
I have searched around the net for other users who have had similar issues as I am experiencing now, but I was unable to gather the actual resolutions to the problems and apply them to mine. So here I go.
I can successfully establish VPN connections but once the connection is established I am unable to ping anything in the internal LAN, that includes the gateway and the VPN server both by DNS or by IP.
I have noticed that once a VPN connection is established in ipconfig there is no gateway retrieved, but there is a correct IP address set on the same subnet as the router and other clients.
On the client which is connecting to the VPN server I have set the “Use default gateway on remote network” option and still no luck.
The VPN server lies behind a home router (ASUS WL600g) with all of the VPN ports (1723, 500, 1701) and presumably the other protocols such as GRE pointing to it.
The firewall is disabled on the VPN server and I am able to ping the gateway and other clients on the network from it.
As there is only one NIC do I have to configure NAT on the VPN server?
Do I have (or is it recommended) to have the VPN IP range on a different subnet?
Do I have to manually route the traffic between the two IP subnets on the router?
Regards
You must be logged in to reply to this topic.
Find out more about our cookie policy here.