Re: RRAS client can't ping internal network

• Previous message: J Porter: "Proper use of RRAS??"
• In reply to: Mike Morgan: "RRAS client can't ping internal network"
• Next in thread: Mike Morgan: "Re: RRAS client can't ping internal network"
• Reply: Mike Morgan: "Re: RRAS client can't ping internal network"
• Messages sorted by: [ date ] [ thread ]

Date: Mon, 9 Aug 2004 15:04:01 -0500

this may help. quoted form http://www.ChicagoTech.net
Can't access the remote network after unchecking "Use default gateway on
Remote Network"

Symptom: After following above instruction and uncheck "Use default gateway
on Remote Network" on VPN connection, you can't access to the remote network
any more. For example, your LAN network is 192.0.0.0 and default gateway is
192.0.0.1; the VPN is 192.0.1.0 and gateway 192.0.1.1.that is connecting to
the remote network 10.0.0.0. After establishing the VPN connection and
unchecking "Use default gateway on Remote Network", your computer use
192.0.0.1 as gateway instead of 192.0.1.1 and can't find a way to 10.0.0.0
network.

Resolution: you need modify the route table manually or refer to our Routing
page on this web. Or check "Use default gateway on Remote Network" on VPN
connection.

-- 
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.
"Mike Morgan" <mmorgan@ci.gulfport.ms.us> wrote in message 
news:OIq1epifEHA.384@TK2MSFTNGP10.phx.gbl...
> I'm having a problem with our win2k routing and remote access server. I 
> can
> get the dialup clients to connect, but they can't see past the remote 
> access
> server. The server can ping the lan and the remote client. But, the client
> can't ping anything on the lan besides the remote access server. Tracert
> reveals that the route dies at the RAS server. How do I make the RAS 
> server
> route traffic to and from the lan for the clients? I used the wizard to
> setup RRAS on the server. I'm using DHCP to assign the remote client
> addresses. The clients are pulling IPs fine, but they aren't getting the 
> DNS
> server IP for some reason. Authentication is done with IAS. I do have ISA
> installed in cache mode for a web proxy. It seems to work fine. I found an
> article at support.microsoft.com that said to turn the IPEnableRouter 
> DWORD
> to 1 in the registry. I set that and rebooted with no joy. Have I missed
> something obvious? Is there a problem with RRAS coexisting with ISA? If 
> so,
> is it fixable? I'd really like to leave all of this on the same machine if
> possible.
>
> 

• Previous message: J Porter: "Proper use of RRAS??"
• In reply to: Mike Morgan: "RRAS client can't ping internal network"
• Next in thread: Mike Morgan: "Re: RRAS client can't ping internal network"
• Reply: Mike Morgan: "Re: RRAS client can't ping internal network"
• Messages sorted by: [ date ] [ thread ]