VPN - Mapping

[Guest]

Hi,
I am not sure what I am doing wrong but here is what is happening. I have a
XP Pro client connecting to a Win 2000 Server through a VPN. I am able to
log on and ping the remote address 192.168.1.169. However, I cannot ping the
server name (win2ksrvr). When I try to map to a shared drive by using the IP
address (\\192.168.1.169\data) and using a domain user with rights
(domain\name) I am unable to authentic and cannot complete the mapping. I
tried connecting using both the domain name and the ip address
(192.168.1.169\username).
Any suggestions would really be appreciated.
Thanks
Rich

 

[Janani [MSFT]]

Hi,
Can you give the following information?
Is 192.168.1.169 the IP of the Internal adapter on the server or is it a LAN
adapter? Or is it the IP of a machine behind the server?
( You can check this by doing an ipconfig on the server. If it is the
Internal adapter this address will be displayed under "PPP adapter")

If it is the IP of a remote machine, are you able to do a net use to the
share from the VPN server itself?

You might not be able to ping the server by name because the DNS server
configured on your client machine may not have the address of the remote
machine registered.

 

[Guest]

Hi Janani,

Thank you for the response - I am sorry it took so long to get back to you.
The Server's IP address is 192.168.1.109. The 192.168.1.169 is generated by
the server and assigned to the VPN connection (I don't know if that answers
the question - please let me know).
I can ping that address. What is interesting is at one time I was able to
connect to the drive using th eserver name (win2ksrv).

thanks
Rich

 

[Bill Grant]

There are two ways to resolve names to IP addresses. One uses Netbios
names and the other uses DNS type names.

Netbios names do not work well over WAN links because they depend on
broadcasts. To get around that problem you would need an LMHOSTS file on the
client with entries for all machines on the LAN which you need to contact by
name.

The other method is to use DNS. When the remote client connects it
should get the address of the DNS server on your LAN. Try ping or nslookup
for the machine's full name (eg w2ksrv.domainname.local) . If this works,
DNS is working. To ping using just the machine name, add your DNS suffix to
the client's TCP/IP properties in connection properties.