Also, I get these erros in NETDIAG...Oops I shuld have posted that in previous mail...
LDAP test. . . . . . . . . . . . . : Passed
[WARNING] Failed to query SPN registration on DC 'RIY04-DC01.riyadh.afg.com'.
[WARNING] Failed to query SPN registration on DC 'mega-dc1.riyadh.afg.com'.
[WARNING] Failed to query SPN registration on DC 'safisulaidc1.riyadh.afg.com'.
Regards,
Athif
-----Original Message-----
From: Mohammed Athif Khaleel
Sent: Monday, 24 May 2004 4:49 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Sysvol Damaged
Roger, Yes, the box is pointing to a correct dc which is actually the PDC running very well and healthy SYSVOL structure. I have been waiting for more than a week for replication to happen but still the same, even the sysvol folder is not shared. I am attaching dcdiag log, I really dont know if i can attach dcdiag.txt. Appologies if thatz not allowed..
TIA,
Athif
-----Original Message-----
From: Rutherford, Robert [mailto:[EMAIL PROTECTED]]
Sent: Monday, 24 May 2004 3:54 PM
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Sysvol Damaged
Can you also run a dcdiag and see if it runs clean? If it doesn't then paste the results here.
Rob
-----Original Message-----
From: Roger Seielstad [mailto:[EMAIL PROTECTED]]
Sent: 24 May 2004 13:39
To: [EMAIL PROTECTED]
Subject: RE: [ActiveDir] Sysvol Damaged
Is the box pointing to a known good DNS server (preferably to DC's in a known good site)?
How long are you waiting for replication to happen? I generally like to let them spin overnight if at all possible before worrying about whether its working correctly.
--------------------------------------------------------------
Roger D. Seielstad - MTS MCSE MS-MVP
Sr. Systems Administrator
Inovis Inc.
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 24, 2004 4:45 AM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Sysvol Damaged
Hi Folks,
I am having a problem with one of my Additonal Domain Controller, which is recently promoted. Actually,this is a newly promoted ADC via a wan link. I had to demote it first using dcpromo/forceremoval as it had problem and it was screwed.( http://support.microsoft.com/default.aspx?kbid=332199 ) Also, i had to delete netlogon.chg file in system root as it was corrupted and then after the reboot the system created the file succesfully..
I later used ADSIEDIT to clear the metabase succesfully. Now in this DC is fresly promoted as a new Additonal Domain controller againt thru the WAN Link, Now, I cant see anything id domain.com in sysvol and itz not shared too. Also, i had to delete netlogon.chg file in system root as it was corrupted and then after the reboot the system created the file succesfully..
How do rebuild the sysvol strucuture, Do I need to use "D2" "D4" Burflags.. I am afraid because I have more that 5 ADC in this site and 2-3 are connected via WAN Link. Or shuld I manually copy the sysvol structure from the GOOD SYSVOL STRUCUTE on another DC and try to restart NTFRS, like, I am really running out of ideas.
Can any one help me on this issue.
Regards,
Mohammed Athif Khaleel
Asst.Network Engineer
AlFaisaliah Group Information Technology
Tel.: +966-1-461-0077 x.209
Moble.: +966-509774015
Email: [EMAIL PROTECTED]
"Save Internet, Keep all the systems patched"
Web: http://alfaisaliah.com
-----------------------------------------------------
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom/which they are addressed. If you have received this email in error please notify the system manager at the following email address: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of Al Faisaliah Group. Internet communications cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, arrive late or contain viruses. The sender therefore does not accept liability for any errors or omissions in the context of this message, which arise as a result of Internet transmission. Finally, the recipient should check this email and any attachments for the presence of viruses. Al Faisaliah Group accepts no liability for any damage caused by any virus transmitted by this email.
-----------------------------------------------------
