T
TastyWheat
I wrestled with this problem for two days straight and I feel it's
worth passing the information on to others. I have a SpeedStream DSL
modem, a WRT54G router, and a Windows XP machine. My modem worked
fine, my router worked fine, but my XP machine couldn't ping any
outside address or renew its IP. I finally realized that it would
startup with the correct IP, but once Windows was fully loaded my
connectivity stopped. It was obviously the work of some malicious or
malfunctioning program (the latter in my case).
Don't just check the taskbar and tray, use task manager to look at all
of the processes. If it's not crucial and it uses the internet then
close it. This includes your firewall; don't just disable it.
Anything that can't be forcibly closed is probably not working
correctly and should be investigated further. If you can't kill the
process try disabling it in the startup sequence using "msconfig". Or
you can try and rename the executable, if you're allowed to. If all of
that fails (to keep the program from running) you should probably just
uninstall it.
In my case Sygate Personal Firewall (smc.exe) was running and I
couldn't close it or keep it from loading. I had to unistall it, and
once I did my internet worked like a charm. Beyond that I don't have a
lot to say. You'll find tons of other suggestions roaming around the
newsgroups.
worth passing the information on to others. I have a SpeedStream DSL
modem, a WRT54G router, and a Windows XP machine. My modem worked
fine, my router worked fine, but my XP machine couldn't ping any
outside address or renew its IP. I finally realized that it would
startup with the correct IP, but once Windows was fully loaded my
connectivity stopped. It was obviously the work of some malicious or
malfunctioning program (the latter in my case).
Don't just check the taskbar and tray, use task manager to look at all
of the processes. If it's not crucial and it uses the internet then
close it. This includes your firewall; don't just disable it.
Anything that can't be forcibly closed is probably not working
correctly and should be investigated further. If you can't kill the
process try disabling it in the startup sequence using "msconfig". Or
you can try and rename the executable, if you're allowed to. If all of
that fails (to keep the program from running) you should probably just
uninstall it.
In my case Sygate Personal Firewall (smc.exe) was running and I
couldn't close it or keep it from loading. I had to unistall it, and
once I did my internet worked like a charm. Beyond that I don't have a
lot to say. You'll find tons of other suggestions roaming around the
newsgroups.