Re: SYSVOL replication stops after DCPROMO

Hi,

Check disk space and dcpromo.log !


Regards.






"Stefan Vogel" <birdie@xxxxxxxxxx> a écrit dans le message de news:
e9bfb2$r18$02$1@xxxxxxxxxxxxxxxxxxxx
There are no errors in eventlog. only an entry, that it is filling SYSVOl
with data from a different DC... but it is not doing so.

Regards

--
______________
(_______
__________) t e f a n

http://www.birdies.de - Die Smart cdr Homepage
http://www.iiih.de - Die Welt der Käfer
http://www.eggpeeling.com

"Thor Vanden Reysen" <toto@xxxxxxx> schrieb im Newsbeitrag
news:uu7DzNDqGHA.5064@xxxxxxxxxxxxxxxxxxxxxxx
OK.

There are errors because AH2C004 is not considered as a DC.

What are errors in event viewer ?

Regards.


"Stefan Vogel" <birdie@xxxxxxxxxx> a écrit dans le message de news:
e9b6kb$nhr$00$1@xxxxxxxxxxxxxxxxxxxx
Hello,

I just copy SP1 to that machine, will install it over the existing
installation when finished.

As the not finished SYSVOL replication is preventing the machine from
becoming a DC, I don't wonder, that KDC is not running. Should it run
anyway?

DNS is running ok. May be that the problem with this FN-server is, that
it is in Germany, and AH is in USA. Sometimes there are problems with
the line.

What should I check on the FSMOs? We have running NetPro
DirectoryAnalyzer and it says that the knowledge of FSMO-role-holder is
consitent.

Regards

--
______________
(_______
__________) t e f a n

http://www.birdies.de - Die Smart cdr Homepage
http://www.iiih.de - Die Welt der Käfer
http://www.eggpeeling.com

"Thor Vanden Reysen" <toto@xxxxxxx> schrieb im Newsbeitrag
news:OWiCbUBqGHA.4988@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

SP1 is integrated in the installation source. so an uninstallation is
no option.

I didn't say uninstall ! LOL ;)

Warning: DsGetDcName returned information for
\\FN2C001.auto.contiwan.com, when we were trying to reach AH2C004.
Server is not responding or is not considered suitable.

Check your DNS resolution !

Role PDC Owner = CN=NTDS
Settings,CN=FR2C001,CN=Servers,CN=FR,CN=Sites,CN=Configuration,DC=contiwan,DC=com


Starting test: frssysvol
* The File Replication Service SYSVOL ready test
The registry lookup failed to determine the state of the
SYSVOL. The

error returned was 0 (The operation completed successfully.).
Check

the FRS event log to see if the SYSVOL has successfully been
shared.
......................... AH2C004 passed test frssysvol

=>ahAc004 passed test frssysvol !

Starting test: FsmoCheck
GC Name: \\ah2c003.autona.contiwan.com
Locator Flags: 0xe00001fc
PDC Name: \\FR2C001.auto.contiwan.com
Locator Flags: 0xe0000179
Time Server Name: \\RH2C001.auto.contiwan.com
Locator Flags: 0xe000017c
Preferred Time Server Name: \\AI2C001.auto.contiwan.com
Locator Flags: 0xe000017c
KDC Name: \\hd2c001.auto.contiwan.com
Locator Flags: 0xe000017c
......................... contiwan.com passed test FsmoCheck

Preferred time server ?
KDC not running on ah2C004 ???
Check fsmo check !

Regards.




=================================================











.

Relevant Pages

  • Re: SYSVOL replication stops after DCPROMO
    ... unable to get the time from our central server. ... As the not finished SYSVOL replication is preventing the machine from ... Locator Flags: 0xe00001fc ... Preferred Time Server Name: \\AI2C001.auto.contiwan.com ...
    (microsoft.public.windows.server.active_directory)
  • Re: SYSVOL replication stops after DCPROMO
    ... As the not finished SYSVOL replication is preventing the machine from ... SP1 is integrated in the installation source. ... Locator Flags: 0xe00001fc ... Preferred Time Server Name: \\AI2C001.auto.contiwan.com ...
    (microsoft.public.windows.server.active_directory)
  • Re: SYSVOL replication stops after DCPROMO
    ... As the not finished SYSVOL replication is preventing the machine from ... SP1 is integrated in the installation source. ... Locator Flags: 0xe00001fc ... Preferred Time Server Name: \\AI2C001.auto.contiwan.com ...
    (microsoft.public.windows.server.active_directory)
  • Re: SYSVOL replication stops after DCPROMO
    ... so an uninstallation is no ... The registry lookup failed to determine the state of the SYSVOL. ... Locator Flags: 0xe00001fc ... Preferred Time Server Name: \\AI2C001.auto.contiwan.com ...
    (microsoft.public.windows.server.active_directory)
  • Re: dcdiag failed - PDC is down
    ... Make sure the Windows Time Service is running on this DC. ... Locator Flags: 0xe00003fc ... The server holding the PDC role is down. ... Preferred Time Server Name: \\dbsvr.mydomain.net ...
    (microsoft.public.win2000.active_directory)
Loading