VPN in successfully; however, can't ping LAN servers.

[Do]

Here the the MS instructions I used.
http://support.microsoft.com/default.aspx?scid=kb;en-us;308208

Yes, the VPN client uses the DNS servers of the site that I am connecting
to. Here's the strange part, and I don't think this affects it-- the IP
that the DHCP assigns to the PPP client is also the gateway. It doesn't
assign the correct gateway or subnet mask from my DNS servers that I have
setup for my LAN (the workstations on the LAN have the correct settings).

PPP adapter Baseline:

Connection-specific DNS Suffix . : *********.com
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.1.63
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 192.168.1.63
DNS Servers . . . . . . . . . . . : 192.168.1.2
192.168.1.7
192.168.1.2
192.168.1.7

Is it reasonable for me to expect that all my PPP settings be identical to
my LAN, if I use the same DNS servers as the workstations on my LAN?

Thanks,

Do

 

[Robert L [MS-MVP]]

quoted from http://www.ChicagoTech.net

Why my XP VPN client's subnet mask is 255.255.255.255

This is by design. Since this connection is point to point, not point to net
or net to net, VPN server assigns 255.255.255.255 mask to the client.

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.

 

[Bill Grant]

You are correct about the gateway setting - this has nothing to do with
your problem. The gateway address must be the "received" IP address. What
this really means is that the default gateway for the client is the PPP link
to the VPN server.

The VPN client does not get its IP address and name server addresses
from DHCP. As part of the PPP setup process, it gets them directly from the
VPN server. After connection, a client can contact DHCP directly.

On the client, check the advanced TCP/IP settings of the connection.
Check that it has the correct DNS suffix set up.