jamescodefour
asked on
UNC path fine in office but fails over VPN - ideas?
Hi, a server share name resolves perfectly by cleint when in the office but when connecting to the server via VPN (Windows 2000 Server Routing and Remote accesss) it shows as network path not found. However can access it via IP. Example
\\SERVER\SHARE - FAILS VIA VPN
\\192.168.0.100\SHARE - WORKS VIA VPN (192.168.0.100 being servers IP)
Ideas?
\\SERVER\SHARE - FAILS VIA VPN
\\192.168.0.100\SHARE - WORKS VIA VPN (192.168.0.100 being servers IP)
Ideas?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
You could try nslookup servername on client to see which DNS server it is using and what (if) it resolves.
ASKER
Can you advise steps for option 3 - HOSTS table on remote PC with server names in ?
on remote machine open up the HOSTS tabel which is located at
c:\winnt\system32\drivers\ etc\hosts
or
c:\windows\system32\driver s\etc\host s
or for Win9x
c:\windows\hosts
edit it as an admin using notepad and add entries for
ipaddress servername
for any servers they need to connect with.
hth
Steve
c:\winnt\system32\drivers\
or
c:\windows\system32\driver
or for Win9x
c:\windows\hosts
edit it as an admin using notepad and add entries for
ipaddress servername
for any servers they need to connect with.
hth
Steve