Re: Routing & Remote Access ip address and resource error

From: Robert L [MS-MVP] (noreply_at_hotmail.com)
Date: 03/23/04

  • Next message: Miha Bernik: "VPN Server" 
    Date: Tue, 23 Mar 2004 12:52:03 -0600

    255.255.255.255 subnet is OK and that is by design. the question is why you
    get 192.168.1.x ip. double check the VPN DHCP settings. 

    -- 
For more and other information, go to  http://www.ChicagoTech.net
Don't send e-mail or reply to me except you need consulting services. 
Posting on MS newsgroup will benefit all readers and you may get more help.
Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on 
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.
"darrien" <anonymous@discussions.microsoft.com> wrote in message 
news:d81701c41103$cd517be0$a001280a@phx.gbl...
> We have 2 windows 2000 machines.  A domain controller with
> exchange on it and a fileserver with routing and remote
> access configured on it.  They both sit behind a linksys
> firewall.  We have elected to use pptp for vpn connections
> so 1723 was opened on the router and forwared to the
> fileserver.  We are using a private ip 192.168.(2).x with
> a class "c" subnet on this network. Routing and remote
> access was configured with basic default settings but the
> assignment of address was set for 192.168.2.100-
> 192.168.2.149.  The clients can vpn into the network.
> They even appear in the remote access client with their
> time.  The are unable to view anything on the network
> though.  When running ipconfig from the client, the
> address it keeps trying to assign is 192.168.(1).x.  with
> a 255.255.255.255 subnet.  When i key in an address into
> the clients pptp ip properties, it will accept the address
> and still log in but still unable to access the network.
> The subnet is still 255.255.255.255.  Is the subnet the
> reason that We are unable to view the network resources or
> is there a bigger problem here?  Is there a need to
> install anything else like wins or open any other ports
> for browsing? extra info.  DNS is done by the domain
> controller. DHCP for our network is done by the linksys
> router.  Thanks again for your help.
  • Next message: Miha Bernik: "VPN Server"

    Relevant Pages

    • Re: Help requested with RIPv1 lan issues (UK school)
      ... > school network. ... > RIP v1 request traffic from our clients that cause our normal client to ... Yet then you go on to discuss RIP, static routes on clients etc. ... You say you have static routes on the clients to the 192.168.2.x subnet. ...
      (microsoft.public.windowsxp.network_web)
    • Re: Help requested with RIPv1 lan issues (UK school)
      ... > school network. ... > RIP v1 request traffic from our clients that cause our normal client to ... Yet then you go on to discuss RIP, static routes on clients etc. ... You say you have static routes on the clients to the 192.168.2.x subnet. ...
      (microsoft.public.windows.server.networking)
    • RE: SBS 2003 VPN issue through ISA
      ... The XP clients and the TS are in the same network and same domain. ... connections are established from the clients themselves using Cisco VPN ... appears ISA is somehow dropping the connection according to the logs. ...
      (microsoft.public.windows.server.sbs)
    • Re: VPN on Small Business Server 2k3
      ... I am able to ping the vpn server ip successfully. ... Currently I have the vpn subnet manually set for 154.204.50.x I changed it ... the SBS network is 192.168.0.x and the local subnet here at the remote locale ...
      (microsoft.public.windows.server.sbs)
    • OT: RRAS doesnt R
      ... A remote user now needs access to our network. ... She needs to connect via VPN ... Our office is only one subnet. ... Here's the routing table from a "route print" done on Dataman, ...
      (microsoft.public.cert.exam.mcse)
    Loading