none
PPTP VPN - Cant Access Remote Network

    Question

  • Hi there,

    I have just set up a PPTP VPN RRAS Server on 2008 R2 with 2 interfaces, one internal [10.6.65.0 \ 255.255.255.128] on a private network (LAN) and one external interface [10.0.0.0 \ 255.255.255.0] connected to the internet (WAN).

    The VPN is configured to relay DHCP from my LAN and that works fine. So when I connect from a remote location to the VPN I recieve a 10.6.65.X IP, with the correct DNS settings, but I can not access anything on the VPN network. I can not ping any addresses by IP, or resolve any hostnames via DNS. I also can not ping the VPN gateway when connected. I am using Win 7 VPN Client.

    Any help would be greatly appreciated.

    Thanks

    Wednesday, April 11, 2012 5:33 PM

Answers

All replies

  • Hi zeroone mike,

    Thanks for posting here.

    So what was the default gateway we set to use at client when VPN tunnel be established ? could you show us the “route print” results from it ? was it still able it access its local network ?

    A series of blog posts for reference:

    Remote Access Deployment

    http://blogs.technet.com/b/rrasblog/archive/2009/03/25/remote-access-deployment-part-1-configuring-remote-access-clients.aspx

    http://blogs.technet.com/b/rrasblog/archive/2009/03/25/remote-access-deployment-part-2-configuring-rras-as-a-vpn-server.aspx

    http://blogs.technet.com/b/rrasblog/archive/2009/03/25/remote-access-deployment-part-3-configuring-radius-server-for-remote-access.aspx

    Split Tunneling for Concurrent Access to the Internet and an Intranet

    http://technet.microsoft.com/en-us/library/bb878117.aspx

    Thanks

    Tiger Li


    Tiger Li

    TechNet Community Support

    • Marked as answer by zeroone mike Friday, April 13, 2012 5:31 AM
    Thursday, April 12, 2012 7:47 AM
  • Thanks for the reply Tiger Li,

    The default gateway on the VPN client connection shows up as nothing, this is because the VPN server is multihomed, and the default gateway on the LAN interface of the server has to be left empty, or the server can't access the internet - and clients can't connect to it - here is an ipconfig /all from of the client VPN connection

    PPP adapter VPN Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : VPN Connection Physical Address. . . . . . . . . : DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv4 Address. . . . . . . . . . . : 10.6.65.73(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.255 Default Gateway . . . . . . . . . : DNS Servers . . . . . . . . . . . : 10.6.65.120 Primary WINS Server . . . . . . . : 10.6.65.120

    To answer your questions, when I do a route print of the VPN Interface on the client end it shows up with no results. Also the client PC can still access its local network while connected to the VPN.

    Friday, April 13, 2012 12:27 AM
  • Further to this looking at the Routing Table on the VPN server I can see there is no route from the external (10.0.0.0) to internal (10.6.65.0) network.. is this something that has to be manually configured? I thought RRAS would auto-configure this when NAT is configured at initial setup.

    Friday, April 13, 2012 1:05 AM
  • Hi Tiger Li,

    I deleted the config on my RRAS server and followed the tutorial you provided step by step. Still no luck.

    Fortunately we're in a virtualised environment and I could knock up another server pretty quickly, went through the setup process you provided and it worked!

    So not sure where the problem lay initially, but it now looks to be resolved. Thank you for your help, the VPN server is now working great.

    Friday, April 13, 2012 5:31 AM