Routing and remote access

Discussion in 'Site & Server Administration' started by Talker, Feb 24, 2009.

  1. #1
    Hi there.

    I have installed Routing and Remote access on a Win2003 box.

    I can connect to it via VPN, and i am able to ping/access the server which has the IP 192.168.0.1 , but i am not able to ping other computers or the file server on that network.

    Does anyone know how to setup the "Routing & remote access" so that i can the file server which has 192.168.0.2.


    Thanks
    Talker.
     
    Talker, Feb 24, 2009 IP
  2. hostingspeak

    hostingspeak Peon

    Messages:
    233
    Likes Received:
    10
    Best Answers:
    0
    Trophy Points:
    0
    #2
    Why don't you open a port for the file server, and VPN directly to it?
     
    hostingspeak, Feb 24, 2009 IP
  3. JPC-NickO

    JPC-NickO Guest

    Messages:
    69
    Likes Received:
    1
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Hi,

    Check the IP address you are assigned and the routes that are added.

    Also is the 192.168.0.0/16 network local?
     
    JPC-NickO, Feb 24, 2009 IP
  4. Talker

    Talker Notable Member

    Messages:
    2,795
    Likes Received:
    108
    Best Answers:
    0
    Trophy Points:
    210
    #4
    I cant coz the file server is not actually a file server.. its a network drive attached to the network. I need to access it via the VPN server.

    Yes 192.168.0.0 is the local network.
    I see the following on the routing & remote access console:

    [​IMG]

    There are no static routes defined and i guess that is what i have to work on. But when i add a new "static route", i put in these details...

    Interface: Local Area Connection
    Destination: 192.168.0.2 (the network storage drive)
    Network Mask: 255.255.255.0
    Gateway: (empty)
    Metric: 1

    I get this error:
    The network mask is not valid.
    The destination address cannot be more specific than the network mask.

    Here is a screenshot:
    [​IMG]


    Either i'm putting in the wrong details, or i'm on the wrong turn.. Any help would be highly appreciated.

    R.Talker.
     
    Talker, Feb 25, 2009 IP
  5. JPC-NickO

    JPC-NickO Guest

    Messages:
    69
    Likes Received:
    1
    Best Answers:
    0
    Trophy Points:
    0
    #5
    Hi,

    When I said local network I meant the network from which you are connecting with the VPN client. If there is a address space conflict it could cause problems.

    on the vpn client paste the output of ipconfig /all

    As for the route your not specifying it correctly.

    It should be if you want access all of 192.168.0.0/24 (including the NAS device)

    Interface: Local Area Connection
    Destination: 192.168.0.0 (the network storage drive)
    Network Mask: 255.255.255.0
    Gateway: (empty)
    Metric: 1

    Or the following if you want to ONLY access the NAS device)

    Interface: Local Area Connection
    Destination: 192.168.0.2 (the network storage drive)
    Network Mask: 255.255.255.255
    Gateway: (empty)
    Metric: 1
     
    JPC-NickO, Feb 25, 2009 IP
  6. Talker

    Talker Notable Member

    Messages:
    2,795
    Likes Received:
    108
    Best Answers:
    0
    Trophy Points:
    210
    #6
    Thanks for the reply.

    The VPN client is on a totally different address space (192.168.4.0)
    And the VPN-Server/NAS device is on a different address space (192.168.0.0).

    Here is the output of ipconfig /all of the VPN-Client.

    Yes i want to add seperate routes for each device i have on the network. so i used:

    Interface: Local Area Connection
    Destination: 192.168.0.2 (the network storage drive)
    Network Mask: 255.255.255.255
    Gateway: cant leave empty
    Metric: 1

    I could not leave the Gateway empty, so i tried putting in
    a. 192.168.0.2
    b. 127.0.0.1
    c. 0.0.0.0
    All of these worked.. the route was added successfully.
    But which one of these should i be using? coz i cant access the NAS device with any one of them.

    Ping to 192.168.0.1 (VPN server) works.
    Ping to 192.168.0.2 (NAS storage device) times out.

    May be on the VPN client, i am accessing the NAS device incorrectly. How am i supposed to access the NAS devide at the VPN client?


    Talker.
     
    Talker, Feb 25, 2009 IP
  7. Talker

    Talker Notable Member

    Messages:
    2,795
    Likes Received:
    108
    Best Answers:
    0
    Trophy Points:
    210
    #7
    Anyone here to help :confused: :confused: :confused:
     
    Talker, Feb 26, 2009 IP