T
Tobias
Hi,
I recently tried to connect a Win2k pro SP4 machine to a
cable modem and apparently messed up something. The
network card had at some point been used for some other
purpose, and since the new connection didn't work I tried
to unbind TCP/IP from all adapters, uninstall it and
reinstall afterwards. I also uninstalled RasPPPoE which,
at some point, had been bound to that adapter as well.
Now, the computer hangs on "preparing network
connections" for about 3 minutes when starting up. Then,
when logging in, it slows down dreadfully, and the Task
Manager shows 100% CPU usage, mostly consumed by
services.exe. Takes about 15 minutes before it
normalizes, but every time anything TCP/IP related kicks
in, it starts hanging again (which, of course, means
networking is inoperable). The only form I figured out to
avoid it is to uninstall or disable the TCP/IP driver
(tcpip.sys), but I need my connectivity back.
Further symptoms: There are event notifications that one
or another network related service has timed out, most
consistently I get "The DNSClient hung on starting"
(Event ID 7022) and "Timeout waiting for a transaction
response from the DNSCache service" (7011) in the process
of system startup.
I have tried to completely unbind/uninstall TCP/IP,
uninstall it in Device Manager, and remove its traces
from the registry as described in two KB articles for NT4
and 2000 server, but after reinstallation the problem
starts again. In fact, it already turns up in the
installation process, at the point where the Connection
Wizard wants to fetch and install required services.
Well, well, don't know, but it seems to me something in
the context of TCP/IP gets caught in a loop, perhaps some
device or service attached to it. For instance, the RAS
Async Adapter shows up in the Device Manager as not
working properly, but I cannot repair (by reinstalling
the driver) nor deinstall it (it seems it is needed for
startup). May that be the problem? And if, how to fix? Or
what else comes with TCP/IP and may have got lost or
corrupted?
Sorry for the length, I'm pretty desperate. Any help
appreciated. Thanks,
Tobias
I recently tried to connect a Win2k pro SP4 machine to a
cable modem and apparently messed up something. The
network card had at some point been used for some other
purpose, and since the new connection didn't work I tried
to unbind TCP/IP from all adapters, uninstall it and
reinstall afterwards. I also uninstalled RasPPPoE which,
at some point, had been bound to that adapter as well.
Now, the computer hangs on "preparing network
connections" for about 3 minutes when starting up. Then,
when logging in, it slows down dreadfully, and the Task
Manager shows 100% CPU usage, mostly consumed by
services.exe. Takes about 15 minutes before it
normalizes, but every time anything TCP/IP related kicks
in, it starts hanging again (which, of course, means
networking is inoperable). The only form I figured out to
avoid it is to uninstall or disable the TCP/IP driver
(tcpip.sys), but I need my connectivity back.
Further symptoms: There are event notifications that one
or another network related service has timed out, most
consistently I get "The DNSClient hung on starting"
(Event ID 7022) and "Timeout waiting for a transaction
response from the DNSCache service" (7011) in the process
of system startup.
I have tried to completely unbind/uninstall TCP/IP,
uninstall it in Device Manager, and remove its traces
from the registry as described in two KB articles for NT4
and 2000 server, but after reinstallation the problem
starts again. In fact, it already turns up in the
installation process, at the point where the Connection
Wizard wants to fetch and install required services.
Well, well, don't know, but it seems to me something in
the context of TCP/IP gets caught in a loop, perhaps some
device or service attached to it. For instance, the RAS
Async Adapter shows up in the Device Manager as not
working properly, but I cannot repair (by reinstalling
the driver) nor deinstall it (it seems it is needed for
startup). May that be the problem? And if, how to fix? Or
what else comes with TCP/IP and may have got lost or
corrupted?
Sorry for the length, I'm pretty desperate. Any help
appreciated. Thanks,
Tobias