All of the routes looked fine. What ended up being the problem was a couple of Cisco switches acting hinky. A boot of them fixed the problem...Now to figure out why the switches acted up.
-Marty -----Original Message----- From: Ben Scott [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 27, 2008 7:22 PM To: NT System Admin Issues Subject: Re: Dialed into a RAS server, cannot ping past it. On Tue, May 27, 2008 at 2:04 PM, Marty Nelson <[EMAIL PROTECTED]> wrote: > We have an XP machine dialing into a Windows 2000 RAS server (at a > lightning fast 26.4K) and I can't seem to get past the RAS server. Have you/can you try it from another client machine? That will at least tell us if the problem is with the client or the server. > I have the "Use the default gateway on remote server box > checked", but it doesn't seem to be working. If you do a "ROUTE PRINT" command on the client, does it show an IP route to the remote network? If the client connected to another IP net which has the same network number? For example, if the remote network is 192.168.1.0/24, and the client is also on a home LAN which is 192.168.1.0/24, you'll have trouble. (The kernel IP router will see the local net as the same as the remote net, and may prefer the local route.) Any third-party firewall software installed on the client? -- Ben ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~ ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
