UNC using IP address

[JimFox2k5]

I am trying to access my file server over a VPN. I can access the file using
a mapped drive (G. If I try to connect to the server using the UNC path
\\192.168.111.11\<share_name> I get an error saying the file can not be
found. (The G drive is mapped to \\192.168.111.11\<share_name>). The problem
is I can't use the mapped drive as I have some files hyperlinked in Word -
which chnages the mapped driver to the UNC share name instead. I don't know
why I can access them using the mapped drive, but not a UNC path. Any help /
suggestions would be appreciated

 

[smlunatick]

I am trying to access my file server over a VPN. I can access the file using
a mapped drive (G. If I try to connect to the server using the UNC path
\\192.168.111.11\<share_name> I get an error saying the file can not be
found. (The G drive is mapped to \\192.168.111.11\<share_name>). The problem
is I can't use the mapped drive as I have some files hyperlinked in Word -
which chnages the mapped driver to the UNC share name instead. I don't know
why I can access them using the mapped drive, but not a UNC path. Any help /
suggestions would be appreciated

Firewall and / or anti-virus settings could block the UNC "protocol."

 

[John Wunderlich]

If I try to connect to the server using the UNC path
\\192.168.111.11\<share_name> I get an error saying the file can
not be found.

Can you elaborate a bit on how you are "connecting"?

What happens if when you do:
Start -> Run -> \\192.168.111.11\sharename

From a command prompt window (start -> Run -> "cmd") what error, if
any, do you get when you enter the following command:
net use \\192.168.111.11\sharename

What happens if you double-click on any folder and enter
\\192.168.111.11\sharename
in the Address Window (assumes Address Toolbar enabled)?

Your UNC path "\\192.168.111.11\sharename" represents a folder
(directory). The error indicates a "file" could not be found. Do
you need to add a filename to the path?

HTH,
John

 

[Anteaus]

You are trying to connect to the server's internal IP address. This will not
be the IP address it's seen-as by the VPN link.

To discover this, type nslookup <servername> or ping <servername> whilst
connected (without the \\)

 

[Anteaus]

Also, not sure if this affects document links, but worth a try:

http://support.microsoft.com/kb/171406/EN-US/

Basically, this changing of driveletters to UNC paths rates as one of the
stupidest pieces of automation of any software. Whoever dreamed it up -as
always- hadn't thought-through the consequences properly.

Aside from the VPN weirdness, a further implication is that the transfer of
a data-store to a new server results in Word still (unknown to the user or
administrator) pulling linked files from the OLD server if it's still
visible. This can result in a catastrophic data loss. Basically this
automatic UNC conversion is a bad, bad BAD idea, and should be
patched/corrected in all Office versions.