Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I've set up a single hosted server to use as a development environment for a web-based application. The web app is served up fine on port 80, however I'm struggling to get my VPN to behave how I'd expect so the developers don't have the access they require.

The VPN connects fine and I can access the back-end database (SQL Server) which resides on the server with the client tools from the laptops. However they cannot access any shared folders.

The server's local IP address is 10.x.x.x, and I've assigned a static IP address pool to RRAS (of 192.168.100.1 - 20). The clients pick up a valid IP Address (i.e. 192.168.100.9) when they connect. There is no name resolution setup, DNS or WINS. When connected via VPN the clients can ping the server (192.168.100.1) by IP Address, but cannot map a drive to a shared folder (net use * \\192.168.100.1\xxxxx) - I get 'System error 53 has occurred. The network path was not found.' I don't understand why I can ping by the ip, but not map by it.

Some details:

  • Server OS is Windows 2008 (Datacenter)
  • VPN is SSTP using RRAS
  • Clients are all Windows 7
  • I've tried temporarily disabling the firewalls

So, why can we not access the file system when everything else (ping, RDP, SQL Server clients tools) works?

Thanks for your help

Duncan

Edit: Even if you don't know the answer, just a simple "yes, if it's configured correctly this should work" would be helpful.

share|improve this question
    
how did you do this please as im having the same problem?? –  ehughes Feb 4 '11 at 21:17
    
@ehughes - if you want to see how someone fixed their problem, try and find the answer that has the tick checkmark against it. On this question it's here: serverfault.com/questions/147117/… –  Mark Henderson Feb 4 '11 at 21:18
    
Can you elaborate what do you mean by "added a client-side static route to pass any traffic for the server's "local" ip address via the address it got from the RRAS static pool"? Did you have to do that in every client or only on the RRAS server itself? I'm having the same issue and had been spending days trying to resolve it. If you can let me know the exact steps that would be great. Thanks –  user75165 Mar 20 '11 at 18:26
    
I didn't need to add the static addresses to the clients, just the server I believe. This was almost a year ago now so I'm afraid I can't recall the exact steps I took. –  DuncanDavies Mar 21 '11 at 10:15
    
you mean there is something that's not automatically created by RRAS and you had to manually add something in? I'm really interested to find out as I still don't have a clue. If you can think of anything, any hint at all, I'd like to try... –  user75165 Mar 22 '11 at 0:55
show 1 more comment

1 Answer

up vote 1 down vote accepted

This was down to the MS File and Printer sharing not binding to the IP Address assigned to the server from the RRAS static pool. As soon as I added a client-side static route to pass any traffic for the server's "local" ip address via the address it got from the RRAS static pool then everything started working.

share|improve this answer
add comment

Your Answer

 
discard

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.