P
Peter Tan
Hi...
My Windows 2000 Professional already has SP4 applied. Last
night I went to the update site again and updated 3
more "Critical Updates" from MS.
After the customary reboot, I found that the connection
process of my Dial Up Networking is extremely slow! The
screen shows "Registering your computer on the network..."
and it appears to hang.. Task Manager says "services.exe"
is running at 99% to 100%, and it takes about 2 minutes to
get to the "Connected" message.
I'm on broadband and prior to the updates, my DUN usually
does "almost instantaneous" connects, ie as soon as I
click on the "Connect" button, it takes about 1 to 2
seconds to get connected.
Disconnecting from the Internet took longer too - from the
1 to 2 seconds to disconnect, it now takes about 30
seconds.
I tried to uninstall the latest changes, but I could only
find 2 out of the 3 I installed in the "Add/Remove" box. I
removed the 2, but there has been no change in the DUN
behaviour...
Anybody has any ideas how this can be fixed? Anybody else
has this problem?
My Windows 2000 Professional already has SP4 applied. Last
night I went to the update site again and updated 3
more "Critical Updates" from MS.
After the customary reboot, I found that the connection
process of my Dial Up Networking is extremely slow! The
screen shows "Registering your computer on the network..."
and it appears to hang.. Task Manager says "services.exe"
is running at 99% to 100%, and it takes about 2 minutes to
get to the "Connected" message.
I'm on broadband and prior to the updates, my DUN usually
does "almost instantaneous" connects, ie as soon as I
click on the "Connect" button, it takes about 1 to 2
seconds to get connected.
Disconnecting from the Internet took longer too - from the
1 to 2 seconds to disconnect, it now takes about 30
seconds.
I tried to uninstall the latest changes, but I could only
find 2 out of the 3 I installed in the "Add/Remove" box. I
removed the 2, but there has been no change in the DUN
behaviour...
Anybody has any ideas how this can be fixed? Anybody else
has this problem?