A relevant piece of information might be *which* windows?

Win2K for example has a very nonstandard way of of talking
to loopback/localhost (127.0.0.1). Specifically, it uses
a large MTU which introduces all sorts of timing problems
in the TCP/IP stack. Not a problem with NT.

So it wouldn't be surprizing if there were also serious
problems introduced when using .255 as a host rather than
broadcast addy. Possibly also having to do with MTU's.

Who knows what evil lurks in the heart of Redmond?

<advocacy>
Aww...just switch to linux! :-) At least then there's a
hope of diagnosing and fixing the problem at the source,
rather than "trying things" until something works.
</advocacy>

Cheryl

On Fri, 4 Jan 2002, Jim wrote:

> > I would contend that this is not a Telecom problem but a CPE problem!!
> > After all the network is the same for Chrissy and the customer who Craig
> > traceroute'd below.
>
> Just a note, I have had problems with windows machines involving a .255
> address. It didn't matter that it wasn't actually the broadcast address for
> the subnet - windows had a fit anyway, and various things didn't work as
> expected. Nothing really stopped working altogether, just behaved
> strangely. Changing the machine to another (non-zero, non-255 address)
> fixed the 'problems'.
>

-- 
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