"Steve Winograd [MVP]" wrote:

> In article <904B666F-FCAB-4627-BCDF-915DB13C0***@microsoft.com>,
> patb63 <pat***@discussions.microsoft.com> wrote:
> >Not sure what's going on, but I have a range of IP addresses I can't ping.
> >They are in the range of 169.254.241.whatever. I try to do a "tracert" and I
> >can't even ping my local server using that address. Any other addresses seem
> >to work okay.
> >
> >These addresses are pointing to off site devices that we occaisionally
> >access for diagnostic work. I am using Windows XP Professional SP-1 on a Dell
> >laptop.
> >
> >Any ideas?
> >
> >Thanks.
>
> Windows XP assigns a 169.254.x.x address to a network connection when:
>
> 1. The connection is configured to obtain an IP address automatically.
>
> and:
>
> 2. It can't communicate with a DHCP server to get an IP address
> assignment.
>
> Is there a DHCP server on the network?  If so, it isn't functioning,
> or it has run out of available addresses, or something else is
> preventing it from assigning addresses.
>
> If there's no DHCP server on the network, these addresses are normal.
> In that case, you can manually assign static addresses in one of the
> ranges reserved for private networks:
>
>    10.0.0.0 - 10.255.255.255
>    172.16.0.0 - 172.31.255.255
>    192.168.0.0 - 192.168.255.255
> --
> Best Wishes,
> Steve Winograd, MS-MVP (Windows Networking)
>
> Please post any reply as a follow-up message in the news group
> for everyone to see.  I'm sorry, but I don't answer questions
> addressed directly to me in E-mail or news groups.
>
> Microsoft Most Valuable Professional Program
> http://mvp.support.microsoft.com
>

>> >Not sure what's going on, but I have a range of IP addresses I can't ping.
>> >They are in the range of 169.254.241.whatever. I try to do a "tracert" and I
>> >can't even ping my local server using that address. Any other addresses seem
>> >to work okay.
>> >
>> >These addresses are pointing to off site devices that we occaisionally
>> >access for diagnostic work. I am using Windows XP Professional SP-1 on a Dell
>> >laptop.
>> >
>> >Any ideas?
>> >
>> >Thanks.
>>
>> Windows XP assigns a 169.254.x.x address to a network connection when:
>>
>> 1. The connection is configured to obtain an IP address automatically.
>>
>> and:
>>
>> 2. It can't communicate with a DHCP server to get an IP address
>> assignment.
>>
>> Is there a DHCP server on the network?  If so, it isn't functioning,
>> or it has run out of available addresses, or something else is
>> preventing it from assigning addresses.
>>
>> If there's no DHCP server on the network, these addresses are normal.
>> In that case, you can manually assign static addresses in one of the
>> ranges reserved for private networks:
>>
>>    10.0.0.0 - 10.255.255.255
>>    172.16.0.0 - 172.31.255.255
>>    192.168.0.0 - 192.168.255.25
>
>Steve,
>Thanks for the reply. I think it is something specific to my laptop because
>other PCs on the same server as me can ping the off-site IP addresses. My
>laptop times out on thesed particular IP addresses. Even when I do the
>tracert, the command times out without even finding my local server.
>
>Any other ideas?