Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1391
  • Last Modified:

VPN client error 'The network path cannot be found'.

I have a Windows 2003 test domain with a multihomed DC, and a member (file) server connected to the LAN adapter of the DC.  I published a share from the file server to active directory and am trying to access it via remote VPN client.  I can ping the file server from the remote client, but 'net view' gives me error 53 ('net view' will show me the shares on the DC however).  I can successfully map a network drive on the remote client of a share on the DC.  I can also map a network drive on the DC of the share on the file server.  I'm not sure why this traffic isn't getting through the DC to the file server (or back).  Any ideas are greatly appreciated.
0
bleujaegel
Asked:
bleujaegel
  • 2
2 Solutions
 
wei2aliCommented:
It depends on how your network is configured.

What's the IP-address you leased for you VPN-client? I believe that the VPN-client can only see the portion of network of its own subnet?
0
 
nazirahmedCommented:
Hi
Check the DNS and WINS setting.Also verify that either the protocol is enabled for routing or the Entire network option is selected for LAN protocols being used by the VPN clients. if you have enabled netbuie and there is router in between, try to enable UDP ports 137 and 138 and TCP port 139 across all routers and firewalls between the PPTP/VPN client and PPTP/VPN server.
Make sure the default gateway points to the remote network rather than to the ISP (if thee is an isp involved)

did you try that?
 h: \\serverip\sharename
0
 
bleujaegelAuthor Commented:
Thanks guys!  I finally got it figured out.  Zone Alarm on the client was blocking the traffic.  It didn't make sense logically though.  I figured since I could map a network drive to the DC, and ping the file server by name that this wouldn't be a problem.  I thought that since they were on the same subnet everything would pass.  Anyway, Wei2Ali's suggestion helped because my VPN server had assigned the dreaded 169.254.x.x address to client.  I restarted RRAS, then DHCP and then it gave clients the 192.168.x.x address.  Then I used Nazirahmed's suggestion to check the firewall.  Well I had them disabled on the servers for testing purposes.  So as a last resort I shut down the clients firewall and shazam.  I configured a static route through Zone Alarm and everything is fine!
0
 
nazirahmedCommented:
Glad it worked.
cheers
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now