"Weird" Behavior in W2k Pro

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
 
G

Glenn

Wow- that was weird! I did manage to solve my problem after many an hour
spent. I'm sure ya'all know that drill!.

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
 
E

Enkidu

So, you did a backup straight after this? If you have a bad sector you
should consider that the disk *might* be ready to fail. Of course it
might live for ages, but would you want to risk it?

Cheers,

Cliff
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top