Windows 2000 Pro "wierd" Network Error

  • Thread starter Thread starter Glenn
  • Start date Start date
G

Glenn

Hello,

One Windows 2000 Pro client is exhibiting strange behavior, specifically
pertaining to the GUI networking component. (The network server is running
2000 server SP4 but I don't think it's relevant in this issue).

The above machine is running W2K SP2. It can seemingly access other network
devices (other machines, printers, internet) fine. *Other* machines can
access this machine.. But what the telltale sign something is wrong is
errors I get trying to use the graphical tools in Windows 2000. So, if I
try to open up the network connectiod using Start | Settings | Network and
Dialup connections it just hangs for a few minutes before coming up with an
empty window. If I try to add a network place via the wizard or explorer
mapping it does a similar thing- nothing. However any drives I already have
mapped are restored upon boot up and show up in explorer. Additionally I
can't add a new mapping using the graphical interface, but I *can* if I open
up a command prompt and use the "net use" commands.

So I feel some networking dlls are corrupt and or missing as they relate to
the Windows graphical interface. I figured that applying a newer service
pack should fix the problem- except that the service pack (SP3 & SP4)
install fails as "netshell.dll" is in use- and there is no way around it.
Additionally, if I go to windows explorer and look at the properties for
that file, as well as "netplwiz.dll" and "netlogon.dll", after a long delay
only the 'general' tab displays, not 'version' tab or any others. Finally,
I tried booting into Safe Mode without Networking and the exact same
behavior occurs.

So I am dead in the water. My next step would be attempt to reinstall
Windows 2000 and hope that cures it, but figured I'd see if anyone has any
insight before I go that route.

TIA,
Glenn
 
Definitely install SP4 on that machine. The things you see might be caused
by blaster. Have a look for mspatch.exe, msblast.exe or teekids.exe in the
\winnt\system32. If you find them, you're blasted.
 
Marina Roos said:
Definitely install SP4 on that machine. The things you see might be caused
by blaster. Have a look for mspatch.exe, msblast.exe or teekids.exe in the
\winnt\system32. If you find them, you're blasted.
Click to expand...

Thanks for the input Marina,

Fortunately none of those files exist and I regularly keep my virus
definations up to date an scan regularly. For good measure I did search the
entire hard drive for those files as well as look at the registry "run"
command to see if anything suspicious was happening at start up, alas it is
not. I feel confident in giving the machine a 'clean bill of health' as far
as viruses are concerned.

Unfortunately I *can't* install Service Pack 4. It fails during the install
(it does go through setup, extract, and prompt to archive) as it says
"netshell.dll" is in use. I have tried to install via CD and from the
windowsupdate.com. I can't uninstall service pack 2, as the machine was
purchased from Dell with SP2 preinstalled as part of the OS. There is no
uninstall option. Also as mentioned in original post, I booted the machine
using "safe mode without networking support" but the same problems occur!

When I performed a backup via the client "backup" utility, it backed up with
the exception of four files reported 'in use'.
C:\winnt\system32\netlogon.dll
C:\winnt\system32\netman.dll
C:\winnt\system32\netlplwiz.dll
C:\winnt\system32\netlshell.dll

Any other insight?

Thanks,
Glenn
 
That is really strange that you're not able to install SP4. Make sure all
3rd party services are stopped and try again. Also make sure that the
machine is not connected to the internet before you have SP4 and ms03-039
installed.
 
Wow- that was weird! I did manage to solve my problem.

After trying numerous workarounds, in the end I did a "chkdsk" on the drive.
It reported an error that is semi-cryptic but also had a key file name that
related to my problems. During the operation, in stage 2 "deleting index
entry netplwiz.dll in index $i30 of file 5752", then in stage 5 it reported
a bad sector. After the cleanup of these items everything worked. Of
course that was my goal, and then I was also able to install SP4 no probs.

-Glenn
 
I would follow the steps in the following KB article as a next step:

254631 Some Network and Dial-Up Connections Icons May Be Missing
http://support.microsoft.com/?id=254631

If that doesn't help, you might also want to try:

SFC /SCANNOW - from the command line
222471 Description of the Windows 2000 System File Checker (Sfc.exe)
http://support.microsoft.com/?id=222471



--------------------
Hello,

One Windows 2000 Pro client is exhibiting strange behavior, specifically
pertaining to the GUI networking component. (The network server is running
2000 server SP4 but I don't think it's relevant in this issue).

The above machine is running W2K SP2. It can seemingly access other network
devices (other machines, printers, internet) fine. *Other* machines can
access this machine.. But what the telltale sign something is wrong is
errors I get trying to use the graphical tools in Windows 2000. So, if I
try to open up the network connectiod using Start | Settings | Network and
Dialup connections it just hangs for a few minutes before coming up with an
empty window. If I try to add a network place via the wizard or explorer
mapping it does a similar thing- nothing. However any drives I already have
mapped are restored upon boot up and show up in explorer. Additionally I
can't add a new mapping using the graphical interface, but I *can* if I open
up a command prompt and use the "net use" commands.

So I feel some networking dlls are corrupt and or missing as they relate to
the Windows graphical interface. I figured that applying a newer service
pack should fix the problem- except that the service pack (SP3 & SP4)
install fails as "netshell.dll" is in use- and there is no way around it.
Additionally, if I go to windows explorer and look at the properties for
that file, as well as "netplwiz.dll" and "netlogon.dll", after a long delay
only the 'general' tab displays, not 'version' tab or any others. Finally,
I tried booting into Safe Mode without Networking and the exact same
behavior occurs.

So I am dead in the water. My next step would be attempt to reinstall
Windows 2000 and hope that cures it, but figured I'd see if anyone has any
insight before I go that route.

TIA,
Glenn
Click to expand...

__
Danny Slye
Microsoft Support Professional
MCSE

This posting is provided "AS IS" with no warranties and confers no rights.
Please reply to the newsgroup so that others may benefit. Thanks!
 
Back
Top