unable to map drive via VPN



mark h via WindowsKB.com
07-10-2005, 02:52 AM
Have an XPsp2 maching that gives the error "network path not found". have
the MS firewall off. using an external firewall that does DHCP also. other
machines on net have not issues with this. can see most of the other
machines on the other side of the VPN but not the machine i need to map to.
using a WAP that all the machines connect to at the remote site. they can
map to the share on the server no problem. I have even rebuilt this machine
still same issue. have changed name no good. still not tried net use no
good get drive disconnected.

Mark

Doug Sherman [MVP]
07-10-2005, 02:52 AM
Try mapping to:

\\IPaddressofserver\sharename

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"mark h via WindowsKB.com" <forum@nospam.WindowsKB.com> wrote in message
news:48347691a0b0466389e46ed142c38536@WindowsKB.com...
> Have an XPsp2 maching that gives the error "network path not found". have
> the MS firewall off. using an external firewall that does DHCP also. other
> machines on net have not issues with this. can see most of the other
> machines on the other side of the VPN but not the machine i need to map
to.
> using a WAP that all the machines connect to at the remote site. they can
> map to the share on the server no problem. I have even rebuilt this
machine
> still same issue. have changed name no good. still not tried net use no
> good get drive disconnected.
>
> Mark

mark h via WindowsKB.com
07-10-2005, 02:52 AM
Doug that worked sort of. it seems it didn't like my login and was not
allowing it to work more than once. I used an admin account and was able to
map via ip. then I changed connection as different user back to me and it
worked. So what causes the ip issue?

Thanks,

Mark

mark h via WindowsKB.com
07-10-2005, 02:52 AM
I attempted to add a new user to the machine with the above problem and am
now getting a domain trust issue. this unusual.

Doug Sherman [MVP]
07-10-2005, 02:52 AM
First of all, browsing and name resolution over a VPN connection is often
problematic. Lmhosts files or WINS are common solution attempts, but even
they don't always work. Since you are mapping to a 'server' - presumably
with a fixed IP - it's probably easier to avoid the issue and just map to
the IP.

If the target drive is on a domain member, you can map with a script and
provide different domain user credentials:

net use x: \\serverIP\share /USER:username@domain.com password

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"mark h via WindowsKB.com" <forum@WindowsKB.com> wrote in message
news:766f434d33494f22b81ff661c6141392@WindowsKB.com...
> I attempted to add a new user to the machine with the above problem and am
> now getting a domain trust issue. this unusual.


unable to map drive via VPN