IWETHEY v. 0.3.0 | TODO
1,095 registered users | 0 active users | 0 LpH | Statistics
Login | Create New User
IWETHEY Banner

Welcome to IWETHEY!

New Re: Here's a strange one . .
169.254.x.x is the "Automatic Private IP Address" that WinX machines define for themselves when they can't find a DHCP server.

[link|http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winxppro/reskit/prjj_ipa_eiih.asp|MS Technet article]

Automatic Private IP Addressing (APIPA) allows home users and small business users to create a functioning, single subnet TCP/IP network without the use of either static addressing or a DHCP server.

Manually configuring IP addresses can be tedious work in all but the very smallest networks and is prone to human error. Generally, autoconfiguration is a better choice. APIPA allows a Windows XP Professional client to assign itself an IP address in the following circumstances:

The client is configured to obtain a lease DHCP, but a DHCP server cannot be found, is unavailable, or is not used (for example, in a small office/home office network).
The client used DHCP to obtain a lease, but the client's attempts to renew the lease through a DHCP server have failed.
In these cases, the Windows XP Professional client selects an IP address from the range of IANA-designated, private class B addresses (169.254.0.1 - 169.254.255.254) with the subnet mask 255.255.0.0. The client performs duplicate-address detection to ensure that the IP address that it has chosen is not already in use. If the address is in use, the client will select another IP address up to 10 times. After the client has selected an address that is verifiably not in use, it configures the interface with that address. In the background, the client continues to check for a DHCP server every five minutes. If a DHCP server is found, the APIPA autoconfiguration information is abandoned and the configuration offered by the DHCP server is used instead.


I'd look for 1) DHCP server out of addresses and other configuration problems 2) Proper NIC setup on client machine 3) cabling issue 4) hub/switch issue
-----
Steve
New Thanks - that explains the address.
Now we can get to the find the problem. DHCP server is ok and accessable to the two machines that work and has plenty of addresses.
[link|http://www.aaxnet.com|AAx]
     Here's a strange one . . - (Andrew Grygus) - (9)
         Dhcp out of addresses? - (Silverlock) - (2)
             Doesn't seem so . . - (Andrew Grygus) - (1)
                 A bad card can cause a lot of bad addresses - (Silverlock)
         Virus checker found nothing. -NT - (Andrew Grygus)
         Re: Here's a strange one . . - (Steve Lowe) - (1)
             Thanks - that explains the address. - (Andrew Grygus)
         Resolved: Hub Jam - (Andrew Grygus) - (2)
             This happened to me before - (nking) - (1)
                 No, DSL was working fine . . - (Andrew Grygus)

My other car is an LRPD.
36 ms