Discussion Locked

Two networks can't see each other

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

A company I work with recently decided to share an office with another company. They wanted to keep the networks separate. So what we did is got a separate IP range from their ISP and had that range routed to our firewall. Everything works fine, except company 1 can't connect to any of the machines on comapny 2's network. Here's a pic to help explain this better:

router (2 sep. valid IP ranges)
| |
co1 firewall CO2 proxy server
| | |
DMZ internal co1 internal co2

Both company 1 (CO1) and company 2 (CO2) can access the internet all everythign just fine, but if someone from CO2 tries connecting to one of the machines i the DMZ of CO1 the connection cannot be made. Also, CO1 cannot ping even the external address of CO2's proxy server.

I know the problem has to be with the router somehow, but can't figure it out. Any suggestions would be much appreciated!

3 replies

by cryspaluz

Sorry about the diagram, it got messed up when posted. Hopefully this will be better:

router -> CO1 firewall -> CO1 DMZ and CO1 Internal

same router -> CO2 proxy -> CO2 Internal range

by timwalsh

I suspect this is a router configuration issue. You may need to create a static route between the two networks in the router. Whoever configured the router probably took you at your word ("to keep the networks separate") and didn't create a route between the two)

by colin_joseph

The way firewalls work, not only do you have to include routes from each network to the other, but you must also explicitly permit traffic from one DMZ to the other. By default, high security interfaces (DMZ1 and 2) can access lower security interfaces (outside IP addresses) without a problem. For traffic to flow from EQUAL or LOWER security interfaces (from DMZ to DMZ), a rule must be explicitly specified. Just my two cents.

This discussion is closed to new replies.