Michael,
Thanks. I completely forgot about the TCPIP/IP stack. ESET screamed
about this early in
their V3 and then their V4 versions. I totally blew this XP glitch off.
I've never seen it before!
Well, maybe I have it now! I printed the directions, and, dl'd the MG
glop. Funny. Because
I've had this tool archived since 2005! I forgot about it!
I'll wind this up and see what happens.
Ultimately, I erase the c:\ partition of this PC and start all over with
Win7pro!
Truly no harm, no foul....................... :)
L8R,
Duncan
On 11/05/2012 23:13, Michael Resnick wrote:
In the past I've had 169.x.x.x IP addresses assigned.
In my experience my problems were caused by a corrupted winsock stack.
The one tool that seemed to work all the time is WinSock XP Fix which
can be downloaded at:
<http://www.majorgeeks.com/WinSock_XP_Fix_d4372.html>http://www.majorgeeks.com/WinSock_XP_Fix_d4372.html
.
If you want to do it manually, Microsoft describes a procedure here:
<http://support.microsoft.com/kb/811259>http://support.microsoft.com/kb/811259
The Winsock Fix utility makes it real easy (just a single mouse click
required) and backs up your registry before making any changes.
I have used this utility multiple times and it has never caused any
problems and has always fixed the winsock problems,
Regards,
Mike
At 07:57 PM 11/3/2012, DSinc 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
__________________________________________
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety." (Benjamin
Franklin, 1755)
