HELP!!

  • Thread starter Thread starter Matthew
  • Start date Start date
M

Matthew

I ran this application and it may have removed a piece of
spyware that attached itself to something that allows me
to connect to the internet. My IP address should be a 192.
number but it is a 164.number when connected to the
router. When I plug straight into the modem however it is
fine. Is there any way (other than system restore) that I
can get connected again.
Matt
 
Yes, and depending on your OS version it is either really simple or no too
complex:

http://support.microsoft.com/kb/892350

The above Microsoft KB article has what you need-- if you are not on XP SP2,
you'll need a portion of a second article it links to--so you may want to go
through it carefully and print bits or all of both articles before you get
back to the errant machine.

Microsoft is aware that this circumstance distresses the users (to put it
mildly)--and I would expect the way this works to change some before final
release.
 
I'm having a similiar problem, I think. I can't connect
to my router. Shouhd have a 192.168.1.xx to connect to my
Linksys router, but I keep getting assigned 0.1.225.100
and I can't ping my router or connect to its web based
settings page. Tried the netsock repair and nothing
changed. Tried ip release/renew and still get same
address. Could also be a bad router.
 
Something is assigning you that address. If you and the Linksys router are
the only devices on the network (wired? wireless?) then I would recommend
doing a full reset on the Linksys to take it back to factory defaults, as
long as you recall the settings you will need to put back to restore it to
your usual configuration.
 
I get assigned that address even when the computer is
disconnected from the router, and I do an
ipconfig /release and /renew.
 
You need to reset the router, meaning pull power, wait a
few seconds and then plug in the power. The router will
reset and should function as before.
 
Problem has been resolved. The problem was caused by a
malfunction of the router, which I fixed by reseting the
router. It was not due to a MS Antisypware issue.
 
Back
Top