Directory Server completely Hosed: Netlogon and SYSVOL replication through firewalls


hopefully can point me in right direction.

 

suspect filtered firewall traffic issue dc666 sits in between 2 replication partners.

thinking applying steps outlined in article: http://support.microsoft.com/kb/899148 (win2ksp2).

i rebuilt domain controller (dc666) scratch yesterday.  did metadata cleanup on it's replication partners, , made sure replication of ntds successful throughout domain.  after rebuild dcpromo'd dc , first indication got wrong  sysvol wasn't sharing , netlogon share wasn't created.

was thinking doing burflags registry thing rebuild contents of sysvol tree in entire domain, that's thirty separate domain controllers.

checked make sure junction points in sysvol there , were.

looking through event logs last night, pretty happy people able authenticate server.  directory service event logs looked , did dns.  morning came in , every thing messed up.  dns empty of records (complete replication existed yesterday).

the complication domain controller bridge between our dc000 (which holds fsmo roles, in (site-a) , upstream server several sites) , segregated site (default-first-site-name).  dc666 supposed replication (site-a) , (default-first-site-name) , push them in either direction.

another issue had when promoting dc666 joined dc999 (default-first-site-name), when wanted join dc000.  thinking disable dc666 dc999 filter?

about firewall in between:

sidewinder 6.1

dc000 (internal burb)

dc666 (services burb)

dc999 (external burb)

ip filters:

allow dc999 - dc000

tcp 53, 88, 123,135, 137, 389, 445, 500, 636, 1024-1065, 3268-3269, 49152

udp 53, 88, 123,135, 137, 389, 445,

allow dc000 - dc999

tcp 53, 88, 123,135, 137, 389, 445, 500, 636, 1024-1065, 3268-3269, 49152

udp 53, 88, 123,135, 137, 389, 445,

allow dc000 - dc666

tcp 53, 88, 123,135, 137, 389, 445, 500, 636, 1024-1065, 3268-3269, 49152

udp 53, 88, 123,135, 137, 389, 445,

allow dc666 - dc000

tcp 53, 88, 123,135, 137, 389, 445, 500, 636, 1024-1065, 3268-3269, 49152

udp 53, 88, 123,135, 137, 389, 445,

allow dc999, dc666

tcp 53, 88, 123,135, 137, 389, 445, 500, 636, 1024-1065, 3268-3269, 49152

udp 53, 88, 123,135, 137, 389, 445,

allow dc666 - dc999

tcp 53, 88, 123,135, 137, 389, 445, 500, 636, 1024-1065, 3268-3269, 49152

udp 53, 88, 123,135, 137, 389, 445,

 

questions:

can dcpromo dc666 down member server (hopefully without /forceremoval) rename , re-promote it?

daniel,

considering operating in firewalled environment, might want designate bridgehead servers each site control flow of intersite replication traffic , creation of automatic connections (or even conifgure them manually). if dcs not automatically added correct site during dcpromo, indicates site/subnet configuration not correct - have verified whether case?

you coud demote newly promoted dc (if this fails you need to clean ad metadata afterwards by following http://support.microsoft.com/kb/555846) i'd consider if ad replication functioning properly.

hth
marcin



Windows Server  >  Directory Services



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...