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!
Best Answer
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. http://www.fishbrains.com/2009/03/12/ping-windows-2008-with-firewall-on/
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.