Re: VPN connect-Ok, but....

From: Bill Grant (not.available_at_online)
Date: 04/01/04 

Date: Thu, 1 Apr 2004 14:56:44 +1000

    You should not need to add any routes. Just check that routing is
enabled. RRAS will route automatically between its interfaces.

    What is the default route of your LAN clients? Is it the RRAS router?
eg

Internet
    |
router
192.168.2.1
    |
192.168.2.200 dg 192.168.2.200
   RRAS ----------------------------------VPN
192.168.1.150 dg blank
    |
LAN clients
192.168.1.x dg 192.168.1.150

    If LAN routing is enabled in RRAS, a remote client using 192.168.200.x
should be able to ping any 192.168.1.x machine.

"PMP" <anonymous@discussions.microsoft.com> wrote in message
news:32DAC73E-49F1-4B8E-8F13-A1FDA665312F@microsoft.com...
> route print:
>
>
===========================================================================
> 0x1 ........................... MS TCP Loopback interface
> 0x1000002 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
> 0x1000003 ...00 03 47 32 2e f2 ...... Intel(R) 82540EM Based Network
Connection
> 0x11000004 ...00 03 47 32 2e f1 ...... Intel(R) PRO Adapter
>
===========================================================================
>
===========================================================================
> net adress mask gateway
interface metric
> 0.0.0.0 0.0.0.0 192.168.2.1
192.168.2.200 1
> 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
> 192.168.1.0 255.255.255.0 192.168.1.150 192.168.1.150
1
> 192.168.1.150 255.255.255.255 127.0.0.1 127.0.0.1
1
> 192.168.1.255 255.255.255.255 192.168.1.150 192.168.1.150 1
> 192.168.2.0 255.255.255.0 192.168.2.200 192.168.2.200 1
> 192.168.2.200 255.255.255.255 127.0.0.1 127.0.0.1
2
> 192.168.2.255 255.255.255.255 192.168.2.200 192.168.2.200 2
> 192.168.200.1 255.255.255.255 127.0.0.1 127.0.0.1
1
> 224.0.0.0 224.0.0.0 192.168.1.150 192.168.1.150
1
> 224.0.0.0 224.0.0.0 192.168.2.200 192.168.2.200
2
> 255.255.255.255 255.255.255.255 192.168.1.150 192.168.1.150 1
> GW: 192.168.2.1
>
===========================================================================
>

Relevant Pages

  • Re: Cannot Share internet thru dual NICs
    ... "You will also need to add a route to your Internet router. ... You need to route traffic for 192.168.254 to the RRAS/NAT router. ... > do an ipconfig /release and ipconfig /renew on the clients to get the new ...
    (microsoft.public.win2000.ras_routing)
  • Re: XP unable to ping.
    ... I did a route print and saw nothing out of the ordinary. ... to go to the router address. ... >> system can ping the Internet DNS server any time. ... >> to route packets to the router for another private LAN. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: Dialing into Internet with one PC and using that PC as gateway for rest of LAN
    ... > currently my only connectivity is dialup. ... /etc/resolv.conf and firewall not blocking internet access). ... Normally the only "default" route should be towards the internet, ... Any local routing that has to go through another local router ...
    (comp.os.linux.networking)
  • Re: [SLE] Routing issues with eth1(internal) & eth2(external)
    ... Let the router do the job it was designed for, ... >> from the internet you can then access all of the internal machines via ... Liberty1 is to be a development server. ...
    (SuSE)
  • Re: another request to reach the router
    ... all of the WXP computers can access the internet (via the ... > not been able to configure it to get to the router. ... if you do not use the -n switch for route or netstat (but that takes ... > I read somewhere that these should not be used when assigning the IP ...
    (comp.os.linux.setup)