ullmanneric
asked on
New Domain COntroller not showing up in Exchange directory access
We have just put a new DC online and transfered all five roles to the new server. DNS has bee installed and confiqured however the new dc does not shwo up in exchange directory access
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
When I look at the file replication service on dc1 which is the new domain controller I keep getting a 13508 event
Try reviewing http://www.eventid.net/display.asp?eventid=13508&eventno=349&source=ntfrs&phase=1
OR
http://technet.microsoft.com/en-us/library/bb727056.aspx
First. netdiag and dcdiag should show no failures before continuing to try to resolve this problem. You may need to open additional questions to solve any new problems that appear in netdiag or dcdiag.
OR
http://technet.microsoft.com/en-us/library/bb727056.aspx
First. netdiag and dcdiag should show no failures before continuing to try to resolve this problem. You may need to open additional questions to solve any new problems that appear in netdiag or dcdiag.
By the way if by 6 nodes you meant 6 clients it shouldnt matter beucase it doesnt need to replicate to clients. If you meant 6 domain controllers, replication is almost immediate to any local DCs but if the other DCs are on distant networks or domains it make take longer depending on what you have set as your replication intervals and domain topology.
To make things simple, at this point it just sounds like its having trouble replicating but I didnt want to ignore your question about how long it should take for replication.
To make things simple, at this point it just sounds like its having trouble replicating but I didnt want to ignore your question about how long it should take for replication.
ASKER
Here is the output when i run dcdiag and netdiag. ANy suggestions? You will noticed the old domain is xxx and the new is dc1
dcdiag.txt
netdiag.log
dcdiag.txt
netdiag.log
ASKER
Any suggestions?
ASKER
The command completed successfully.
C:\Documents and Settings\Administrator.xxx
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC
Starting test: Connectivity
......................... DC1 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC
Starting test: Replications
......................... DC1 passed test Replications
Starting test: NCSecDesc
......................... DC1 passed test NCSecDesc
Starting test: NetLogons
......................... DC1 passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\xxx.xxx.com, when we were trying to reach DC1.
Server is not responding or is not considered suitable.
......................... DC1 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... DC1 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... DC1 passed test RidManager
Starting test: MachineAccount
......................... DC1 passed test MachineAccount
Starting test: Services
......................... DC1 passed test Services
Starting test: ObjectsReplicated
......................... DC1 passed test ObjectsReplicated
Starting test: frssysvol
......................... DC1 passed test frssysvol
Starting test: frsevent
There are warning or error events within the last 24 hours after the
SYSVOL has been shared. Failing SYSVOL replication problems may cause
Group Policy problems.
......................... DC1 failed test frsevent
Starting test: kccevent
......................... DC1 passed test kccevent
Starting test: systemlog
......................... DC1 passed test systemlog
Starting test: VerifyReferences
......................... DC1 passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : medittech
Starting test: CrossRefValidation
......................... xxx.com passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... xxx.com passed test CheckSDRefDom
Running enterprise tests on : xxx.com
Starting test: Intersite
......................... xxx.com passed test Intersite
Starting test: FsmoCheck
......................... xxx.com passed test FsmoCheck
ASKER
..........................
Computer Name: DC1
DNS Host Name: dc1.xxx.com
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 15 Model 2 Stepping 7, GenuineIntel
List of installed hotfixes :
Q147222
Netcard queries test . . . . . . . : Passed
[WARNING] The net card 'Intel(R) PRO/1000 XT Server Adapter #2' may not be w
orking.
[WARNING] The net card 'Intel(R) PRO/1000 XT Network Connection' may not be
working.
Per interface results:
Adapter : Local Area Connection 3
Netcard queries test . . . : Failed
NetCard Status: DISCONNECTED
Some tests will be skipped on this interface.
Host Name. . . . . . . . . : dc1
Autoconfiguration IP Address : 169.254.127.86
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . :
Adapter : Local Area Connection
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : dc1
IP Address . . . . . . . . : 192.168.1.200
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.1.1
Dns Servers. . . . . . . . : 192.168.1.2
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Adapter : Local Area Connection 2
Netcard queries test . . . : Failed
NetCard Status: DISCONNECTED
Some tests will be skipped on this interface.
Host Name. . . . . . . . . : dc1
Autoconfiguration IP Address : 169.254.240.184
Subnet Mask. . . . . . . . : 255.255.0.0
Default Gateway. . . . . . :
Dns Servers. . . . . . . . :
Global results:
Domain membership test . . . . . . : Failed
[WARNING] Ths system volume has not been completely replicated to the local
machine. This machine is not working properly as a DC.
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{4E00D8E6-6838
NetBT_Tcpip_{8675F214-7BDC
NetBT_Tcpip_{EB205F01-D3C4
3 NetBt transports currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
[WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
[WARNING] Cannot find a primary authoritative DNS server for the name
'dc1.medittech.com.'. [ERROR_TIMEOUT]
The name 'dc1.medittech.com.' may not be registered in DNS.
[WARNING] Cannot find a primary authoritative DNS server for the name
'dc1.medittech.com.'. [ERROR_TIMEOUT]
The name 'dc1.medittech.com.' may not be registered in DNS.
PASS - All the DNS entries for DC are registered on DNS server '192.168.1.2'
and other DCs also have some of the names registered.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{4E00D8E6-6838
NetBT_Tcpip_{8675F214-7BDC
NetBT_Tcpip_{EB205F01-D3C4
The redir is bound to 3 NetBt transports.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{8675F214-7BDC
NetBT_Tcpip_{4E00D8E6-6838
NetBT_Tcpip_{EB205F01-D3C4
The browser is bound to 3 NetBt transports.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Passed
Secure channel for domain 'xxx' is to '\\xxx.xxx.com
'.
Kerberos test. . . . . . . . . . . : Passed
LDAP test. . . . . . . . . . . . . : Passed
Bindings test. . . . . . . . . . . : Passed
WAN configuration test . . . . . . : Skipped
No active remote access connections.
Modem diagnostics test . . . . . . : Passed
IP Security test . . . . . . . . . : Skipped
Note: run "netsh ipsec dynamic show /?" for more detailed information
The command completed successfully
ASKER
Please look at these logs above and let me know
ASKER
When i check the event log I keep getting event 13508.
Please help
Please help
Is there a reason why this server is trying to use 192.168.1.2 as its DNS server? Shouldn't it be using 127.0.0.1 to point to itself??
ASKER
Which server the old server is the dns server dns 1 should look at 192.168.1.2
So obviously sysvol isnt replicating properly. Could you try running netdiag /fix ?
There is also another question open along the same lines
https://www.experts-exchange.com/questions/23630051/WARNING-Ths-system-volume-has-not-been-completely-replicated-to-the-local-Machine.html
One of the experts suggested editing the registry to reset "SysvolReady" flag under HKEY_LOCAL_MACHINE\System\
There is also another question open along the same lines
https://www.experts-exchange.com/questions/23630051/WARNING-Ths-system-volume-has-not-been-completely-replicated-to-the-local-Machine.html
One of the experts suggested editing the registry to reset "SysvolReady" flag under HKEY_LOCAL_MACHINE\System\
ASKER