XP SP2 Wrong IP on connection

I have a strange issue with the establishing a wireless connection to a DHCP
Router (D-Link 624). System is XP SP2.

The IP shown on the XP machine is 169.254.171.218, but the Router says it
assigned 169.254.0.15. The Router IP is within the DHCP assignment range.

Once the Repair is run on the connection, all is correct.

All Help is appreciated.

TIA
Dick

Are there any specific reason why you set the ip to start with 169?
Can you change the ip range to 168.x.x.x and see what happens? Since 169 is
invalid ip address.

Yi (MSFT)

"D Wells" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I have a strange issue with the establishing a wireless connection to a
>DHCP
> Router (D-Link 624). System is XP SP2.
>
> The IP shown on the XP machine is 169.254.171.218, but the Router says it
> assigned 169.254.0.15. The Router IP is within the DHCP assignment range.
>
> Once the Repair is run on the connection, all is correct.
>
> All Help is appreciated.
>
> TIA
> Dick
>
>

"Yi Chen [MSFT]" <(E-Mail Removed)> wrote in message
news:uYMYk%(E-Mail Removed)...
> Are there any specific reason why you set the ip to start with 169?
> Can you change the ip range to 168.x.x.x and see what happens? Since 169
> is invalid ip address.
>
How about 192.168.xxx.xxx?
Certainly the 169.254.xxx.xxx should not be used.

I think Yi Chen meant in the 192.168.x.x range. =)

Unless the ip address was changed in the D-Link router, the default ip
address for the LAN should already be set to use the 192.168.0.x range and a
subnet mask 255.255.255.0.

_____________
Eric Cross
Microsoft MVP (Windows Networking)
http://mvp.support.microsoft.com


"Jim Fox" <(E-Mail Removed)> wrote in message
news:XuqdndeIQ-3zICrcRVn-(E-Mail Removed)...
>
> "Yi Chen [MSFT]" <(E-Mail Removed)> wrote in message
> news:uYMYk%(E-Mail Removed)...
>> Are there any specific reason why you set the ip to start with 169?
>> Can you change the ip range to 168.x.x.x and see what happens? Since 169
>> is invalid ip address.
>>
> How about 192.168.xxx.xxx?
> Certainly the 169.254.xxx.xxx should not be used.
>