Going bald! (Win2K->NT Server VPN routing)

[Duke]

Ok folks, I've been pulling my hair out on this checking the KB and
Google's groups but haven't found what I'm looking for (yet!)

Here's what I have:

NT PDC server that acts as the RAS and DHCP server for our office
network. The office network is the 192.168.1.x , and the NT server's
address is 192.168.1.67.

We have a dedicated connection to the internet via a smoothwall
firewall (it is the gateway and NAT device 192.168.1.1) and cisco
router. The smoothwall firewall has ports 47, and 1723 forwarded
(/usr/local/bin/ipfwd --masq 192.168.1.67 47 & etc.)

Now I have a laptop that I use sometimes at work, sometimes at home
that has Windows 2000 on it. When I use it at work it has a DHCP
assigned address. When I take it home it is a standalone machine. I
have a DSL line (via BellSouth) that I'm trying to use to connect to
the office network via VPN with PPTP.

I have the NT server set up to allow for RAS with my client specifying
it's own address (192.168.1.23) and have resolved the authentication
MS-CHAP issues so that I can actually connect. However, that is where
it falls apart. I can connect (either the DSL or a BellSouth dial-up
line) but I cannot ping anything on the office network. In the office
I cannot ping the laptop even though the NT server knows the address
and it's hostname.

Here is the routing table while connected:
Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 60 08 d1 9b bf ...... FE575 Ethernet Adapter
0x14000004 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
0x15000005 ...00 53 45 00 00 00 ...... WAN (PPP/SLIP) Interface
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface
Metric
0.0.0.0 0.0.0.0 68.159.252.90 68.159.252.90
1
68.159.252.90 255.255.255.255 127.0.0.1 127.0.0.1
1
68.255.255.255 255.255.255.255 68.159.252.90 68.159.252.90
1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
192.168.1.23 255.255.255.255 127.0.0.1 127.0.0.1
1
192.168.1.255 255.255.255.255 192.168.1.23 192.168.1.23
1
209.215.217.65 255.255.255.255 68.159.252.90 68.159.252.90
1
216.131.29.186 255.255.255.255 68.159.252.90 68.159.252.90
1
224.0.0.0 224.0.0.0 68.159.252.90 68.159.252.90
1
224.0.0.0 224.0.0.0 192.168.1.23 192.168.1.23
1
255.255.255.255 255.255.255.255 192.168.1.23 2
1
Default Gateway: 68.159.252.90
===========================================================================
Persistent Routes:
None

The 68.159.x.x stuff is the dial-up connection (I'm using dial-up on
the laptop at work to try and get it working, DSL at home).

Is the 192.168.1.23 gateway correct? It would seem like it should use
the VPN server 192.168.1.67 as the gateway for it's connection.

Other notes: I've tried the "Use default gateway on remote network"
checked and unchecked with no success.

What else can I check/try? Am I missing something big here?

TIA!
Duke

 

[Robert L [MS-MVP]]

some things wrong with the routing table and the gateway should be
192.168.1.67. posting ipconfig /all may help.

--
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.