Problems when you open MY COMPUTER from a client machine in a NT domain

[Dan]

Hello...

We have a network running on a NT4 domain with client machines ranging from
98 to XP inc 2000. This morning all of a sudden all client machines (about
70) would freeze if you tried to open up MY COMPUTER. Right click on MY
computer and explore and you just get an egg timer for anything upto 10
mins. Clients can view the internet, clients can even browse the network
itself opening files on different machines and servers. However when any
client machine tries to propergate a list of mapped drives from within MY
COMPUTER it takes ages and as a result of this many people seem to be
experiencing blue screens and crashing apps. I have searched the MSknowledge
base but how do you explain this? Don't think it's a hardware issue because
if you can browse the entire network why can't you browse your own PC and
mapped drives?

Any help would be greatly appreciated as I'm kinda at a loss as to what to
do next.

 

[Kevin D. Goodknecht [MVP]]

In Dan <[email protected]> posted a question
Then Kevin replied below:
: Hello...
:
: We have a network running on a NT4 domain with client machines
: ranging from 98 to XP inc 2000. This morning all of a sudden all
: client machines (about 70) would freeze if you tried to open up MY
: COMPUTER. Right click on MY computer and explore and you just get an
: egg timer for anything upto 10 mins. Clients can view the internet,
: clients can even browse the network itself opening files on different
: machines and servers. However when any client machine tries to
: propergate a list of mapped drives from within MY COMPUTER it takes
: ages and as a result of this many people seem to be experiencing blue
: screens and crashing apps. I have searched the MSknowledge base but
: how do you explain this? Don't think it's a hardware issue because if
: you can browse the entire network why can't you browse your own PC
: and mapped drives?
:
: Any help would be greatly appreciated as I'm kinda at a loss as to
: what to do next.

Since this is an NT4 domain it is unlikely to be DNS, make follow-ups to
microsoft.public.windowsnt.domain NG

It has been almost three years since I upgraded from NT4 but it sounds to me
like the machines are unable to contact a DC. Have you attempted to restart
your PDC?
Is there a BDC in the works and is it able to contact the PDC?