I'm not familiar with the Ni200's operation. But if it configures itself as a
pseudo network adapter, then the most likely conflict that jumps to mind is a
conflict for which route (/default route) to take. The LAN, or the Internet.

It shouldn't be noticable on a LAN if it's only a small lan using a
255.255.255.0 subnet mask, but if it's a reasonably large lan that uses a wider
subnet mask, or several blocks of IP's then it's a possibility.

Well, that, and yeah, there was something a while back about IP's having .255
in the IP itself. Windows machines having issues with it. If you got a static
IP like that it'd be another possible problem.

Jp.

Gavin wrote:

> Only 0 in the IP was the 210.xxx.xxx.xxx
>
> Got the IP changed for now but told the person in question that I doubt it
> would make any diference....
>
> Mark Foster writes:
>
> > A stab in the dark Gavin - If the IP contains a zero it could be an
> > Operating System issue.
> >
> > What kind of 'conflict' can an IP cause? an Ni200 is internal, so the IP
> > is issued to the interface on the machine itself - where else is it going
> > to conflict?
> --
> This message is part of the NZ ADSL mailing list.
> see http://unixathome.org/adsl/ for archives, FAQ,
> and various documents.
> To unsubscribe: send mail to majordomo@lists.unixathome.org
> with "unsubscribe adsl" in the body of the message
>

-- 
This message is part of the NZ ADSL mailing list. 
see http://unixathome.org/adsl/ for archives, FAQ, 
and various documents. 
To unsubscribe: send mail to majordomo@lists.unixathome.org 
with "unsubscribe adsl" in the body of the message