Why should Windows refuse to accept an IP just because there is a
conflict on the network? As long as that machine has a unique address,
why should it care about the duplicate? Makes it hard to troubleshoot
the network when your troubleshooting machine won't get an address.
Scott Lambert wrote:
On Tue, Dec 11, 2007 at 08:21:37AM -0800, Marlon K. Schafer (509) 982-2181
wrote:
Here's an example from yesterday. My new laptop is Vista (the old one has
a concrete floor induced broken screen). There is a device somewhere on my
network that is answering arp requests incorrectly. No matter what IP addy
I put on the Vista machine (or osx for that matter) it shows an IP address
conflict and resorts to a 169.x.x.x IP addy.
Any OS other than osx or Vista (both MS products these days) works just
fine. So I have a brand new laptop that won't work here and I'm gonna have
to waste who knows how much time tracing down a device, and spend money
replacing it, that is otherwise working just fine.
As much as I dislike Windows, you can't really blame that issue on
Windows. You have to blame that one on the bogus hardware which is
breaking arp...
like Quicken these days. I'd pay MORE for a program that just balanced my
checkbook and gave me some nice reports. I'm sick and tired of everyone
trying to force services and other crap down my throat.
http://moneydance.com/
--
Scott Reed
Owner
NewWays
Wireless Networking
Network Design, Installation and Administration
www.nwwnet.net
(765) 855-1060
--------------------------------------------------------------------------------
WISPA Wants You! Join today!
http://signup.wispa.org/
--------------------------------------------------------------------------------
WISPA Wireless List: wireless@wispa.org
Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless
Archives: http://lists.wispa.org/pipermail/wireless/
