In article <c162vk$ho9$(E-Mail Removed)>,
(E-Mail Removed) says...
[snip]
> Don't know about LSP hijack, but I think your first suggestion would've done
> the trick.
>
> I say 'would' because I actually found a neat little application,
> winsockxpfix.exe, which essentially does the same thing, removes winsock
> entries from the registry and re-installs a fresh batch, then resets the
> TCP/IP stack as you suggested.
I had a customers XP box that looked to have a failed network card and
it would not renew the IP either. I found that it was a stack problem,
but I didn't want to wipe the machine....
I tried the net fix command as shown on the MS site, but it didn't work.
I had to export the WINSOCK and WINSOCK2 registry trees from a working
machine and import them to the broken machine - worked fine after that.
The was the first instance I've seen of this. It appears to have been
caused by a search bar type assistant program loaded by the owner of the
machine.
--
--
(E-Mail Removed)
(Remove 999 to reply to me)