Discussion Locked

Connecting two LANS via VPN

0 helpful
11 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am running a VPN client on Windows 98 using Checkpoint's VPN-1 SecuRemote 4.1 SP1 3DES along with their Firewall-1 Authentication Agent and connecting to my company's network using cable modem access to the web. I purchased a Linksys Etherfast Cable/DSL Router (BEFSR81) with IPSec Pass-Thru. Prior to installing the router I had no problems with my VPN connection. After installing the router I am able to get authenticated by my company's Checkpoint server (I enter my username an password and receive authentication from the Checkpoint software). However, I still cannot see my company's servers behind the firewall. I cannot ping any of their servers. My internet connection is fine and I can ping any website and use my web browser (I.E.5.5) to surf.

Currently I have only one computer on my home LAN. It is set up with a static IP address. I opened up the following port ranges 47-2010, 21, 23, 25 and had traffic forwarded to the static IP address of my one computer. These were the port ranges suggested by Linksys' help desk.

Any ideas why I cannot see my company's network? I have talked to my sys admin and Linksys tech support but with no luck. Unfortunately we do not have support from Checkpoint.

11 replies

by rabbit_runner

This sounds like a 'route statment' problem. From you comments, I assume that the Linksys router is installed at your home to secure your home pc. However, prior to its installation, you were able to connect just fine. After, it was installed, your connection to your work LAN is only 'one way'. This means you can surf the web, connect to your Checkpoint firewall at work, but your 'work LAN' does not know how to connect BACK to you, through the Linksys. You may have to install a route statement in the Linksys, but this may compromise your security.
My answer may be totally 'off base' but I am trying to work with what you have given. I do not think the problem is with ports. I think it is a route statement. If you have already opened upthe ports, then, that is not your answer.
I would like to pursue this further. If you think my answer is wrong, then discard it. But it is worth checking.
Best of luck

by rodbailey

Sorry for holding up your rating. My sysadmin has it resolved. Don't know what the issue was.

by estebandelatorre

Ping from home your firewall private address, if you can, should allow firewall?s traffic or ports to reach your servers
(login first to firewall!)

by rodbailey

I tried that already. I can't even ping the firewall server even after getting authenticated by the firewall, which is really strange.

by estebandelatorre

so, probably your vptunnel ip ending address is wrong. It should be the same as the firewall private address.
Am I wright?

by rodbailey

Sorry for holding up your rating. My sysadmin has it resolved. Don't know what the issue was.

by estebandelatorre

Also, pinging a firewall (both from lan or wan side) is not allways possible, due to the fact that most firewalls are not configured to respond or echo icmp (ping) requests.

This discussion is closed to new replies.