'NET USE' over VPN. Cant map drives

Hi,
I have an R2 server running VPN/Remote access.
The VPN works and can connect no worries. But when I try to map a drive I get an error about the file not being accessible.

Perms all seem to be set correctly.
Users have access to the share Im trying to connect to.
Works fine in house.

I use the IP and get same result.

I wouldnt usually set the router as dns, i would normally use the server for dns... I feel this might mess with the name resolution, but would this cause my problem even when I use ip's?

This is becoming urgent as my client needs other countries to have access from other offices and I cant work it out fo rthe life of me.

Any help greatly appreciated.

Can you post the error message you're getting?

"error 1920 the file cannot be accessed by the system."

Not trying to hijack the thread, but just to throw a thought in there, this still sounds like a permissions issue. Is it possible you need to specificy the domain name with the username/password when issuing the net use command? I tried Googling the exact error you're getting and all I could find was one person experiencing a similar issue due to permissions on local accounts vs domain accounts.

Thats not a hijack... its an attempt to help me out. Cheers.

I have tried un and pwd in net use, to no avail.
I have tried sooooo many things.
Tried changing remote access rules, file perms, dir perms, root perms... and many other things (including un and pwd)

The only thing I think isnt perfect is the fact the router is issuing DHCP, not the DC.
I know this isnt perfect, but would it cause this problem?

Anyways, un and pwd doesnt change anything.

No, i don't think it's an IP addressing or network issue. Can you ping the server? Can you put the command you're trying in here? (change the server name to "servername" if you wish to keep it hidden.

I would imagine that a simple "net use \\servername\test" command would work. Try setting up a test folder like that and do that from the command line (instead of a script)?

I agree with Adam, try running net use from a command prompt instead of the script. If you get desparate, can you temporarily add the user to the Domain Admins group (that group usually has full access to everything so that may rule out a permissions issue)? DHCP being on the router and not server shouldn't matter. When connected via VPN, can you ping the resources that hosts the folder/file you're trying to get to by name and IP? This would rule out a potential DNS issue that may be causing name resolution issues. Really though it does sound like a permissions issue. I'm sure you already know most of this, but here's a KB from Microsoft on the net use command that may help; maybe you're forgetting something small? CLICK

Thanks for the replies so far.
None to an avail though.

I use (in cmd) 'net use X: \\server(or ip)\share
and get


I have, since first posting:
Removed 3rd party TS server (XPUnlimited) +reboot
turned off AV + reboot
Added ppped/pppuser/cmd/ to AV firewall

I've also got a 3rd party *guru* looking at this and they are stumped as well.

I'm really getting lost here. This is pretty basic stuff... and it's making me look like a numpty!!!!!!
DOH.

Any ideas appreciated... even if you think it might sound dump/useless/whatever... please dont hold back... I've exhausted my knowledge here.

Any help very much appreciated.

EDIT: I also tried the user level stuff. Even admin himself cant map drives.

Can you try mapping the internal IP of the server you're trying to reach using the HOSTS file? This would eliminate a DNS issue for testing purposes. Also, install Wireshark on the target server. Start the analyzer, and when you try to access the file over vpn, monitor the status of the Wireshark scan to see if the vpn client is actually making it's way to the server's NIC.

VPN traffic IS making its way to server coz I can RDP successfully into server

So when connected to the VPN, you can RDP into it by the computer name, not just IP, right? If so, you don't have a DNS issue.

Just to be clear, you are able to map that drive when you are not VPN'ed in, right?

DNS is not the problem.
Yes, I can map drives when onsite. No in house users complain about mapped drive issues. It is only over VPN that I have the problem,

Are you mapping the drives by computer name or IP? Second thought, you said DNS isn't the problem right? I take it to mean, that was your response to me asking you if you could RDP be into the server, while connected to the vpn, via the computer name?

Can you ping the server? What if you don't try to map the drive and just type it into the address bar once you're connected? Do any of those work?