Re: Duplicate ip addresses in network.
It is correct that 192.168 is private address range and can not go
accross the Internet. It is VERY BAD to have ANY duplicate ip addresses.
If these are on a host and only brought up in case of failure, I guess it
would work as long as only 1 address is up at a time. If it is to load
share, I would think using a one DNS name on different IP addresses would
Schahfer" To: <nv-l AT tkg DOT com>
r AT trw DOT com> Subject: [NV-L] Duplicate
ip addresses in network.
The network I work on has been customized with duplicate addresses of
192.168.10.150 and 192.168.10.151. These addresses were assigned to
a total of eight platforms/hosts (i.e., four have addess of 192.168.10.150
four have address of 192.168.10.151). The network architect felt it was
okay to do this because 192.168.10 is considered a "private network" and
is not routed over the network. The platforms with these addresses contain
additional network cards which are unique and which are what I really
want to monitor.
I have tried via a seedfile to get netmon to ignore these addresses
(i.e., !192.168.10.150-192.168.10.151) but netmon still finds the
addresses...because of the other network addresses in these platforms, I
I see in the NetView Diagnsis Guide the documented solution is to "Correct
problem in your network". However, it would be more desirable if I could
just get NetView to ignore the duplicate addresses. Does anyone know
another way to get NetView to ignore the duplicate addresses but still
rest of the platforms?
Thanks, Anne Schahfer
NV-L List information and Archives: http://www.tkg.com/nv-l