Relative path problem across WAN?

I'm using an Autodesk application call Revit to collaborate on a file
with a partner firm (connected with ipsec vpn). This particular
application is sort of the a "check in/check out" system, although there
is only one central file that is being shared. Basically, you create a
file, enable "sharing," then everyone opens the central file, saves a
local copy for working, then periodically saves back the changes to the
Central File (using the command "Save to Central" rather the the
standard "Save")

So we set up the VPN and the partner firm set up a windows share on
their server, which I connected to using:

NET USE * \\10.1.1.50\cincydata\ED\Mux\Mux1202\REvit\Central


(I have to specify that I want to use the partner firm's server
credentials with , or the command will fail)

So far, so good. I can add, edit and delete files on the remote share.

The only problem is a critical one. Revit can't save local changes
back to the central shared file. It returns a "path not found" error.

So, there seems to be some difference between the pathname that is
mapped on my workstation, and the path that the central file thinks that
it lives in. I've tried a number of different was to resolve this, but
not matter how I connect to that share, the problem persists.



So, a couple things I'm wondering about:

1. Is there any difference in the way path names to resources referred
to if you use "Net use" or just type in a UNC pathname in the "map
network drive"

2. Is there a recomended "best practice" method for mapping these
drives to avoid conflicst like this?

3. What about drive letters? Do I need to worry that there is a
mapping conlict between a reference to a drive letter and a UNC
pathname? Any sure ways to avoid this?

4. I'm mapping the share from IP adress + pathname across a VPN. Does
name resultion (e.g.DNS and WINS) come into play anywhere in this
process? I don't see how, but that is something that we are not
transmitting across the WAN currently.

Or really, any insights into the inner workings or MS drive mappings
that I may have overlooked would be appreciated. I've been searching and
experimenting for some days, but I'm just not getting anywhere!

Thanks
Jim Helfer
Systems Administrator
WTW Architects