Correct. Probably before you assigned it an IP, it gave itself that IP. ---- Julian
On Sat, Nov 3, 2012 at 8:57 PM, DSinc <[email protected]> wrote: > Jamie, > Yes. Yes. I managed to also find this info also. OK. > My quest is NOTa bad inbound address? > It is just my machine? > Duncan > > > On 11/03/2012 18:39, Jamie Furtner wrote: >> >> The addresses 169.254.1.0 to 169.254.254.255 are for the APIPA (Automatic >> Private IP Addressing or link-local) network - check >> http://en.wikipedia.org/wiki/Apipa#IPv4 for more details. Devices will >> configure themselves with an address in that network if they are unable to >> contact a DHCP server and they don't have a static IP address set. They are >> not routable addresses, and your ISP shouldn't be letting them propagate >> past its boundary. >> >> Configure DHCP and ensure that the computer can contact the DHCP server >> (check the network cable & router/switch). >> >> I don't use a dedicated application for doing traceroutes. I use tracert >> from a command prompt on Windows, or traceroute on Linux (this has the >> advantage that they're always present - nothing new to install) - so I can't >> comment on a replacement application. >> >> Jamie >> >> On 2012-11-03 3:00 PM, DSinc wrote: >>> >>> I currently use Neo-Trace v3.25. I think this sw is going lame. >>> >>> I tried to update it and my ESET SW said No-Go. >>> >>> Fine. Is there another proggy I can use instead? >>> No, I do not wish to go back to tough machine-based proggies. >>> >>> But,...ATM....I'd really like to find out Who-Is IP addy: >>> 169.254.93.208...... ??? >>> This IP Addy seems to live deep inside my [Test] machine. >>> Hmm.................. ? >>> Duncan >>> >> >
