Re: DC Temporarily Off-line, Remaining DC Struggling
- From: "Richard Tubb" <richard@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 5 Jul 2005 10:52:04 +0100
Hi Rebecca,
Thanks for your quick and detailed response.
To confirm - when the original win2k DC is taken off-line leaving just the
newly promoted win2k3 DC on-line, client logon to the domain and any
subsequent actions (clicking on the start menu, shutting down, etc.) are
very slow. Once the win2k server DC is brought back on-line, these issues
don't occur.
Using "Active Directory Users and Computers" we have transferred the
Operations Masters roles, RID, PDC and Infrastructure, to the new Windows
2003 DC. We have done this whilst both servers are on-line.
Using "Active Directory Sites and Services" we have made the new Windows
2003 DC the Global Catalog server. Event logs show that the win2k DC
relinquishes it's role as GC succesfully (EventID 1120) and the win2k3 takes
over as GC succesfully (EventID 1119).
However we've noticed that after transferring the GC role to the Win2k3 DC,
the win2k DC shows Event ID 1534 in it's "Directory Service" Event log,
"This machine holds the Domain Master Role, and is not a GC. These two
states are incompatible. Either this machine should be made a GC or the role
should be transferred to a machine that is a GC".
I'm not aware of how we might transfer the "Domain Master Role" - can you
advise?
Regards,
Richard Tubb.
www.netlinktrading.co.uk
""Rebecca Chen [MSFT]"" <v-rebc@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:Ti7T7PUgFHA.3240@xxxxxxxxxxxxxxxxxxxxxxxx
> Hi Richard,
>
> I would like to confirm that if the original win2k server is taken
> offline,
> the client logon to the domain very slowly; all issues are resolved once
> you bring the win2k server back.
>
>
> I have the similar experience, my scenario is the same and the root cause
> turns out the new win2k3 server is not a GC. Technically speaking, you
> need
> to transfer 5 FSMO roles to the new win2k3 server as well as the GC.
> However, it takes some time to replicate between two servers. You will
> notice Event ID 1119 appears in the new win2k3 server to announce this
> server is the GC in the network. An easy way to identify the GC is to run
> the following command:
> nltest /server:servername /dsgetdc:domainname
>
> servername: Specifies the name of the domain controller you have
> designated
> as a global catalog server.
>
> domainname: Specifies the name of the domain to which the server belongs.
>
> For more details about the command, please refer to the following article:
>
> Verify global catalog readiness
> http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/Opera
> tions/dc3e9f5e-097d-4736-ae8d-30103a055d97.mspx
>
> Please check if the current server is GC. Another way to determine a GC is
> to add a new user account on win2k3 server, when you new a user account,
> do
> you receive the message indicates "cannot verify GC, DC will create the
> account and will verify the unique until contact GC"? If you do, the
> current DC is not a GC.
>
> In addition to the client logon to win2k3 server very slowly, do you
> observe other symptoms?
>
> If the issue persists, please refer to the following article to gather the
> MPSreport on the win2k3 server and send the MPSreport to
> v-rebc@xxxxxxxxxxxxx for research. Please download the MPSRPT_DirSvc.EXE
> one and run it on the win2k3 server:
>
> Microsoft Product Support's Reporting Tools
> http://www.microsoft.com/downloads/details.aspx?familyid=cebf3c7c-7ca5-408f-
> 88b7-f9c79b7306c0&displaylang=en
>
> The following article has described the MPSreport:
> Overview of the Microsoft Configuration Capture Utility (MPS_REPORTS)
> http://support.microsoft.com/default.aspx?scid=kb;en-us;818742
>
> I look forward to your reply.
>
> Best regards,
>
> Rebecca Chen
>
> MCSE2000 MCDBA CCNA
>
>
> Microsoft Online Partner Support
> Get Secure! - www.microsoft.com/security
>
> =====================================================
>
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
>
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> --------------------
>>From: "Richard Tubb" <richard@xxxxxxxxxxxxxxxxxxxx>
>>Subject: DC Temporarily Off-line, Remaining DC Struggling
>>Date: Mon, 4 Jul 2005 22:23:25 +0100
>>Lines: 36
>>X-Priority: 3
>>X-MSMail-Priority: Normal
>>X-Newsreader: Microsoft Outlook Express 6.00.2900.2527
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
>>X-RFC2646: Format=Flowed; Original
>>Message-ID: <OXurd6NgFHA.1044@xxxxxxxxxxxxxxxxxxxx>
>>Newsgroups: microsoft.public.windows.server.active_directory
>>NNTP-Posting-Host: brokerassistance.co.uk 62.173.74.14
>>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!tk2msftngp13.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.windows.server.active_directory:31354
>>X-Tomcat-NG: microsoft.public.windows.server.active_directory
>>
>>Hi,
>>
>>We've got an AD domain with 2 Domain Controllers, one (the original)
> running
>>Windows 2000 Advanced Server. The 2nd (a later addition) running Windows
>>2003 Server.
>>
>>We've recently had cause to take our Windows 2000 Server off-line for
>>maintenance, and have noticed that the Windows 2003 DC doesn't seem to
> take
>>up the strain very well. All FMSO roles (including GC) were transferred to
>>the 2003 DC before the 2000 DC was taken off-line. However when users try
> to
>>login, the response is very very sluggish. Doing much of anything on the
>>Desktop after this also seems incredibly sluggish, although no actual
> errors
>>are produced.
>>
>>Once the 2000 DC is rebooted and back on-line, logins go quickly and
>>performance is back to normal.
>>
>>I can see nothing out of the ordinary in the event log of either DC. DNS
>>appears to be setup correctly, with DHCP handing out both DC's IP address
> as
>>Primary and Secondary DNS server. Therefore I'd hope that whilst the 2000
> DC
>>is off-line, the 2003 DC will deal with any DNS requests and visa-versa.
>>
>>I should add that the long term plan is to remove the 2000 DC altogether
> as
>>it is struggling with lack of disk space, etc. However I'm not confident
>>enough in the 2003 DC to demote the 2000 DC altogether just yet. I'd be
> much
>>happier knowing that with 2 DC's in working order, when one goes off-line
>>the other picks up the slack in the short-term!
>>
>>Can anyone suggest what the issue might be, or where I might start to look
>>to troubleshoot?
>>
>>Regards,
>>
>>Richard Tubb.
>>
>>
>>
>
.
- Follow-Ups:
- Re: DC Temporarily Off-line, Remaining DC Struggling
- From: Hank Arnold
- Re: DC Temporarily Off-line, Remaining DC Struggling
- From: Paul Williams [MVP]
- Re: DC Temporarily Off-line, Remaining DC Struggling
- References:
- DC Temporarily Off-line, Remaining DC Struggling
- From: Richard Tubb
- RE: DC Temporarily Off-line, Remaining DC Struggling
- From: "Rebecca Chen [MSFT]"
- DC Temporarily Off-line, Remaining DC Struggling
- Prev by Date: Software deployment
- Next by Date: Re: Software deployment
- Previous by thread: RE: DC Temporarily Off-line, Remaining DC Struggling
- Next by thread: Re: DC Temporarily Off-line, Remaining DC Struggling
- Index(es):
Relevant Pages
|
