Welcome to ISAserver.org

Static Route to "Different" External Network

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> Network Infrastructure >> Static Route to "Different" External Network

Page: [1]

Message

<< Older Topic Newer Topic >>

Static Route to "Different" External Network - 11.Nov.2004 1:28:00 PM

iansutherland

Posts: 5
Joined: 11.Nov.2004
From: Burnley, Lancashire, UK
Status: offline

we have a Win2K RRAS server on out network that is used for an ISDN dial-up connection to another 3rd Party Network. We also have an ISA 2004 server as our default gateway for everything else.
I have configured a static route on the ISA server in RRAS to direct traffic for the 195.166.16.0 network to the Win2K RRAS server (10.10.10.3).
In the "Networks" section of ISA 2004 I have added the 195.166.16.0 network as a second range of addresses in the default "Internal Network". This works fine except that in the Application log we are getting the error:
"ISA server detected routes through adapter "Internal" that do not correlate with the network element to which the adapter belongs, the address ranges in conflict are: 195.166.13.0 - 195.166.13.0 fix the network element/routing table etc. etc.
Is there a better way of configuring this so I don't get the error. I would imagine there may be many instances where you need to route traffic to a different gateway, but I am reluctant to either add static routes on each client, or add another router between the network and the ISA server.