asked on

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.

SOLUTION

wei2ali

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

ASKER CERTIFIED SOLUTION

nazirahmed

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

bleujaegel

ASKER

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!

nazirahmed

Glad it worked.
cheers