Can't talk to my LAN

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Recently I was infected by the "Where you Search" (or some such) tool bar. It was an application that showed up in Task Manager, I could kill it, but it would come back. About that same time I suddenly could not connect on my home LAN, my desktop wouldn't talk to the network (no address, no nothing). To get the bar off I finally edited the registery to delect any reference to it and it was gone, but I still couldn't talk to the network. Any association? Any suggestions?
 
Recently I was infected by the "Where you Search" (or some such) tool bar.
It was an application that showed up in Task Manager, I could kill it,
but it would come back. About that same time I suddenly could not
connect on my home LAN, my desktop wouldn't talk to the network (no address, no nothing).
To get the bar off I finally edited the registery to delect any
reference to it and it was gone, but I still couldn't talk to the network. Any association?
Any suggestions?
Click to expand...

When you say "no address" do you mean no IP address and if so, how did
you determine that? Can you check your network connection settings and
make sure (in the properties for your local network interface card) that
you have the TCP/IP protocol loaded and properly configured?
You should also make sure that toolbar didn't drop a HOSTS file on your
machine that is causing issues. On Win2K, if I remember correctly, that
would be in C:\Windows\system32\drivers\etc. It would be called HOSTS
(with no file extension). If you find one, try renaming it to something
else, like "HOSTS.OLD" or "OLDHOSTS".
 
"MVP-One wrote: ---- said:
Recently I was infected by the "Where you Search" (or some such) tool bar.
It was an application that showed up in Task Manager, I could kill it,
but it would come back. About that same time I suddenly could not
connect on my home LAN, my desktop wouldn't talk to the network (no address, no nothing)
To get the bar off I finally edited the registery to delect any
reference to it and it was gone, but I still couldn't talk to the network. Any association
Any suggestions?
Click to expand...

When you say "no address" do you mean no IP address and if so, how di
you determine that? Can you check your network connection settings an
make sure (in the properties for your local network interface card) tha
you have the TCP/IP protocol loaded and properly configured
You should also make sure that toolbar didn't drop a HOSTS file on you
machine that is causing issues. On Win2K, if I remember correctly, tha
would be in C:\Windows\system32\drivers\etc. It would be called HOST
(with no file extension). If you find one, try renaming it to somethin
else, like "HOSTS.OLD" or "OLDHOSTS"
-
-Ben
Ben M. Schorr, MVP-OneNot
OneNote FAQ: http://home.hawaii.rr.com/schorr/Computers/OneNoteFAQ.ht
SchorrTech Blog: http://www.thespoke.net/MyBlog/bschorr/MyBlog.asp

I forgot that I'm running XP Pro on that desktop. Any way there was a "hosts" file and I renamed it, but it didn't work anyway. When I do an "ipconfig" I still get a 169.255.133.37 address instead of a 192.1686.0.x address from my DHCP server

thanks, but anything else
 
I forgot that I'm running XP Pro on that desktop. Any way there
was a "hosts" file and I renamed it, but it didn't work anyway. When I
do an "ipconfig" I still get a 169.255.133.37 address instead of a
192.1686.0.x address from my DHCP server.

thanks, but anything else?
Click to expand...

What happens if you do

IPCONFIG /release

followed by

IPCONFIG /renew

Do you get the proper IP address then?
 
after the /release, it just sits there looking for a DHCP server, can't find one and times out. Doing a ping to 192.168.0.1, the DHCP server, I get a host not reachable. Pinging another host on the net I get the same thing. It's suddenly just not talking to the network.


"MVP-One wrote: ---- said:
I forgot that I'm running XP Pro on that desktop. Any way there
was a "hosts" file and I renamed it, but it didn't work anyway. When I
do an "ipconfig" I still get a 169.255.133.37 address instead of a
192.1686.0.x address from my DHCP server
Click to expand...

What happens if you d

IPCONFIG /releas

followed b

IPCONFIG /rene

Do you get the proper IP address then

-
-Ben
Ben M. Schorr, MVP-OneNot
OneNote FAQ: http://home.hawaii.rr.com/schorr/Computers/OneNoteFAQ.ht
SchorrTech Blog: http://www.thespoke.net/MyBlog/bschorr/MyBlog.asp
 
after the /release, it just sits there looking for a DHCP server, can't
find one and times out. Doing a ping to 192.168.0.1, the DHCP server,
I get a host not reachable. Pinging another host on the net I get the same thing.
It's suddenly just not talking to the network.
Click to expand...

