Welcome to ISAserver.org

Static Routes

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> Network Infrastructure >> Static Routes

Page: [1]

Message

<< Older Topic Newer Topic >>

Static Routes - 7.Apr.2005 9:54:00 PM

SmokeNMirrors

Posts: 3
Joined: 7.Apr.2005
From: Torrance, CA
Status: offline

ISA 2004 is my back firewall in a front-back firewall configuration. I've recently installed a second front firewall, which provides a encrypted route to a customer of ours.

I know that the 2nd firewall and route to the customer is good, the route works fine on a machine connected straight to it.

The static route sort of works. When I ping the client's address space, the fist ping gets a reply, but all the rest are dropped. This happens on both the ISA server and clients behind it.

Am I missing something? I can't come up with any reason for this behavior...

Do I have to put the 2nd firewall in a DMZ or something?

Jeff

[ April 07, 2005, 10:28 PM: Message edited by: Smoke N Mirrors ]

Post #: 1

Featured Links*

RE: Static Routes - 7.Apr.2005 10:33:00 PM

WyldWolf

Posts: 246
Joined: 3.Mar.2005
From: Wisconsin
Status: offline

What does your route table and gateway's look like on the ISA server? It sounds like you may have a device (either ISA or another hop) that had more than one default gateway which is incorrect.

(in reply to SmokeNMirrors)

Post #: 2

RE: Static Routes - 14.Apr.2005 5:06:00 PM

SmokeNMirrors

Posts: 3
Joined: 7.Apr.2005
From: Torrance, CA
Status: offline

Here's the route table on the ISA server:
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.121.1 192.168.121.62 20
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.121.0 255.255.255.0 192.168.121.62 192.168.121.62 20
192.168.121.3 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.4 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.5 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.6 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.7 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.8 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.9 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.10 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.39 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.51 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.52 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.53 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.54 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.55 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.56 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.62 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.121.255 255.255.255.255 192.168.121.62 192.168.121.62 20
192.168.180.0 255.255.255.0 192.168.121.254 192.168.121.62 1
xxx.yyy.31.0 255.255.255.0 xxx.yyy.31.254 xxx.yyy.31.254 20
xxx.yyy.31.254 255.255.255.255 127.0.0.1 127.0.0.1 20
xxx.yyy.31.255 255.255.255.255 xxx.yyy.31.254 xxx.yyy.31.254 20
224.0.0.0 240.0.0.0 192.168.121.62 192.168.121.62 20
224.0.0.0 240.0.0.0 xxx.yyy.31.254 xxx.yyy.31.254 20
255.255.255.255 255.255.255.255 192.168.121.62 192.168.121.62 1
255.255.255.255 255.255.255.255 xxx.yyy.31.254 xxx.yyy.31.254 1
Default Gateway: 192.168.121.1
===========================================================================
Persistent Routes:
None

So, everything but traffic to 192.168.180.0 should be routed through to 192.168.121.1 (the ip of my 1st front firewall). Traffic to 192.168.180.0 should route through 192.168.121.254 (the new, 2nd front firewall). But, it doesn't... The route tables on both the front firewalls only have default gateways on there external ports and the gateway is the same cisco router. What's got me baffled is, I put the same route table on a linux box, and access both networks just fine. I have created the route using both the route command and using RRAS, both with the same result.

Jeff

[ April 14, 2005, 05:15 PM: Message edited by: Smoke N Mirrors ]

(in reply to SmokeNMirrors)

Post #: 3

RE: Static Routes - 14.Jun.2005 4:53:00 PM

SmokeNMirrors

Posts: 3
Joined: 7.Apr.2005
From: Torrance, CA
Status: offline

Turns out it was nothing I was doing. My ISA server was interfacing with a faulty piece of hardware. Once that was swapped out, everything worked fine.

(in reply to SmokeNMirrors)

Post #: 4