VPN issues with seeing resources

[Gary Pasler]

I have a problem that I cannot peg down here. Most of our
VPN clients have no problems getting on the network from
their remote location. However, these are all on XP
clients. Now we have a Windows2K Pro machine. It was
sitting on the local network and everything was fine, I
have taken it off the local network and moved it to a
remote location and setup VPN. However, I cannot resolve
names to ip addresses... unless.... the user is given
administrative privilidges on the domain, then it works.
I have looked at the other users who are able to work
properly from their xp machine for example. They are just
domain users, no admin privilidges on the network at all,
heck their machines aren't even listed as members of the
domain at all, actually one is, a laptop.

What could be causing me to be unable to resolve names to
ip addresses (which is realy hosing up using
Outlook/Exchange over the VPN) without administrative
privilidges? Note, these are users that are all setup and
working fine on the domain network (win2k server).

Gary Pasler
PBNA
(e-mail address removed)

 

[Bill Grant]

I can't think what difference having admin privilege would make. I do
know that W2k clients have problems which XP clients don't in this
situation. XP have an improved version of connection manager which makes
domain access over a RAS/VPN link more reliable.

I would look at the domain suffix settings in the client's connection
properties. Make sure that they have the correct suffix for the domain on
the LAN. The machine won't necessarily use the settings set up on another
connection (such as a NIC) for the WAN connection.