VPN client cannot see ping internal resources by name
Posted on 2005-03-22
I have a windows 2000 server acting as a DC, DNS server and RRAS server.
Connecting to the RRAS from my home via a Mac OS X, I can ping internal resources by name (e.g. server1.domain.com, server1, computer1, etc).
Connecting to the RRAS from my home via a windows xp home laptop, I cannot ping internal resources by name. IPCONFIG from xp shows that DNS is office DNS server for the PPTP connection. "Use default gateway from the remote network" is checked to prevent split tunneling. Both clients can surf the Internet without difficulty.
What I've learned from the windowsitlibrary.com Site:
"Use Default Gateway on Remote Network: When this option is selected, packets that are unable to be routed over the local network are passed on to the default gateway of the remote network for resolution. With this option, addressing conflicts between the local LAN and the remote LAN are adjudicated in favor of the remote network."
I'm deducting that memdata.com is more easily resolved over my local network since I've visited the site before. It is therefore sending the request to our remote web host, 184.108.40.206. Because of that, I cannot see the remote resources by name at my office because the office uses the domain memdata.com as the internal domain. I presume that if we changed it, it would work.
On the other hand, the Mac sends all requests directly to the remote network (an option I selected when initially setting up the connection), not attempting to resolve anything locally. Because of this, the Mac can see the remote resources by name without any problems, but the XP machine cannot.
Can anyone verify this?