Making a VPN connection just sets up an IP connection between host and
guest through the tunnel. It does not work like a LAN connection, and it
certainly does not do a domain login.
If you want name resolution to work, you will need to make sure the
client gets the correct info for DNS and WINS. If it doesn't get the right
info automatically, you need either fix it at the server end or configure
the client's connection properties manually with the correct settings
(particularly the domain suffix).
Glenn Thomson wrote:
> Hi Brad thanks for replying, so in your opinion this is the way it is
> suppose to be? it just seems strange to me to have the VPN tool that
> is for logging into remote networks that does not even show the
> network that was logged into? (not even the Domain ?)
>
> "Brad Dinerman [MVP - Windows Server Netw" wrote:
>
>> Perhaps just give the user a logon script (batch file using NET USE
>> F: \\Server\Share or something like that) and put the script on the
>> user's desktop. A single click on the batch file will map those
>> drives for the user.
>>
>> -Brad
>>
>>
>> ______________________________________
>> Bradley J. Dinerman, MVP - Windows Server Systems
>> President, New England Information Security Group
>> http://www.neisg.org
>>
>> Glenn Thomson wrote:
>>> We have a firewall and then RAS on single nic Windows Server 2003.
>>> When a user logs into VPN, Windows Explorer on the VPN client does
>>> not update with the network the user VPN'd into. Is there a way to
>>> get Explorer to populate with the VPN'd into network information
>>> without say typing in \\servername\c$ ??
>>> My users don't know or want to know the names of the servers or
>>> type them in.
Similar Threads
Linear Mode
