VPN connects, cannot ping network resources/no access

Question

_{Monday, October 1, 2012 7:52 PM}

Pretty sure it's a server side setting that was deleted, however I don't know where or what.  RRaS is running with a single nic, on a DC.  VPN connections have worked fine until this point.  A tech support call was placed to Microsoft for another issue, at some point I was asked if he could delete an entry, which was one of the IP addresses of the RRaS server, and I said yes not thinking.   I'm not sure if the machine should even have two ip addresses assigned to it, it only has one nic plugged into the network.

Currently users connect and authenticate, they are given ip addresses in the correct range/subnet, but cannot ping or access network resources.  I can see them connected in RRaS console running on the server.

Would an easy fix be to disable and reenable RRaS?  Should I delve deep into it and figure out what was deleted?

All replies (9)

_{Thursday, October 4, 2012 7:15 PM}

Bump

_{Friday, October 5, 2012 8:57 AM}

Hi,

Thank you for the post.

Try to restart Routing and Remote Access service. Or you have to disable RRAS and reconfigure your RRAS server.

If there are more inquiries on this issue, please feel free to let us know.

Regards

Rick Tan

TechNet Community Support

_{Friday, October 5, 2012 12:26 PM}

Restarting the service did not correct the issue, any idea what entry could have been removed to prevent access to the network? 

_{Monday, October 8, 2012 7:06 AM}

Hi,

1. Verify if enable IPv4 Router--LAN and demand-dial routing option.

2. Verify if enable Remote access connections (inbound only) option.

Regards

Rick Tan

TechNet Community Support

_{Monday, October 8, 2012 8:02 PM}

1) LAN routing only is checked. 2) Remote access and demand-dial routing is checked

_{Saturday, October 27, 2012 12:16 PM | 1 vote}

Hello kastle1! I have the same issue... have you manged to solve it?

Thanks!

Later Edit: For me the problem was the assigned IP address for the client. It seemed to be a valid IP address but for a reason that i can't explain it just wasn't usable. The solution was to right-click the server's name in Routing and remote access and select proprieties. Then, I went to IPv4 tab and assigned a static address pool for clients.

After that, another issue was that some clients, while connected to VPN, were unable to browse the Internet. This one was solved by un-checking the "use default gateway on remote network" option in VPN connection proprieties.

Good luck!

_{Tuesday, October 30, 2012 12:47 PM}

Hi Claudiu, yes I was able to solve my issue.  My resolution was different than yours though, I had to install a certificate from my RRAS server.  That resolved a few of my issues, I do remember reading to use a static ip pool as a resolution while I was researching my issue.  My understanding is that checking the "use default gateway" option means the internet connection will pass through the gateway of the machines network connection, not the VPN endpoint.  I wonder why it would be blocking traffic at the endpoint?

_{Saturday, March 30, 2013 8:27 PM | 1 vote}

I had the exact same problem. I was able to connect to the VPN but was unable to ping any resources. I was getting my IP assignments from my DHCP. I switched to using a static pool instead. Now I can access all resources on the LAN. 

_{Wednesday, July 2, 2014 11:24 AM}

Thanks Guys. I had same issue

Setting up IP assignment  from DHCP helped me as well