!!!Cannot access remote network!!!

[Abernut]

Our company has recently started a second branch in another state. That branch has a business class service from their local provider. There are only a few PC's and a router that the local provider provided us. All of their PCs are on the 172.28.158.0 network, 172.28.158.1 being the Gateway.

Our home office is on the 172.28.159.0 network. We have a watchguard firewall and a Cisco 2800 series router in place.

We have a client VPN service running on our Watchguard wich allows users to access our network "172.28.159.0".

How can I set up our home office to be able to view the remote PC's, either through Windows Network Places. I cant even ping the remote PC's.

I think it has something to do with setting up the route in our Cisco, but I am not sure.

HELP

 

[burtsbees]

Depends on what kind of VPN...IPSec? L2TP? Have you considered Cisco EasyVPN in the 2800?

Burt

 

[Abernut]

We are using IPSec on our Watchguard.

To use Cisco's EasyVPN will I need a Cisco at our remote site. Curently there is just a Modem/Router that the Local (I think TimeWarner) company provided us which they do not let us manage. If so will I be able to access that network in a windows environment.

Thanks
Chip

 

[burtsbees]

I believe you do need a Cisco router at that end. What kind of connections? ADSL, by chance? I happen to have a Cisco 837 I am selling, if interested. Please know I am not using this thread to sell it---I was going to put it on Ebay for around $150, I've just been busy...well, actually lazy, too.

Burt

 

[dtrtel]

You mentioned having business class service at one endpoint. Does that include a static IP address? You will need a static IP (or setup with a dynamic DNS provider such as DynDNS) on at least office connection. Your connections must be configured to allow VPN pass-through and it is best to have the outside interface on your VPN concentrator (2800) to have a public IP as assigned by your provider. The remote site can be setup to establish your VPN tunnel (L2TP/IPSEC) and keep it alive, reconnecting always if it drops.

If you can verify the VPN tunnel is established but can't ping remote PCs, check your routing tables at both ends to make sure you have routes for your local and remote subnets.

If you are this far, pings may fail because of ICMP filtering by windows firewall or on one or both of the devices providing the connection.

Browsing PCs on the remote network can present a challenge. You may need as WINS server at local and remote and have them setup to WINS-proxy for local and remote networks.



--jeff

http://linkedin.com/in/JeffLynch