ajness
asked on
VPN connects, but a network drive is not accessible still
I have a user that can connect to the office VPN with no problems. If he does so outside of his home, it works fine. I've tested the laptop from my home location and been able to connect to the shared drive, and from the office on a different subnet connects to the shared drive as well. The only time we have a problem is when he is working from his home, which naturally is where he needs to us it!
I have made a few site visits to his home. I have tried my own laptop on his network and failed also. I took my own router over, which I know works, and swapped it with his existing home office router/firewall. I was sure that was going to fix it but it didn't. Here's the configuration:
Laptop -> Docking station with it's own NIC -> SOHO router -> Cable Modem
There is also a wireless router connected into the SOHO router but I've tried connecting to the share with and without the wireless and it's the same behavior either way. What I've tried:
User Laptop in the docking station: Fails to connect to share, connects to VPN ok
User Laptop off the docking station: Fails to connect to share, connects to VPN ok
My own laptop off the docking station: Fails to connect to share, connects to VPN ok
Swapping out my router for his, using his laptop: Fails to connect to share, connects to VPN ok
We can ping the remote gateway, and we are able to see the private IP for the remote router (192.168.0.1) pinging anything else on the 192.168.0.x subnet does not work.
It acts exactly like I'd expect if there was a firewall at his home, blocking shared traffic. I've triple checked and there just isn't a firewall on the laptop, and I know for sure that my router allows shared traffic since I use it all the time.
In case it matters, the VPN is IPSEC via Netgear FVS.
Anyone know how to solve this?
I have made a few site visits to his home. I have tried my own laptop on his network and failed also. I took my own router over, which I know works, and swapped it with his existing home office router/firewall. I was sure that was going to fix it but it didn't. Here's the configuration:
Laptop -> Docking station with it's own NIC -> SOHO router -> Cable Modem
There is also a wireless router connected into the SOHO router but I've tried connecting to the share with and without the wireless and it's the same behavior either way. What I've tried:
User Laptop in the docking station: Fails to connect to share, connects to VPN ok
User Laptop off the docking station: Fails to connect to share, connects to VPN ok
My own laptop off the docking station: Fails to connect to share, connects to VPN ok
Swapping out my router for his, using his laptop: Fails to connect to share, connects to VPN ok
We can ping the remote gateway, and we are able to see the private IP for the remote router (192.168.0.1) pinging anything else on the 192.168.0.x subnet does not work.
It acts exactly like I'd expect if there was a firewall at his home, blocking shared traffic. I've triple checked and there just isn't a firewall on the laptop, and I know for sure that my router allows shared traffic since I use it all the time.
In case it matters, the VPN is IPSEC via Netgear FVS.
Anyone know how to solve this?
Have you made sure the IP ranges are in different subnets, my guess is that the cable modems LAN port is in the same IP range as your office.
ASKER
I know how to access the router/firewall, but how would I tell if the cable modem's LAN port is in the same IP range?
you bypass router and connect directly to the modem, do an ipconfig and check what IP address you'll be pulling...now reconnect pc back to router and do an ipconfig and double check the IP addresses...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
snerkel: thanks I'll give it a shot.
TeeSeePeeEyePee: I'd do that but it's an IPSEC connection with some rather specific settings; I've only been successful going through the ProSafe VPN Client in establishing the VPN connection. Also, it works just fine from anyplace besides his home, so that would not be a user profile issue, correct?
TeeSeePeeEyePee: I'd do that but it's an IPSEC connection with some rather specific settings; I've only been successful going through the ProSafe VPN Client in establishing the VPN connection. Also, it works just fine from anyplace besides his home, so that would not be a user profile issue, correct?
That sounds correct. If it is a ProSafe software client connecting to a hardware VPN on the NetGear at the office, definitely try ataridex's advice and hook the laptop up directly to the cable modem (wouldn't hurt to get the docking station out of the loop, too, if the network card is internal to the laptop).