[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 588
  • Last Modified:

RPC Server Not Available - Freezing FSMO DC.

I cant seem to find whats causing our main DC (FSMO) to freeze. The RPC server not available message comes up when users try to authenticate. Its causing the CPU to pin at 100% rendering the DC useless.
0
tmccabe
Asked:
tmccabe
  • 7
  • 3
2 Solutions
 
Lukasz ChmielewskiCommented:
take a look at the services and see if the rpc server runs with dependent services
0
 
ryansotoCommented:
I would look to something else causing it.  I would first try the usual thing such as antivirus - try disabling AV services then retest and see if the issue still occurs
0
 
tmccabeAuthor Commented:
no AV software at all on this DC
0
Get free NFR key for Veeam Availability Suite 9.5

Veeam is happy to provide a free NFR license (1 year, 2 sockets) to all certified IT Pros. The license allows for the non-production use of Veeam Availability Suite v9.5 in your home lab, without any feature limitations. It works for both VMware and Hyper-V environments

 
tmccabeAuthor Commented:
ryansoto - about a million dependancies-have you ever looked at how many there are ?
0
 
Lukasz ChmielewskiCommented:
not a million but few basic direct linked, see in administrative tools in control panel what shares do you have (administrative)
0
 
tmccabeAuthor Commented:
48 on the Server 2003 standard, 59 on my other DC which is Server 2008 standard.
0
 
Lukasz ChmielewskiCommented:
are we into counting or into solving this ? is the rpc server running ?
0
 
tmccabeAuthor Commented:
relax ! ;-)
yes it is running = started/automatc. There is nothing inthe event logs that is tipping me off either. Just strated the other day so I was racking my brain as to whats different or what was changed and we hardly ever touch this DC other that to have a look around every few days. Reboots once a month
0
 
tmccabeAuthor Commented:
Just froze again and I ran aDCdiag and captured the out to a file attached.
DC4.txt
0
 
tmccabeAuthor Commented:
Turns  out that one of my branch office support users was trying to add a refurbed desktop to the domain and the drive obviously had some sort of poison trojan or worm on it and it would not add to the domain but would pin the processor on that particular DC. Once we remove that beast from the netrwork and turned it off the DC is back being a domain controller. I have never seen a desktop do that before !! Thanks to all.
0
 
tmccabeAuthor Commented:
always get good idea for the knowledge base regardless if you gusy nail it on the head or not. Its all good.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

  • 7
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now