General discussion

Locked

Routing on NT4

By rakesh.chawda ·
I want to connect 2 networks together below is a diagram of what i want to acheive:
Basically we have a dedicated 10meg lease line to a remote network, on my side we have a checkpoint firewall with the 4th NIC connect to the lease line and on the remote firewall they have their NIC connect to the lease line. from their end they can ping any server on our internal network 10.0.0.0 mask 255.255.0.0 from their 192.168.1.0 mask 255.255.255.0 network.

After i added a static route on our NT checkpoint firewall:

route add 192.168.1.0 mask 255.255.255.0 10.1.0.1 (gateway address of the remote firewall Interface)

I can ping any server/ip address from our firewall. But the issue i have is no one behind our firewall can ping the 192.168.1.0range of addresses. is there any other route i need to add to our firewall or the remote one.

Our firewall has only one default gateway IP address which is the external Interface. the 10.1.0.1 gatway which i added is the remote firewall's interface. As my firewall can ping the remote internal network I feel i need to add the route on my firewall - Does anyone know what route i will need to add or any other helpful suggestions for my internal network to be able to see the remote one.

internal net --- checkpoint -- freebsd--- remote
10.0.0.0/16 10.1.0.2/24 10.1.0.1/24 192.168.1.0/24

Cheers

Raks

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Routing on NT4

by rakesh.chawda In reply to Routing on NT4

Point value changed by question poster.

Collapse -

Routing on NT4

by colang In reply to Routing on NT4

Did you communicate before adding the route?
It seems (if I not misundertanded) you have the external nic in your firewall with an address 10.x.x.x as the internal network.
If the external network is 192.168.ecc.ecc your external nic must have an 192.168.ecc.ecc address with same subnet mask otherwise your nic don't communicate on that network.
After adding route, the firewall will try anyway to send out a packet on that nic only because it is their default gateway but the clients cannot known the trick.
Try configure your external nic with 192.168.1.1 (or 192.168.1.2 if .1 is the other firewall) with subnet mask 255.255.255.0 and default gateway the address of the other firewall.
On the clients set the default gateway as internal ip address of your firewall.
Delete the route for network 192.168 (the firewall should know it as directly connected).
For any other network not known, the firewall will attempt to route the packets to its default gateway, we said the other firewall and all should work.

Hope it can be useful.
If not understood the question please tell me more.

Collapse -

Routing on NT4

by rakesh.chawda In reply to Routing on NT4

The question was auto-closed by TechRepublic

Collapse -

Routing on NT4

by gbjoe In reply to Routing on NT4

After you added the route, can the machines on 192.168.1.0 still ping your internal servers ?

If yes then I suggest you check your firewall's configuration. You may permit pings originating from the 192.168.1.0 and not 10.0.0.0.

Also check all your internal servers gateway to be sure they are pointing at the right address.

Use tracert (or traceroute) to see where the communication fails

During troubleshooting view your firewall's logs to see if any icmp packets are being dropped.
Are you doing any address translation ? If yes then check that also.

Hope this helps

Collapse -

Routing on NT4

by rakesh.chawda In reply to Routing on NT4

The question was auto-closed by TechRepublic

Collapse -

Routing on NT4

by Gregory W. Smith In reply to Routing on NT4

I suspect that the CheckPoint firewall is dropping PING packets.

Can you try other methods of communication?
say, http:\\192.168.0.3 if that server has IIS or some sort of Web service running? The firewall *should* allow http through :)

Collapse -

Routing on NT4

by rakesh.chawda In reply to Routing on NT4

The question was auto-closed by TechRepublic

Collapse -

Routing on NT4

by pdpjp In reply to Routing on NT4

Have you configure the clients with the Firewall as the default gateway.

Collapse -

Routing on NT4

by rakesh.chawda In reply to Routing on NT4

The question was auto-closed by TechRepublic

Collapse -

Routing on NT4

by rakesh.chawda In reply to Routing on NT4

This question was auto closed due to inactivity

Back to Networks Forum
10 total posts (Page 1 of 1)  

Related Discussions

Related Forums