VPN clients cannot ping Netbios name but only ip address.

  • Thread starter Thread starter Joe Mine
  • Start date Start date
J

Joe Mine

Hi, I've a VPN client in a different domain and the VPN server/network is
another domain.
From the VPN client which was given the VPN ip address of 192.168.100.71.
And this client is trying to communicate with a Windows 2k Server: Mercury
with ip 192.168.100.11. It can ping Mercury's ip 192.168.100.11 fine (see
below). But it cannot ping the netbios name Mercury... And when net view
\\Mercury system error 53 occurs. But when net view \\192.168.100.11 it
shows the shares.

I need to ping Mercury and net view \\Mercury for important application.
What must I do to allow this? Please list the steps, thank you.


Results of Pings.
C:\>ping 192.168.100.11

Pinging 192.168.100.11 with 32 bytes of data:

Reply from 192.168.100.11: bytes=32 time=78ms TTL=127

Reply from 192.168.100.11: bytes=32 time=62ms TTL=127

Reply from 192.168.100.11: bytes=32 time=78ms TTL=127

Reply from 192.168.100.11: bytes=32 time=78ms TTL=127

Ping statistics for 192.168.100.11:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 62ms, Maximum = 78ms, Average = 74ms

C:\>ping mercury

Unknown host mercury.

C:\>net view \\mercury

System error 53 has occurred.

The network path was not found.



C:\>net view \\192.168.100.11

Shared resources at \\192.168.100.11





Share name Type Used as Comment

---------------------------------------------------------

NETLOGON Disk Logon server share

REPLDATA Disk

SYSVOL Disk Logon server share

VPHOME Disk Symantec AntiVirus

VPLOGON Disk Symantec AntiVirus

The command completed successfully.
 
If the LAN is running WINS, make sure the client gets the correct WINS
address.

Without WINS, you need an LMHOSTS file on the client to resolve the name
to its IP address.
 
Back
Top