1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

RRAS static ip assignment issue

Discussion in 'Networking (Hardware & Software)' started by uniburner, 2005/03/15.

Thread Status:
Not open for further replies.
  1. 2005/03/15
    uniburner

    uniburner Inactive Thread Starter

    Joined:
    2004/10/06
    Messages:
    2
    Likes Received:
    0
    Hello all,

    First of all, thank you for taking time to read about my issue. I have a rras server running windows 2000 server and i have a static pool (192.168.10.x) of addys assigned for users when accessing different from the internal network (192.168.2.x)... up until today, it has worked fine but now when my 5 users login, they authenticate and connect but cannot access or ping anything on the network... i assigned the pool with 192.168.10.x with a subnet of 255.255.255.0. When i vpn to the server and do a ipconfig... my ip is 192.168.10.4 with a subnet of 255.255.255.255 ... I’m not sure why its giving me this subnet??? And im not sure why no one can access the network; any suggestions would be greatly appreciated!

    -U
     
  2. 2005/03/16
    ReggieB

    ReggieB Inactive Alumni

    Joined:
    2004/05/12
    Messages:
    2,786
    Likes Received:
    2
    A mask of 255.255.255.255 gives a host only address (as opposed to a network/subnet address). When you connect via dial-in that connection is effectively point to point - one host to another host. Therefore a network mask would be inappropriate. You would only use a network mask to route to a network beyond the host dialing in.

    First thing to test is that TCP/IP is working over the connection. If you do an IPCONFIG you should get two addresses. The address of the remote client (192.168.10.4) in your example, and the gateway address. The gateway is the other end of the point to point connection, and is the server's address on this connection. It may well be 192.168.10.1. Start by pinging the gateway address. If you get replies you know that TCP/IP is working over the dial-in connection. I expect that in this case you have a routing issue at the server. If it fails you have a problem with the dial-up connection.
     

  3. to hide this advert.

  4. 2005/03/30
    uniburner

    uniburner Inactive Thread Starter

    Joined:
    2004/10/06
    Messages:
    2
    Likes Received:
    0
    Thank you for the information; it was a routing problem and once i added static routes, it all started working great!

    Thanks again for your input/time!
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.