Re: NETLOGON and SYSVOL not replicated to new 03DC ?

Hi Scott,

If you go to BServer and enter this in start run menu

\\bserver\

do you see Netlogon and SYSVOL?

What errors do you get in Event logs (check all of them on both computers).

This seems to me like DNS problem.

Can you resolve both servers from command line? E.g. on Bserver

nslookup dserver

and then go to Dserver and do

nslookup bserver

On DServer open Active Directory Users and Computers -- click on Domain
Controllers OU. Which accounts do you see here? How about on BServer?
Open Sites and Serivces. Which server do you see here if you drill down
under Default Site (if you haven't renamed it).

Note: try to keep your posts in one thread -- it will be easier for us to
help you.

--
Mike
Microsoft MVP - Windows Security

"scott" <nospam@xxxxxxxxx> wrote in message
news:OUd9L86tFHA.2540@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I added a 2003 DC (Bserver) to my 2000 AD domain (Dserver is old DC). All
> roles have been transfered and global cat, DCDIAG reports that all FMSO
> roles (according to bserver and dserver) reside with bserver (which is
> right i think).
>
> SCHEMA bserver bserver
>
> NAMING bserver bserver
>
> INFRASRRUCTURE bserver bserver
>
> RID bserver bserver
>
> PDC bserver bserver
>
> GLOBAL CATALOG bserver bserver
>
>
> NETLOGON and SYSVOL still not replicated on bserver from deserver, think
> this is the problem now.
>
> i.e
> when dserver off, i cant logon to domain
> dserver DNS points to bserver
> bserver dns points to itself
>
> Thanks for any help.
> Scott
>


.

Relevant Pages

  • Re: NETLOGON and SYSVOL not replicated to new 03DC ?
    ... After you do this -- reboot the bserver. ... Then open Sites and Services on dserver and drill down under Default Site ... Can you see SYSVOL and NETLOGON shares on both servers? ... > Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: NETLOGON and SYSVOL not replicated to new 03DC ?
    ... from bserver \\bserver i can only see SYSVOL. ... The DNS server list of restricted interfaces contains IP addresses that are ... Event Source: NtFrs ... The File Replication Service has enabled replication from DSERVER to BSERVER ...
    (microsoft.public.windows.server.general)
  • Re: NETLOGON and SYSVOL not replicated to new 03DC ?
    ... DSERVER and then BSERVER. ... BSERVER DNS looks at its own IP as does DSERVER. ... * Identifying all servers. ... Starting test: CrossRefValidation ...
    (microsoft.public.windows.server.general)
  • Re: NETLOGON and SYSVOL not replicated to new 03DC ?
    ... My advice would be to transfer the roles back to dserver ... problem) with new server you should transfer FSMO roles back with bserver. ... Then try to force replication manually using Sites and Services. ...
    (microsoft.public.windows.server.general)
  • Re: NETLOGON and SYSVOL not replicated to new 03DC ?
    ... After you do this -- reboot the bserver. ... > Then open Sites and Services on dserver and drill down under Default Site ... > replication partners and there should be bserver. ... The File Replication Service moved the preexisting files in ...
    (microsoft.public.windows.server.general)