Static Routes & Default Gateways

[Paul King]

Hi there - I would like some help please....

I have an Intenal LAN of 192.168.160.0/24. Our default CISCO gateway of
192.168.160.250 communicated to our other office network (Location B) on
192.168.161.0/24. Location B accomodates at present our mail server and
Proxy Firewall sever.

At Location A, we are now upgrading our system so that this specific
location can bypass Location B for internet access etc. We have therefore
employed a hardware firewall on 192.168.160.253 and placed policies on this
box.

Now, all the client workstations has at present a default Gateway of
192.168.160.250, but will migrate soon over to the .253

However in the meantime, we need to run as is.....

The issue is that we also have a Windows 2003.net server at Location A - and
the default gateway is set to the new firewall (192.168.160.253) - again no
problems yet!

We have started to design a corporate intranet hosted on the Windows
2003.net server, but we wish for the clients to see it before we do the
migration. Bearing in mind that, the Server is on a different default
gateway to the client workstations

Therefore, can I put in a static route to help me out here?

Regards
Paul.

 

[Phillip Windell]

Therefore, can I put in a static route to help me out here?

Yes.
The Firewall at *.253 must have a static route entered into it somewhere so
that it knows that it isn't to be used as the gateway for that but gateway
*.250 is to used instead. The Firewall probably also has a LAT of some
sort. This LAT must include the address range of both networks,...or just
use the full range of 192.168.0.0 -- 192.168.255.255 to cover it all in one
shot.

You could use static routes on each client to accomplish this, but that
isn't very scalable. Each subnet should have one primary "routing device"
acting as the Default Gateway for all subnet members, and then that "routing
device" should be what contains the static routes for "exceptions". This
keeps the subnet routing centralized and managable per each subnet.

 

[Robert L [MS-MVP]]

since server 2003 is in the 192.168.160 network, clients in location A
should work fine. For the clients in location B, you may need mortify the
routing table.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

 

[Jeff Cochran]

Hi there - I would like some help please....

I have an Intenal LAN of 192.168.160.0/24. Our default CISCO gateway of
192.168.160.250 communicated to our other office network (Location B) on
192.168.161.0/24. Location B accomodates at present our mail server and
Proxy Firewall sever.

At Location A, we are now upgrading our system so that this specific
location can bypass Location B for internet access etc. We have therefore
employed a hardware firewall on 192.168.160.253 and placed policies on this
box.

Now, all the client workstations has at present a default Gateway of
192.168.160.250, but will migrate soon over to the .253

However in the meantime, we need to run as is.....

The issue is that we also have a Windows 2003.net server at Location A - and
the default gateway is set to the new firewall (192.168.160.253) - again no
problems yet!

We have started to design a corporate intranet hosted on the Windows
2003.net server, but we wish for the clients to see it before we do the
migration. Bearing in mind that, the Server is on a different default
gateway to the client workstations

Therefore, can I put in a static route to help me out here?

Yes.

ROUTE -P ADD 192.168.161.0 MASK 255.255.255.0 192.168.160.250 METRIC 1

Jeff

 

[Paul King]

Thanks chaps.

Although I still feel that we may have a problem after adding a STATIC route
on our new Firewall. Each client machine has 192.168.161.1 entered in as
their proxy Server under Intenet Explorer.

Therefore if I change each client machine to the new gateway, will this have
a knock on effect for each browser?

Regards
Paul.