General discussion

Locked

Routing on NT4

By rakesh.chawda ·
Routing on NT4
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 leaseline 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 canping the 192.168.1.0 range of addresses. is there any other route i need to add to our firewall or the remote one. theres nothing on our Firewall policy to deny this traffic

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.

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

All Comments

Collapse -

Routing on NT4

by Rabbit_Runner In reply to Routing on NT4

From my experience, I would say that your problem is the communication between your Internal Net and your Firewall. Do your workstations have a default gateway which points to your firewall? From the note you posted, there was no diagram for me toobserve. But from what you stated, check the gateway on your internal network.

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 agibbs In reply to Routing on NT4

I think your Firewall's OK. Double-check the default gateway/router config on the 192.168.1.0 network's end. Sounds like packets are getting to them OK but they can't get them out!

Also remember that the 192.168.0.0/16 network is sortof a "reserved" range -- i.e. you won't find any 192.168.x.x internet websites. The InterNIC excluded the 192.168 class B from Internet usage, just so companies could use it on their LAN and never have to worry about conflicting with another address on the Internet. Your 192.168.1.0/24 network would fall into this category.

It could be your firewall is "assuming" that your 192.168.1.0 traffic is local and not forwarding it properly. I've seen ISP's do this before as a security measure -- that way you couldn't spoof a 192.168.x.x address and hack into someone's LAN through the Internet.

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 Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums