Changes cause Active Directory to lockup

[Guest]

I've had 2 domain controllers in my organization running flawlessly for the past year, however, recently I've noticed when I make any changes in Active Directory on the first domain controller, Active Directory freezes and users cannot access any files on the server. The other domain controller continues functioning fine, but the one that froze has to be restarted so users can access files on it. It doesn't matter whether its simply to reset a password or create a new user account, any changes on the first controller causes it to freeze. If I make changes on the second controller, they work fine. Anyone have some ideas??

 

[Scott Harding - MS MVP]

Do you have any errors in the event log? If you make these change on the 2nd
DC does the same thing occur? What errors do people get when the freezing
occurs>?

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

I've had 2 domain controllers in my organization running flawlessly for

the past year, however, recently I've noticed when I make any changes in
Active Directory on the first domain controller, Active Directory freezes
and users cannot access any files on the server. The other domain
controller continues functioning fine, but the one that froze has to be
restarted so users can access files on it. It doesn't matter whether its
simply to reset a password or create a new user account, any changes on the
first controller causes it to freeze. If I make changes on the second
controller, they work fine. Anyone have some ideas??

 

[Guest]

Nothing shows in the event log; I wish it did. When the server locks ups and a user goes to open a file, like a Word document, Word lauches but the file never opens. After about 30 seconds, an error message is returned saying to check the path because the file could not be located. Users can browse the files in their directory all they want, but when they go to open a file, it locks up because of the server. Once the server is restarted, the Active Directory changes are applied and everything is back to normal

If I make changes on my second domain controller, the changes go through fine and replicate to the first one with no lock ups.

----- Scott Harding - MS MVP wrote: ----

Do you have any errors in the event log? If you make these change on the 2n
DC does the same thing occur? What errors do people get when the freezin
occurs>

--
Scott Hardin
MCSE, MCSA, A+, Network
Microsoft MVP - Windows NT Serve

I've had 2 domain controllers in my organization running flawlessly fo

the past year, however, recently I've noticed when I make any changes i
Active Directory on the first domain controller, Active Directory freeze
and users cannot access any files on the server. The other domai
controller continues functioning fine, but the one that froze has to b
restarted so users can access files on it. It doesn't matter whether it
simply to reset a password or create a new user account, any changes on th
first controller causes it to freeze. If I make changes on the secon
controller, they work fine. Anyone have some ideas?

 

[Cary Shultz [A.D. MVP]]

Tom,

I might suggest that you install the Support Tools on each of your Domain
Controllers and run both a netdiag /v and dcdiag /v. The Support Tools are
located in three locations: on the WIN2000 Server CD in the Support | Tools
folder; on the WIN2000 Service Pack CD in the Support | Tools folder; and on
the MS web site.

I might ask what you have added / removed on the first DC? Meaning, what
has changed immediately before this problem started?

Scott, hope that you do not mind that I jumped in....;-)

HTH,

Cary

Nothing shows in the event log; I wish it did. When the server locks ups

and a user goes to open a file, like a Word document, Word lauches but the
file never opens. After about 30 seconds, an error message is returned
saying to check the path because the file could not be located. Users can
browse the files in their directory all they want, but when they go to open
a file, it locks up because of the server. Once the server is restarted,
the Active Directory changes are applied and everything is back to normal.

If I make changes on my second domain controller, the changes go through

fine and replicate to the first one with no lock ups.

 

[Guest]

Hi Cary

The wierd part is that nothing has changed since I use my first DC solely as a file server. No programs have been added or removed. The first time it happened a few months ago, I searched the web and found that it may be because my hard drive was fragmented. I ran defrag, scan disk, and even the disk cleanup utility, but the problem still persists. I also ran the netdiag and dcdiag programs, and no problems were detected and the dc passed all of the tests.

One little fact I can add though. After the dc locks up and I restart it, everything works fine. I can even go into Active Directory and make changes and they won't lock up the server. The next day, however, if I go into Active Directory to make a change, the server locks up again and has to be restarted. Any ideas?

Thanks for your help

To


----- Cary Shultz [A.D. MVP] wrote: ----

Tom

I might suggest that you install the Support Tools on each of your Domai
Controllers and run both a netdiag /v and dcdiag /v. The Support Tools ar
located in three locations: on the WIN2000 Server CD in the Support | Tool
folder; on the WIN2000 Service Pack CD in the Support | Tools folder; and o
the MS web site

I might ask what you have added / removed on the first DC? Meaning, wha
has changed immediately before this problem started

Scott, hope that you do not mind that I jumped in....;-

HTH

Car

Nothing shows in the event log; I wish it did. When the server locks up

and a user goes to open a file, like a Word document, Word lauches but th
file never opens. After about 30 seconds, an error message is returne
saying to check the path because the file could not be located. Users ca
browse the files in their directory all they want, but when they go to ope
a file, it locks up because of the server. Once the server is restarted
the Active Directory changes are applied and everything is back to normal