Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Can't access shared drives over vpn
I have two domains. bcd.corp and mno.local. I have created domain trust on these two Windows 2008 domains. I use an SSL-VPN 200 (SoniWall). At the office, I am able to view all mapped drives. At home, over VPN, I can view mapped drives on bcd.corp, but when I try to view mapped drives on mno.local, I get a message saying that the network path cannot be found. Over VPN, I can ping the FQDNs of both servers (each of them is the domain controller for their separate domains).
Who is Participating?
Sorry, here's the correct error message. It says that the mapped drive "is not accessible. The network location cannot be reached."
jpgobert, I'll get back to you on the commands shortly.
jpgobert, I'll get back to you on the commands shortly.
jp the first 2 commands ran successfully. For the third, I get the following error message:
"System error 53 has occurred.
The network path was not found."
"System error 53 has occurred.
The network path was not found."
This only happens when attempting to map the connection over your VPN connection while remote? Does it work properly when you're at your office and not relying on a VPN connection?
I'm gonna have to drop offline soon... the most common reasons this will happen will either be due to a firewall blocking the required ports / services & or netbios resolution isn't working. I'm not sure what the connection path looks like and where your VPN connection is coming in at but I'd check to make sure that you've got the right ports open between your PC, across the VPN and to the server hosting mno.local. Also, I'm assuming we're talking about Windows 7 on this... when you first connected to the VPN connection Windows should have popped open the network type dialog box that allows you to choose home / work / public. I'd make sure that work was chosen and that the local firewall isn't blocking the connection without you realizing it.
I've already mapped the network drive. I just am unable to view the contents. Check this out - If I map the network drive normally, I can view it without problems (using remote server's IP address). If I however map the network drive, via DFS path/address, then I'm unable to view the contents of the mapped drive.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
ping server.mno.local <- make sure you get a reply
net view \\server.mno.local <- see if it returns the network shares & if so, make sure the share you're trying to get to shows up
net use z: \\server.mno.local\share /user:domain\username <- if it fails you should get an error message with a failure type... if it can't find the path, try mapping with the server's IP address instead of the name
Between these three simple commands something should stick out... post back with any errors you get unless you get it figured out...