ISA Server (2004) detected routes through adapter "External" that do not correlate with the network element to which this adapter belongs. The address ranges in conflict are: 192.0.0.192-192.0.0.192;. Fix the network element and/or the routing table
- From: "Tristan" <tristan@xxxxxxxxxxxx>
- Date: Wed, 18 Jan 2006 21:51:47 +1300
Hi,
Just upgraded ISA 2000 to ISA 2004. I exported ISA 2000 settings during the
upgrade process and it reimported them into ISA 2004.
Everything seems to work fine, but I'm getting alerts saying that my network
is configured wrong.
Here is the message:
Event Type: Error
Event Source: Microsoft Firewall
Event Category: None
Event ID: 14147
Date: 18/01/2006
Time: 8:28:02 p.m.
User: N/A
Computer: PCISERVER
Description:
ISA Server detected routes through adapter "External" that do not correlate
with the network element to which this adapter belongs. The address ranges
in conflict are: 192.0.0.192-192.0.0.192;. Fix the network element and/or
the routing table to make these ranges consistent; they should be in both or
in neither. If you recently created a remote site network, check if the
event recurs. If it does not, you may safely ignore this message.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
My routing table looks like this:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator>route print
IPv4 Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x3 ...00 09 6b a5 28 21 ...... Broadcom NetXtreme Gigabit Ethernet - Packet
Sch
eduler Miniport
0x20002 ...00 07 e9 1f 4f 7e ...... IBM Netfinity 10/100 Ethernet Security
Adapt
er 2 #2 - Packet Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.3 192.168.0.2 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.0.0.192 255.255.255.255 192.168.16.18 192.168.16.18 1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 20
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 20
192.168.16.0 255.255.255.0 192.168.16.18 192.168.16.18 20
192.168.16.18 255.255.255.255 127.0.0.1 127.0.0.1 20
192.168.16.255 255.255.255.255 192.168.16.18 192.168.16.18 20
224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 20
224.0.0.0 240.0.0.0 192.168.16.18 192.168.16.18 20
255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1
255.255.255.255 255.255.255.255 192.168.16.18 192.168.16.18 1
Default Gateway: 192.168.0.3
===========================================================================
Persistent Routes:
None
In ISA Management - Firewall Policy - Toolbox - Network Objects - Network -
Internal.
It has an IP Address range setup as: 192.0.0.192 - 192.0.0.192.
After installing ISA04 I used the SBS03 Internet Configuration Wizard.
I'm really not that good with working out routing and what I need to change.
Can somebody help me out.
Thanks
Tristan
.
- Follow-Ups:
- Prev by Date: RE: Read Only in My Documents after adding to script
- Next by Date: Re: IIS (on SBS 2k) default website stopped 'address already in use'
- Previous by thread: IMF safe sender list
- Next by thread: Re: ISA Server (2004) detected routes through adapter "External" that do not correlate with the network element to which this adapter belongs. The address ranges in conflict are: 192.0.0.192-192.0.0.192;. Fix the network element and/or the routing table
- Index(es):
Relevant Pages
|
