My workplace offers a Cicso VPN which I am trying to use from home (via ADSL) to work remotely. I believe the workplace's VPN is IPSec, as it requires me to have an IPSec ID and an IPSec secret to connect.
Connecting the VPN tunnel works fine, but it stops transmitting bytes soon after, making it impossible to do anything useful.
The interesting thing is that I can work just fine by using my mobile phone (4G) as a wireless access point and connect my laptop to that instead of my home's WiFi router attached to the ADSL modem.
I contacted my ISP about this problem and got an email response in which the following (among other things) was suggested:
- Enable Port Forwarding for the VPN port 500, ( for IPSec VPN's), port 1723 for PPTP VPN's, and port 1701 for L2tp- L2tp routing and remote access. Port 500 may be listed under the list of services. [...] Note: Check if the WAN IP is Public or Private. Ports can be opened on Public IP addresses only.
Is port forwarding technically really required client-side? If that was true, wouldn't that also prevent other people on my home network from doing the same thing from their laptops (say, if one of my co-workers visited my home and also wanted to connect to the office's VPN)?
- By default the router's firewall is configured to drop (delete) ICMP packets sent from outside your network to the WAN port. Your VPN may require the ICMP packets.
Again, is this necessary for getting a Cisco VPN operational on client-side?
Or, in other words: Has anyone using such a Cisco VPN had to open ports on their modem/router from where they want to connect to the VPN endpoint?