Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We are a small, distributed company with a Windows Server 2008R2 installation. I would like to set up a way for our employees to connect securely to this server via VPN and then be able to map a network drive.

I have gotten this to work somewhat by installing the Network Policy and Access Services Role on the server and using the default settings. I have also created a network share on the server.
The problem is that our connectivity is sporadic (sometimes the service stops listening on the port or simply refuses to authorize correct credentials) and slow.
I can always connect through VPN, but mapping is problematic.

I would be grateful for the answer on how to accomplish this as well as some guidance on whether I am on the right track.
Thanks in advance!

share|improve this question

Your issues may revolve around DNS. I'll assume your using Routing and Remote Access for PPTP VPN. Once you connect the VPN I'll assume your client VPN IP is on the same subnet as the Windows Server. If those are true then the next step to proper file share access is DNS.

Can you ping the server by name from the client?

Can you ping the server from hostname, and hostname.dnsdomain?

Also, when you can't connect to the share, can you try via IP i.e. \\192.168.x.x (whatever server IP is)?

A proper DNS setup will ping to all three of those names/address above, assuming you allow ping through the server firewall.

Are the computers on the same domain and what is their OS? XP and older are known for slow file share access over the Internet. SMB 2 in Vista and newer fix that issue.

You might update your question with more details on how they VPN in, what software/services and network layout. I've used Network Policy and Access services for a decade and find them reliable for all business sizes, so it's likely a config or implementation issue.

share|improve this answer
Your assumptions are correct. I can ping the server, both by IP and hostname. I cannot map the file share via IP - still not responding. The computers are not on the same domain, all are Win7. I had the VPN set up to not use the remote gateway as the default, so that regular Internet traffic can go outside the VPN (because I'd just like to use that for a simple file share) but maybe the issue is that the client is trying to connect to file share outside the VPN tunnel? – Martin Wiboe Oct 4 '11 at 9:40
It would only try outside the VPN running if the server FQDN is also publicly available. Are you putting credentials in like domain\username? – Bret Fisher Oct 4 '11 at 21:28
The FQDN is publicly available . There is basically one server, which serves web pages, and I would like to extend it so we can share a network drive on it. Can this be accomplished? – Martin Wiboe Oct 4 '11 at 23:14
SMB is generally not recommended for use over "raw Internet" without a VPN. Your post title says "through VPN", so now you are saying you are not using VPN? If you want general file syncing between computers that are not connected by vpn then I would recommend, or my fav – Bret Fisher Oct 6 '11 at 22:51
Sorry, I am not making myself clear :) There is indeed VPN, and I would like the file access to go through VPN. However, the server also serves web pages - so if you try to access, you'll be served web pages. When you're connected through VPN, it should also be possible to access \\\FileShare. – Martin Wiboe Oct 7 '11 at 6:21

Are you clients Windows 7? Are the members of the domain?

You might want to look into using Direct Access instead of VPN so that the users don't need to VPN into the network it'll connect automatically via a secure tunnel (sort of like VPN). This requires that the remote machines are members of the domain (hence my second question).

What errors are the users getting when connecting?

share|improve this answer
The clients are Windows 7. They are not members of the domain. The errors are that the server cannot be reached or that the credentials are not accepted. I thought maybe there could be a problem in that the clients are not using the remote gateway as a default for VPN (so their Internet access goes outside the VPN tunnel) - maybe the client is trying to access the file share outside the VPN? – Martin Wiboe Oct 4 '11 at 9:35
They shouldn't be, but it is possible. That would account for server cannot be reached errors but not credentials not being accepted. Starting with the machines that can't connect to the server, can they ping the server? What shows up when the run a tracert to the server? – mrdenny Oct 4 '11 at 18:51
Seeing your comments above, if they can ping the server then the traffic is going the right way. It's just IP based traffic. Is the firewall on the server setup correctly? How about on the clients? Can you telnet from the client to port 139 on the server? – mrdenny Oct 4 '11 at 18:52
The traffic seemed to be unproblematic, and after tinkering with it it now seems to work, as long as NetBIOS over TCP/IP is enabled in VPN connection settings. It is still very slow though (and I can RDP to the server and have basically no lag at all) – Martin Wiboe Oct 4 '11 at 23:31

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.