O.K., so we have to get even more basic. Double check your cables and
your connectors. Is your hub/switch lighting up the proper port to show
that it recognizes that your machine is connected to it? Does your network
card on the machine have indicator lights that show it recognizes the cable
plugged in? Try unplugging and replugging the cable on both ends to make
sure the connection is secure.
Then try the IPCONFIG /renew again and see if you can ping your DHCP server.

You might also try to reload the drivers for your NIC if you haven't already.
Next thing to try would be to completely uninstall your network card (physically
too, if it's not integrated onto the motherboard) and then reinstall it.

If after all that it still doesn't see the network I would try to swap
in a different network card (NIC) and see if that card works -- it's possible
that your NIC has actually failed. If it's integrated onto the motherboard
that will be difficult to replace - is the machine still under warranty?
 
I think may be the system has virus. You will scan virus that use Virus
tools.

Hugh said:
Recently I was infected by the "Where you Search" (or some such) tool bar.
Click to expand...
It was an application that showed up in Task Manager, I could kill it, but
it would come back. About that same time I suddenly could not connect on my
home LAN, my desktop wouldn't talk to the network (no address, no nothing).
To get the bar off I finally edited the registery to delect any reference to
it and it was gone, but I still couldn't talk to the network. Any
association? Any suggestions?
 
Also thought it might be virus related. Did a full system scan with NAV Corp and current defs. Came up clean
I'm convinced its related to the "search-cancer" effecting something more core to tcp/ip.
 
I'm struggling with the same problem right now. It seemed to result from attempts to remove the searchexe.com adware.
I too have tried all the above fixes with no result. I was successful in restoring to a previous point, prior to attempts to remove it with an "adware remover" app. and have the network connection restored
-removal and reinstall of the nic, protocal, etc. never worked
Unfortunately, I then tried again to remove the adware, and turned of system restore (as done with virus removal). In this attempt, xp home deleted all of the restore points. Now I'm stuck
Have lost LAN connectivilty. Won't find the dhcp server. I'm thinking something with dhcp or the tcp/ip stack.
Any ideas what to try now?
 
See the two links below. First try repairing winsock and if that does not help try
reinstalling tcp/ip. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;817571
http://support.microsoft.com/?id=285034

Hugh said:
Recently I was infected by the "Where you Search" (or some such) tool bar. It was
Click to expand...
an application that showed up in Task Manager, I could kill it, but it would come
back. About that same time I suddenly could not connect on my home LAN, my desktop
wouldn't talk to the network (no address, no nothing). To get the bar off I finally
edited the registery to delect any reference to it and it was gone, but I still
couldn't talk to the network. Any association? Any suggestions?
 
I have also got into this situation, I removed a lot of 'tracking' stuff with AdAware and now my DHCP seems to fail, I can also not set the Network->Properties->Authentication setings. When leaving the configuration tool it fails and tells Failed to save all parameters. During startup I have a HUGE timeout before the system responds and Symantec A.V. reports no TCP/IP network. Clues anyone?
 
Here are a couple of things to try.

Uninstall network adapter in device manger and reboot the computer. You may need to
have drivers available after the reboot if your computer does not already know them
as it does for many of the popular nics.

Try the following links in the order listed.
http://support.microsoft.com/default.aspx?scid=kb;en-us;817571 OR try
http://www.cexx.org/lspfix.htm --Lspfix.
http://support.microsoft.com/?id=285034

If none of that helps, try booting into safe mode with networking. If that works you
have a startup program/process interfering and you will have to use selective startup
to troubleshoot using msconfig from a copy of XP or downloaded from the internet.
Autoruns from SysInternals can also do much of the same.
http://www.sysinternals.com/ntw2k/freeware/autoruns.shtml

If none of that helps. Consider a in place upgrade installation keeping in mind it
will require you to reinstall service pack and all critical updates. -- Steve
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175

Ernie said:
I have also got into this situation, I removed a lot of 'tracking' stuff with
Click to expand...
AdAware and now my DHCP seems to fail, I can also not set the
Network->Properties->Authentication setings. When leaving the configuration tool it
fails and tells Failed to save all parameters. During startup I have a HUGE timeout
before the system responds and Symantec A.V. reports no TCP/IP network. Clues anyone?restoring to a previous point, prior to attempts to remove it with an "adware
remover" app. and have the network connection restored.restore (as done with virus removal). In this attempt, xp home deleted all of the
restore points. Now I'm stuck!
 
Back
Top