Discussion:
AD Replication issues
(too old to reply)
Toni Rantanen
2009-06-01 19:51:02 UTC
Permalink
Hi,

My client is having two different Active Directory replication issues in
same domain. At least I believe that these are two separete issues. I just
wanted to report these in same message because I'm not sure if these problems
have something to do with each other. Domain functional level is Windows
Server 2003 and all DC's are having operating system Windows Server 2003 SP2
standard.

Please see output of AD Replication Monitor - Search Domain Controllers For
Replication Failures:

********************************************************
Active Directory Replication Domain Controller Replication Failure Output
Printed at 1.6.2009 22:13:40

Below are the replication failures detected on Domain Controllers for this
domain:

Domain Controller Name: DC01
Directory Partition: DC=domain,DC=net
Replication Partner: SITE2\DC02
Failure Code: 1818
Failure Reason: The remote procedure call was
cancelled.

Domain Controller Name: DC03
Directory Partition: DC=domain,DC=net
Replication Partner: SITE4\DC04
Failure Code: 1818
Failure Reason: The remote procedure call was
cancelled.
********************************************************


PROBLEM 1: DC01-DC02

I can see following Warnings in DC01 computer's Event Viewer Directory
Service log:

********************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Date: 1.6.2009
Time: 21:40:52
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC01
Description:
Active Directory attempted to perform a remote procedure call (RPC) to the
following server. The call timed out and was cancelled.

Server:
ee15dc9e-173b-4a0d-b5c4-a823b5f6063a._msdcs.domain.net
Call Timeout (Mins):
45
Thread ID:
a78

Additional Data
Internal ID:
5001047

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************

and

********************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
Date: 1.6.2009
Time: 21:40:52
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC01
Description:
A thread in Active Directory is waiting for the completion of a RPC made to
the following domain controller.

Domain controller:
ee15dc9e-173b-4a0d-b5c4-a823b5f6063a._msdcs.domain.net
Operation:
get changes
Thread ID:
a78
Timeout period (minutes):
45

Active Directory has attempted to cancel the call and recover this thread.

User Action
If this condition continues, restart the domain controller.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************

Based on Knowledge Base article (http://support.microsoft.com/kb/830746) I
have tried to increase the value of the RPC timeout for Active Directory
replication from 5 minutes to 45 minutes. This didn't solved the issue.

Network bandwidth is quite slow between DC01 and DC02 (ping round trip time
about 400ms) but we have other sites having even slower connection but AD
replication working fine.

I have already troubleshooted this issue with network service provider but
they state that there is no network related errors between those two
computers.


PROBLEM 2: DC03-DC04

I can see following Warnings and Errors in DC03 computer's Event Viewer
Directory Service log:

********************************************************
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 2.6.2009
Time: 1:33:01
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
Description:
The Knowledge Consistency Checker (KCC) was unable to form a complete
spanning tree network topology. As a result, the following list of sites
cannot be reached from the local site.

Sites:
CN=SITE4,CN=Sites,CN=Configuration,DC=domain,DC=net


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************

and

********************************************************
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 2.6.2009
Time: 1:33:01
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
Description:
The Knowledge Consistency Checker (KCC) has detected problems with the
following directory partition.

Directory partition:
CN=Configuration,DC=domain,DC=net

There is insufficient site connectivity information in Active Directory
Sites and Services for the KCC to create a spanning tree replication
topology. Or, one or more domain controllers with this directory partition
are unable to replicate the directory partition information. This is probably
due to inaccessible domain controllers.

User Action
Use Active Directory Sites and Services to perform one of the following
actions:
- Publish sufficient site connectivity information so that the KCC can
determine a route by which this directory partition can reach this site. This
is the preferred option.
- Add a Connection object to a domain controller that contains the directory
partition in this site from a domain controller that contains the same
directory partition in another site.

If neither of the Active Directory Sites and Services tasks correct this
condition, see previous events logged by the KCC that identify the
inaccessible domain controllers.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************

and

********************************************************
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 2.6.2009
Time: 1:33:01
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
Description:
The Knowledge Consistency Checker (KCC) was unable to form a complete
spanning tree network topology. As a result, the following list of sites
cannot be reached from the local site.

Sites:
CN=SITE4,CN=Sites,CN=Configuration,DC=domain,DC=net


For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

********************************************************

I have double-check my AD Sites and Services configurations and everything
should be ok there.

I would appreciate if you could help me solving these issues. Thanks in
advance.

Best regards,

Toni Rantanen
Ace Fekay [Microsoft Certified Trainer]
2009-06-02 00:36:29 UTC
Permalink
Post by Toni Rantanen
Hi,
My client is having two different Active Directory replication issues in
same domain. At least I believe that these are two separete issues. I just
wanted to report these in same message because I'm not sure if these problems
have something to do with each other. Domain functional level is Windows
Server 2003 and all DC's are having operating system Windows Server 2003 SP2
standard.
Please see output of AD Replication Monitor - Search Domain Controllers For
[snipped]
Post by Toni Rantanen
I have double-check my AD Sites and Services configurations and everything
should be ok there.
I would appreciate if you could help me solving these issues. Thanks in
advance.
Best regards,
Toni Rantanen
Hello Tony,

Can you post an unedited ipconfig /all from your DCs in all sites, please? It would be helpful to gain a little knowledge of your DNS resolving infrastructure before attempting to offer a diagnosis. Describe the WAN connection types and speeds, firewall types, VPN, etc, please.

Slow connectivity would be a big factor. If you can get a bandwidth test between locations, that would be helpful, or at least the speed of the line. Keep in mind, the GPO threshold is 500K, however, 128k is basically bare minimum for DCs between locations, but even if it is higher, and there's other traffic (resolution, internet, file transfers, and other type of traffic), that will significantly effect speed and RPC. RPC is not forgiving when it comes to speed drops. Also firewall rules, if misconfigured (should configure to allow ALL), will be a major factor, as well as the type of WAN link. MTUs below 1500 will major cause problems, too. For example, MTU of 1492 is used by ISPs for ADSL connectivity, and causes problems with RPC and LDAP.
--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
***@mvps.RemoveThisPart.org

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay
Meinolf Weber [MVP-DS]
2009-06-02 08:52:59 UTC
Permalink
Hello Toni,

Please post an unedited ipconfig /all from the problem DC and also from another
in the site. Please describe a bit more detailed the network setup.

Does something like a crash happen before or reinstall from backup etc.?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Post by Toni Rantanen
Hi,
My client is having two different Active Directory replication issues
in same domain. At least I believe that these are two separete issues.
I just wanted to report these in same message because I'm not sure if
these problems have something to do with each other. Domain functional
level is Windows Server 2003 and all DC's are having operating system
Windows Server 2003 SP2 standard.
Please see output of AD Replication Monitor - Search Domain
********************************************************
Active Directory Replication Domain Controller Replication Failure Output
Printed at 1.6.2009 22:13:40
Below are the replication failures detected on Domain Controllers for
Domain Controller Name: DC01
Directory Partition: DC=domain,DC=net
Replication Partner: SITE2\DC02
Failure Code: 1818
Failure Reason: The remote procedure call
was
cancelled.
Domain Controller Name: DC03
Directory Partition: DC=domain,DC=net
Replication Partner: SITE4\DC04
Failure Code: 1818
Failure Reason: The remote procedure call
was
cancelled.
********************************************************
PROBLEM 1: DC01-DC02
I can see following Warnings in DC01 computer's Event Viewer Directory
********************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Date: 1.6.2009
Time: 21:40:52
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC01
Active Directory attempted to perform a remote procedure call (RPC) to the
following server. The call timed out and was cancelled.
ee15dc9e-173b-4a0d-b5c4-a823b5f6063a._msdcs.domain.net
45
a78
Additional Data
5001047
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************
and
********************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
Date: 1.6.2009
Time: 21:40:52
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC01
A thread in Active Directory is waiting for the completion of a RPC made to
the following domain controller.
ee15dc9e-173b-4a0d-b5c4-a823b5f6063a._msdcs.domain.net
get changes
a78
45
Active Directory has attempted to cancel the call and recover this thread.
User Action If this condition continues, restart the domain
controller.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************
Based on Knowledge Base article
(http://support.microsoft.com/kb/830746) I have tried to increase the
value of the RPC timeout for Active Directory replication from 5
minutes to 45 minutes. This didn't solved the issue.
Network bandwidth is quite slow between DC01 and DC02 (ping round trip
time about 400ms) but we have other sites having even slower
connection but AD replication working fine.
I have already troubleshooted this issue with network service provider
but they state that there is no network related errors between those
two computers.
PROBLEM 2: DC03-DC04
I can see following Warnings and Errors in DC03 computer's Event
********************************************************
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 2.6.2009
Time: 1:33:01
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
The Knowledge Consistency Checker (KCC) was unable to form a complete
spanning tree network topology. As a result, the following list of sites
cannot be reached from the local site.
Sites: CN=SITE4,CN=Sites,CN=Configuration,DC=domain,DC=net
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************
and
********************************************************
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 2.6.2009
Time: 1:33:01
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
The Knowledge Consistency Checker (KCC) has detected problems with the
following directory partition.
CN=Configuration,DC=domain,DC=net
There is insufficient site connectivity information in Active
Directory Sites and Services for the KCC to create a spanning tree
replication topology. Or, one or more domain controllers with this
directory partition are unable to replicate the directory partition
information. This is probably due to inaccessible domain controllers.
User Action Use Active Directory Sites and Services to perform one of
the following actions: - Publish sufficient site connectivity
information so that the KCC can determine a route by which this
directory partition can reach this site. This is the preferred option.
- Add a Connection object to a domain controller that contains the
directory partition in this site from a domain controller that
contains the same directory partition in another site.
If neither of the Active Directory Sites and Services tasks correct
this condition, see previous events logged by the KCC that identify
the inaccessible domain controllers.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************
and
********************************************************
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 2.6.2009
Time: 1:33:01
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
The Knowledge Consistency Checker (KCC) was unable to form a complete
spanning tree network topology. As a result, the following list of sites
cannot be reached from the local site.
Sites: CN=SITE4,CN=Sites,CN=Configuration,DC=domain,DC=net
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************
I have double-check my AD Sites and Services configurations and
everything should be ok there.
I would appreciate if you could help me solving these issues. Thanks
in advance.
Best regards,
Toni Rantanen
Paul Bergson [MVP-DS]
2009-06-02 12:38:04 UTC
Permalink
Along with the ipconfig /all the others have suggested:


Run diagnostics against your Active Directory domain.

If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> ntfrsutl ds your_dc_name > c:\sysvol.log
-> dnslint /ad /s "ip address of your dc"

**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take into
account slow links to dc's will also add to the testing time.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests without
having to learn all the switch options. The details will be output in
notepad text files that pop up automagically.

The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.

Description and download for dnslint
http://support.microsoft.com/kb/321045
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
Post by Toni Rantanen
Hi,
My client is having two different Active Directory replication issues in
same domain. At least I believe that these are two separete issues. I just
wanted to report these in same message because I'm not sure if these problems
have something to do with each other. Domain functional level is Windows
Server 2003 and all DC's are having operating system Windows Server 2003 SP2
standard.
Please see output of AD Replication Monitor - Search Domain Controllers For
********************************************************
Active Directory Replication Domain Controller Replication Failure Output
Printed at 1.6.2009 22:13:40
Below are the replication failures detected on Domain Controllers for this
Domain Controller Name: DC01
Directory Partition: DC=domain,DC=net
Replication Partner: SITE2\DC02
Failure Code: 1818
Failure Reason: The remote procedure call was
cancelled.
Domain Controller Name: DC03
Directory Partition: DC=domain,DC=net
Replication Partner: SITE4\DC04
Failure Code: 1818
Failure Reason: The remote procedure call was
cancelled.
********************************************************
PROBLEM 1: DC01-DC02
I can see following Warnings in DC01 computer's Event Viewer Directory
********************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1232
Date: 1.6.2009
Time: 21:40:52
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC01
Active Directory attempted to perform a remote procedure call (RPC) to the
following server. The call timed out and was cancelled.
ee15dc9e-173b-4a0d-b5c4-a823b5f6063a._msdcs.domain.net
45
a78
Additional Data
5001047
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************
and
********************************************************
Event Type: Warning
Event Source: NTDS Replication
Event Category: DS RPC Client
Event ID: 1188
Date: 1.6.2009
Time: 21:40:52
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC01
A thread in Active Directory is waiting for the completion of a RPC made to
the following domain controller.
ee15dc9e-173b-4a0d-b5c4-a823b5f6063a._msdcs.domain.net
get changes
a78
45
Active Directory has attempted to cancel the call and recover this thread.
User Action
If this condition continues, restart the domain controller.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************
Based on Knowledge Base article (http://support.microsoft.com/kb/830746) I
have tried to increase the value of the RPC timeout for Active Directory
replication from 5 minutes to 45 minutes. This didn't solved the issue.
Network bandwidth is quite slow between DC01 and DC02 (ping round trip time
about 400ms) but we have other sites having even slower connection but AD
replication working fine.
I have already troubleshooted this issue with network service provider but
they state that there is no network related errors between those two
computers.
PROBLEM 2: DC03-DC04
I can see following Warnings and Errors in DC03 computer's Event Viewer
********************************************************
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 2.6.2009
Time: 1:33:01
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
The Knowledge Consistency Checker (KCC) was unable to form a complete
spanning tree network topology. As a result, the following list of sites
cannot be reached from the local site.
CN=SITE4,CN=Sites,CN=Configuration,DC=domain,DC=net
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************
and
********************************************************
Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 2.6.2009
Time: 1:33:01
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
The Knowledge Consistency Checker (KCC) has detected problems with the
following directory partition.
CN=Configuration,DC=domain,DC=net
There is insufficient site connectivity information in Active Directory
Sites and Services for the KCC to create a spanning tree replication
topology. Or, one or more domain controllers with this directory partition
are unable to replicate the directory partition information. This is probably
due to inaccessible domain controllers.
User Action
Use Active Directory Sites and Services to perform one of the following
- Publish sufficient site connectivity information so that the KCC can
determine a route by which this directory partition can reach this site. This
is the preferred option.
- Add a Connection object to a domain controller that contains the directory
partition in this site from a domain controller that contains the same
directory partition in another site.
If neither of the Active Directory Sites and Services tasks correct this
condition, see previous events logged by the KCC that identify the
inaccessible domain controllers.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************
and
********************************************************
Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1865
Date: 2.6.2009
Time: 1:33:01
User: NT AUTHORITY\ANONYMOUS LOGON
Computer: DC03
The Knowledge Consistency Checker (KCC) was unable to form a complete
spanning tree network topology. As a result, the following list of sites
cannot be reached from the local site.
CN=SITE4,CN=Sites,CN=Configuration,DC=domain,DC=net
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
********************************************************
I have double-check my AD Sites and Services configurations and everything
should be ok there.
I would appreciate if you could help me solving these issues. Thanks in
advance.
Best regards,
Toni Rantanen
Toni Rantanen
2009-06-03 09:12:02 UTC
Permalink
Hello,

Thanks for your help Ace, Meinolf and Paul.

For security reasons I modified in my earlier post name of the DC's and name
of the domain. Now I thought that there would be too much work to go through
all outputs Paul requested and modify the names, so all outputs are now
unmodified.

Please find out ipconfig /all from all four DC's that you all requested.

DC01 - FIALEDC01 (Site: FIALE)
***********************
Windows IP Configuration

Host Name . . . . . . . . . . . . : FIALEDC01
Primary Dns Suffix . . . . . . . : dynea.net
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dynea.net
eu.dynea.net
dynea.com

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-50-56-A5-26-AC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.200.52
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.200.1
DNS Servers . . . . . . . . . . . : 10.1.200.52
10.1.201.32
Primary WINS Server . . . . . . . : 10.1.200.55
***********************

DC02 - VNHCMDC01 (Site: VNHCM)
***********************
Windows IP Configuration

Host Name . . . . . . . . . . . . : VNHCMDC01
Primary Dns Suffix . . . . . . . : dynea.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dynea.net
eu.dynea.net
dynea.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : dynea.net
Description . . . . . . . . . . . : HP NC7761 Gigabit Server Adapter
Physical Address. . . . . . . . . : 00-13-21-AE-66-62
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.171.45
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.171.253
DNS Servers . . . . . . . . . . . : 10.1.171.45
10.1.167.45
Primary WINS Server . . . . . . . : 10.1.200.55
***********************

DC03 - SGSGDC01 (Site: SGSG)
***********************
Windows IP Configuration

Host Name . . . . . . . . . . . . : SGSGDC01
Primary Dns Suffix . . . . . . . : dynea.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dynea.net
eu.dynea.net
dynea.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : dynea.net
Description . . . . . . . . . . . : HP NC7761 Gigabit Server Adapter
Physical Address. . . . . . . . . : 00-13-21-FC-A2-03
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.167.45
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.167.1
DNS Servers . . . . . . . . . . . : 10.1.167.45
10.1.201.32
Primary WINS Server . . . . . . . : 10.1.200.55
***********************

DC04 - CHGUADC02 (Site: CHGUA)
***********************
Windows IP Configuration

Host Name . . . . . . . . . . . . : CHGUADC02
Primary Dns Suffix . . . . . . . : dynea.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dynea.net
eu.dynea.net
dynea.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : dynea.net
Description . . . . . . . . . . . : HP NC7761 Gigabit Server Adapter
Physical Address. . . . . . . . . : 00-14-38-4E-A4-2F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.175.45
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.175.1
DNS Servers . . . . . . . . . . . : 10.1.175.45
10.1.167.45
Primary WINS Server . . . . . . . : 10.1.200.55
*******************

For Ace's questions about network...
There is different network service provider between FIALEDC01 (DC01) and
VNHCMDC01 (DC02) than there is on SGSGDC01 (DC03) and CHGUADC02 (DC04). I
have contacted both network service providers and here is what network
service provider between FIALEDC01 and VNHCMDC01 respond:

"There is IPsec VPN connection through public internet. VPN tunnel is
terminated to a statefull firewall at both ends and everything is allowed
through that tunnel. Line speed is 512K. The latency of the connection varies
quite a lot especially with bigger packets. Like: --- 10.1.200.52 ping
statistics for 1000 byte packet --- 50 packets transmitted, 50 packets
received, 0% packet loss round-trip min/avg/max = 421.8/930.7/2403.9 ms. On
the firewall the physical interface's MTU is 1500 but because it is an IPsec
tunnel there is an header overhead."

I haven't received reply from network service provider between SGSGDC01 and
CHGUADC02 but that connection much more faster than between FIALEDC01 and
VNHCMDC01. SGSGDC01 and CHGUADC02 are connected to each other with MPLS
connection. As soon as I get more details of network connection between
SGSGDC01 and CHGUADC02, I'll provide it to you.


For Meinolf's questions...
I hope you did receive enogh information about netwrok setup on above. There
is no crash or reinstall from backup that could have caused this. These DC's
have been running for some years and now the problems suddenly started 1-2
weeks ago.


For Paul's questions about those outputs...
Would you like me to copy/paste results of those test here? I think can't
attach files here, or...? If I copy/paste everything here, then it's going to
be long posting. :)


Best regards,

Toni Rantanen
Ace Fekay [Microsoft Certified Trainer]
2009-06-04 03:19:14 UTC
Permalink
Post by Toni Rantanen
Hello,
Thanks for your help Ace, Meinolf and Paul.
For security reasons I modified in my earlier post name of the DC's and name
of the domain. Now I thought that there would be too much work to go through
all outputs Paul requested and modify the names, so all outputs are now
unmodified.
Please find out ipconfig /all from all four DC's that you all requested.
DC01 - FIALEDC01 (Site: FIALE)
***********************
Windows IP Configuration
Host Name . . . . . . . . . . . . : FIALEDC01
Primary Dns Suffix . . . . . . . : dynea.net
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dynea.net
eu.dynea.net
dynea.com
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet Adapter
Physical Address. . . . . . . . . : 00-50-56-A5-26-AC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.200.52
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.200.1
DNS Servers . . . . . . . . . . . : 10.1.200.52
10.1.201.32
Primary WINS Server . . . . . . . : 10.1.200.55
***********************
DC02 - VNHCMDC01 (Site: VNHCM)
***********************
Windows IP Configuration
Host Name . . . . . . . . . . . . : VNHCMDC01
Primary Dns Suffix . . . . . . . : dynea.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dynea.net
eu.dynea.net
dynea.com
Connection-specific DNS Suffix . : dynea.net
Description . . . . . . . . . . . : HP NC7761 Gigabit Server Adapter
Physical Address. . . . . . . . . : 00-13-21-AE-66-62
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.171.45
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.171.253
DNS Servers . . . . . . . . . . . : 10.1.171.45
10.1.167.45
Primary WINS Server . . . . . . . : 10.1.200.55
***********************
DC03 - SGSGDC01 (Site: SGSG)
***********************
Windows IP Configuration
Host Name . . . . . . . . . . . . : SGSGDC01
Primary Dns Suffix . . . . . . . : dynea.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dynea.net
eu.dynea.net
dynea.com
Connection-specific DNS Suffix . : dynea.net
Description . . . . . . . . . . . : HP NC7761 Gigabit Server Adapter
Physical Address. . . . . . . . . : 00-13-21-FC-A2-03
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.167.45
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.167.1
DNS Servers . . . . . . . . . . . : 10.1.167.45
10.1.201.32
Primary WINS Server . . . . . . . : 10.1.200.55
***********************
DC04 - CHGUADC02 (Site: CHGUA)
***********************
Windows IP Configuration
Host Name . . . . . . . . . . . . : CHGUADC02
Primary Dns Suffix . . . . . . . : dynea.net
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dynea.net
eu.dynea.net
dynea.com
Connection-specific DNS Suffix . : dynea.net
Description . . . . . . . . . . . : HP NC7761 Gigabit Server Adapter
Physical Address. . . . . . . . . : 00-14-38-4E-A4-2F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.1.175.45
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.1.175.1
DNS Servers . . . . . . . . . . . : 10.1.175.45
10.1.167.45
Primary WINS Server . . . . . . . : 10.1.200.55
*******************
For Ace's questions about network...
There is different network service provider between FIALEDC01 (DC01) and
VNHCMDC01 (DC02) than there is on SGSGDC01 (DC03) and CHGUADC02 (DC04). I
have contacted both network service providers and here is what network
"There is IPsec VPN connection through public internet. VPN tunnel is
terminated to a statefull firewall at both ends and everything is allowed
through that tunnel. Line speed is 512K. The latency of the connection varies
quite a lot especially with bigger packets. Like: --- 10.1.200.52 ping
statistics for 1000 byte packet --- 50 packets transmitted, 50 packets
received, 0% packet loss round-trip min/avg/max = 421.8/930.7/2403.9 ms. On
the firewall the physical interface's MTU is 1500 but because it is an IPsec
tunnel there is an header overhead."
I haven't received reply from network service provider between SGSGDC01 and
CHGUADC02 but that connection much more faster than between FIALEDC01 and
VNHCMDC01. SGSGDC01 and CHGUADC02 are connected to each other with MPLS
connection. As soon as I get more details of network connection between
SGSGDC01 and CHGUADC02, I'll provide it to you.
For Meinolf's questions...
I hope you did receive enogh information about netwrok setup on above. There
is no crash or reinstall from backup that could have caused this. These DC's
have been running for some years and now the problems suddenly started 1-2
weeks ago.
For Paul's questions about those outputs...
Would you like me to copy/paste results of those test here? I think can't
attach files here, or...? If I copy/paste everything here, then it's going to
be long posting. :)
Best regards,
Toni Rantanen
Hi Toni,

Lot's of info. I had to actually draw it out on paper to get a better 'view'
of it.

The ping times between Sites FIALE and VNHCM, 421.8/930.7/2403.9 ms, are
kind of high. Even the lowest one at 421 is kind of high, especially if that
is the minimal one. That would explain RPC failing. What other type of
traffic is on this line?

Which site is the central site?
How are the sites connected? In a mesh, or do you have it as a hub and
spoke?

Ace
Ace Fekay [Microsoft Certified Trainer]
2009-06-04 05:06:49 UTC
Permalink
Post by Ace Fekay [Microsoft Certified Trainer]
Hi Toni,
Lot's of info. I had to actually draw it out on paper to get a better
'view' of it.
The ping times between Sites FIALE and VNHCM, 421.8/930.7/2403.9 ms, are
kind of high. Even the lowest one at 421 is kind of high, especially if
that is the minimal one. That would explain RPC failing. What other type
of traffic is on this line?
Which site is the central site?
How are the sites connected? In a mesh, or do you have it as a hub and
spoke?
Ace
Also, forgot to ask, why are those additional search suffixes on the DCs?

Ace
Toni Rantanen
2009-06-04 14:22:01 UTC
Permalink
Hi Ace,

I agree that ping time between FIALE and VNHCM is high. Around 400ms is
minimum for 1000 byte packet. But we have other sites as well with even worse
bandwidth and ping results but replication is working. That's why I doubt
that slow bandwidth between FIALE and VNHCM would cause this issue.

There shouldn't be any other traffic. I can ask network service provider to
confirm this again but this is what they stated to me earlier.

I can try draw some picture on here below about site and replication
structure:

FIDHC (DC's with FSMO roles)
| |
FIALE SGSG
| |
VNHCM CHGUA

Hope this helps you to grasp the situation. Every site should be able to see
each other over the network. There is being used both IPSec VPN and MPLS
connections between the sites.

I'm not sure why additional search suffixes are on the DCs. There is still
working old domain named "eu.dynea.net" (which is going to be decomissioned
soon) and computers in DMZ are FQDN like: computername.dynea.com. Those
additional search suffixes have been delivered by script to whole dynea.net
domain. Do you think that these are causing some problems when being on DCs
as well?

From my earlier post there were missing information about SGSG and CHGUA
connectivity. Unfortunately I still haven't reached MPLS network service
provider. But as said it is MPLS connection and here are details about
connection speed: 10.1.167.45 ping -> 10.1.175.45 statistics for 1000 byte
packet - 50 packets transmitted, 50 packets received, 0% packet loss
round-trip > min/avg/max = 138/138/139 ms. So it's definetely better
connection than between FIALE and VNHCM sites.

Paul asked me in his earlier post some DCDIAG, netdiag, etc. outputs. Could
you please advice on how should I deliver these posts to you guys? If
copy/paste them to here, it's going very long post. :)

I have noticed that when running netdiag on VNHCMDC01 and CHGUADC02, I've
been having problems to copy output text files from these two servers. This
must be some network connection related issue, or what do you think? I
receive error message that "network share no longer exists" or something like
that. But I am wondering why so, especially between SGSG and CHGUA, based
ping results network connection should be ok...

I really appreciate your help. Thanks already. I hope we get these problems
solved asap.

Best regards,

Toni
Ace Fekay [Microsoft Certified Trainer]
2009-06-04 15:45:52 UTC
Permalink
Post by Toni Rantanen
Hi Ace,
I agree that ping time between FIALE and VNHCM is high. Around 400ms is
minimum for 1000 byte packet. But we have other sites as well with even worse
bandwidth and ping results but replication is working. That's why I doubt
that slow bandwidth between FIALE and VNHCM would cause this issue.
There shouldn't be any other traffic. I can ask network service provider to
confirm this again but this is what they stated to me earlier.
I can try draw some picture on here below about site and replication
FIDHC (DC's with FSMO roles)
| |
FIALE SGSG
| |
VNHCM CHGUA
Hope this helps you to grasp the situation. Every site should be able to see
each other over the network. There is being used both IPSec VPN and MPLS
connections between the sites.
I'm not sure why additional search suffixes are on the DCs. There is still
working old domain named "eu.dynea.net" (which is going to be
decomissioned
soon) and computers in DMZ are FQDN like: computername.dynea.com. Those
additional search suffixes have been delivered by script to whole dynea.net
domain. Do you think that these are causing some problems when being on DCs
as well?
From my earlier post there were missing information about SGSG and CHGUA
connectivity. Unfortunately I still haven't reached MPLS network service
provider. But as said it is MPLS connection and here are details about
connection speed: 10.1.167.45 ping -> 10.1.175.45 statistics for 1000 byte
packet - 50 packets transmitted, 50 packets received, 0% packet loss
round-trip > min/avg/max = 138/138/139 ms. So it's definetely better
connection than between FIALE and VNHCM sites.
Paul asked me in his earlier post some DCDIAG, netdiag, etc. outputs. Could
you please advice on how should I deliver these posts to you guys? If
copy/paste them to here, it's going very long post. :)
I have noticed that when running netdiag on VNHCMDC01 and CHGUADC02, I've
been having problems to copy output text files from these two servers. This
must be some network connection related issue, or what do you think? I
receive error message that "network share no longer exists" or something like
that. But I am wondering why so, especially between SGSG and CHGUA, based
ping results network connection should be ok...
I really appreciate your help. Thanks already. I hope we get these problems
solved asap.
Best regards,
Toni
If the other sites are that slow, then the only thing I can think of is
there are firewall rules blocking traffic? If not, it doesn't make sense,
unless of course there is other traffic. But accoriding to your 'diagram' it
appears FIALE is connected to both FIDHC and VNHCM, so there's additional
traffic from the two locations. You said all sites can see each other, then
there is traffic between them as well. Do you only have one IP connector
between all of them, or tehre are specific connectors you created to support
the diagram?

Just paste the errors from the dcdiags and netdiags.

If you are getting "network share no longer exists" between SGSG and CHGUA,
then there is definitely some type of connectivity lag, which can be another
sign for replication problems, but surprisingly not betweenb those two
locations.

The suffixes wouldn't cause problems. Just curious why they are there and
you only indicate you have one domain.

Ace
Toni Rantanen
2009-06-05 09:53:01 UTC
Permalink
Post by Ace Fekay [Microsoft Certified Trainer]
Post by Toni Rantanen
Hi Ace,
I agree that ping time between FIALE and VNHCM is high. Around 400ms is
minimum for 1000 byte packet. But we have other sites as well with even worse
bandwidth and ping results but replication is working. That's why I doubt
that slow bandwidth between FIALE and VNHCM would cause this issue.
There shouldn't be any other traffic. I can ask network service provider to
confirm this again but this is what they stated to me earlier.
I can try draw some picture on here below about site and replication
FIDHC (DC's with FSMO roles)
| |
FIALE SGSG
| |
VNHCM CHGUA
Hope this helps you to grasp the situation. Every site should be able to see
each other over the network. There is being used both IPSec VPN and MPLS
connections between the sites.
I'm not sure why additional search suffixes are on the DCs. There is still
working old domain named "eu.dynea.net" (which is going to be decomissioned
soon) and computers in DMZ are FQDN like: computername.dynea.com. Those
additional search suffixes have been delivered by script to whole dynea.net
domain. Do you think that these are causing some problems when being on DCs
as well?
From my earlier post there were missing information about SGSG and CHGUA
connectivity. Unfortunately I still haven't reached MPLS network service
provider. But as said it is MPLS connection and here are details about
connection speed: 10.1.167.45 ping -> 10.1.175.45 statistics for 1000 byte
packet - 50 packets transmitted, 50 packets received, 0% packet loss
round-trip > min/avg/max = 138/138/139 ms. So it's definetely better
connection than between FIALE and VNHCM sites.
Paul asked me in his earlier post some DCDIAG, netdiag, etc. outputs. Could
you please advice on how should I deliver these posts to you guys? If
copy/paste them to here, it's going very long post. :)
I have noticed that when running netdiag on VNHCMDC01 and CHGUADC02, I've
been having problems to copy output text files from these two servers. This
must be some network connection related issue, or what do you think? I
receive error message that "network share no longer exists" or something like
that. But I am wondering why so, especially between SGSG and CHGUA, based
ping results network connection should be ok...
I really appreciate your help. Thanks already. I hope we get these problems
solved asap.
Best regards,
Toni
If the other sites are that slow, then the only thing I can think of is
there are firewall rules blocking traffic? If not, it doesn't make sense,
unless of course there is other traffic. But accoriding to your 'diagram' it
appears FIALE is connected to both FIDHC and VNHCM, so there's additional
traffic from the two locations. You said all sites can see each other, then
there is traffic between them as well. Do you only have one IP connector
between all of them, or tehre are specific connectors you created to support
the diagram?
Just paste the errors from the dcdiags and netdiags.
If you are getting "network share no longer exists" between SGSG and CHGUA,
then there is definitely some type of connectivity lag, which can be another
sign for replication problems, but surprisingly not betweenb those two
locations.
The suffixes wouldn't cause problems. Just curious why they are there and
you only indicate you have one domain.
Ace
Hi Ace,

I have confirmed from our network service provider that there is no firewall
rules blocking any traffic between FIALE and VNHCM. I still haven't reached
network service provider of link between SGSG and CHGUA.

I have been trying to move netdiag output files (size about 621 KB). When
moving from VNHCMDC01 the netdiag output file I received an error "Cannot
copy netdiag_VNHCMDC01: The specified network name is no longer available".
Even when trying to move the file to a computer in same (100 MB) LAN!! When
trying to move other files between other servers on the same LAN, this works
fine. What do you think, could there be some issue on VNHCMDC01 causing this
problem?

If there is some issue on VNHCMDC01 causing file transfer to fail, I think
that this might be same issue causing the replication fail as well...

I have investigated netdiag files on locally on the servers over Remote
Desktop connection and I haven't found any tests from the files not being in
PASSED state. So I couldn't find any errors from netdiag files.

The DCDIAG that Paul instructed me to run, is still running (has been
running for couple of days). So I won't be able to provide information about
that.
Please find out DCDIAG output below, which has been taken with switches /q
/e /f:"filename".

REPLICATION-RECEIVED LATENCY WARNING
FIDHCDC01: Current time is 2009-06-05 00:15:14.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
FIDHCDC02: Current time is 2009-06-05 00:15:15.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
[Replications Check,FIALEDC01] A recent replication attempt failed:
From VNHCMDC01 to FIALEDC01
Naming Context: DC=dynea,DC=net
The replication generated an error (1818):
The remote procedure call was cancelled.
The failure occurred at 2009-06-04 23:58:19.
The last success occurred at (never).
268 failures have occurred since the last success.
REPLICATION LATENCY WARNING
FIALEDC01: A long-running replication operation is in progress
The job has been executing for 16 minutes and 37 seconds.
Replication of new changes along this path will be delayed.
Error: Higher priority replications are being blocked
Enqueued 2009-06-04 23:52:28 at priority 70
Op: SYNC FROM SOURCE
NC DC=dynea,DC=net
DSADN CN=NTDS
Settings,CN=VNHCMDC01,CN=Servers,CN=VNHCM,CN=Sites,CN=Configuration,DC=dynea,DC=net
DSA transport addr
ee15dc9e-173b-4a0d-b5c4-a823b5f6063a._msdcs.dynea.net
REPLICATION-RECEIVED LATENCY WARNING
FIALEDC01: Current time is 2009-06-05 00:15:14.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
[Replications Check,SGSGDC01] A recent replication attempt failed:
From CHGUADC02 to SGSGDC01
Naming Context: DC=dynea,DC=net
The replication generated an error (1818):
The remote procedure call was cancelled.
The failure occurred at 2009-06-04 23:48:25.
The last success occurred at 2009-05-14 03:25:19.
826 failures have occurred since the last success.
REPLICATION LATENCY WARNING
SGSGDC01: A long-running replication operation is in progress
The job has been executing for 41 minutes and 22 seconds.
Replication of new changes along this path will be delayed.
Error: Higher priority replications are being blocked
Enqueued 2009-06-04 23:58:10 at priority 90
Op: SYNC FROM SOURCE
NC DC=dynea,DC=net
DSADN CN=NTDS
Settings,CN=CHGUADC02,CN=Servers,CN=CHGUA,CN=Sites,CN=Configuration,DC=dynea,DC=net
DSA transport addr
842084b0-167a-402e-a1be-6f4390b056ab._msdcs.dynea.net
REPLICATION-RECEIVED LATENCY WARNING
SGSGDC01: Current time is 2009-06-05 00:15:16.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/05/2009 00:48:15
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/05/2009 00:48:15
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/05/2009 00:48:15
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/05/2009 00:48:15
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/05/2009 00:48:15
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/05/2009 00:48:15
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/05/2009 00:48:15
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/05/2009 00:48:15
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/05/2009 00:48:15
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/05/2009 00:48:15
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/05/2009 00:48:15
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/05/2009 00:48:15
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/05/2009 00:48:15
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/05/2009 00:48:15
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/05/2009 00:48:15
Event String: The Knowledge Consistency Checker (KCC) was
......................... SGSGDC01 failed test kccevent
REPLICATION-RECEIVED LATENCY WARNING
ATKREDC01: Current time is 2009-06-05 00:15:19.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
FIALEDC04: Current time is 2009-06-05 00:15:20.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
THHATDC01: Current time is 2009-06-05 00:15:22.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
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.
......................... THHATDC01 failed test frsevent
REPLICATION-RECEIVED LATENCY WARNING
MANSMDC01: Current time is 2009-06-05 00:15:29.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
THBANDC01: Current time is 2009-06-05 00:15:34.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
VNHCMDC01: Current time is 2009-06-05 00:15:40.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
REPLICATION-RECEIVED LATENCY WARNING
FIHAMDC01: Current time is 2009-06-05 00:15:50.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
DEERKDC01: Current time is 2009-06-05 00:15:50.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
CHSHADC01: Current time is 2009-06-05 00:15:54.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
HUKAZDC02: Current time is 2009-06-05 00:15:58.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
FIKITDC01: Current time is 2009-06-05 00:15:59.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
NOLILDC01: Current time is 2009-06-05 00:15:59.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
BEGENDC01: Current time is 2009-06-05 00:16:00.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
FRBREDC01: Current time is 2009-06-05 00:16:01.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
Authoritative attribute lastLogonTimestamp on CHSHADC01
(writeable)
usnLocalChange = 2750096
LastOriginatingDsa = FIDHCDC01
usnOriginatingChange = 59673582
timeLastOriginatingChange = 2009-06-04 13:55:47
VersionLastOriginatingChange = 72
Out-of-date attribute lastLogonTimestamp on FIDSRDC01 (writeable)
usnLocalChange = 217893
LastOriginatingDsa = FIDHCDC01
usnOriginatingChange = 50901560
timeLastOriginatingChange = 2009-05-25 11:53:58
VersionLastOriginatingChange = 71
......................... FRBREDC01 failed test ObjectsReplicated
REPLICATION-RECEIVED LATENCY WARNING
NLDELDC01: Current time is 2009-06-05 00:16:02.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
CHBEIDC01: Current time is 2009-06-05 00:16:05.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
CHGUADC02: Current time is 2009-06-05 00:16:13.
DC=dynea,DC=net
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
NZNEPDC04: Current time is 2009-06-05 00:16:22.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
IECORDC02: Current time is 2009-06-05 00:16:27.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
PLTRZDC01: Current time is 2009-06-05 00:16:28.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
SGSGDC02: Current time is 2009-06-05 00:16:30.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
INJAKDC01: Current time is 2009-06-05 00:16:34.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
REPLICATION-RECEIVED LATENCY WARNING
INMEDDC02: Current time is 2009-06-05 00:16:41.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
Authoritative attribute lastLogonTimestamp on CHSHADC01
(writeable)
usnLocalChange = 2750955
LastOriginatingDsa = FIDHCDC01
usnOriginatingChange = 59676178
timeLastOriginatingChange = 2009-06-04 17:25:37
VersionLastOriginatingChange = 62
Out-of-date attribute lastLogonTimestamp on FIDSRDC01 (writeable)
usnLocalChange = 217941
LastOriginatingDsa = FIDHCDC01
usnOriginatingChange = 50995560
timeLastOriginatingChange = 2009-05-25 14:02:06
VersionLastOriginatingChange = 61
......................... INMEDDC02 failed test ObjectsReplicated
REPLICATION-RECEIVED LATENCY WARNING
UKAYCDC01: Current time is 2009-06-05 00:16:46.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
Authoritative attribute lastLogonTimestamp on CHSHADC01
(writeable)
usnLocalChange = 2749787
LastOriginatingDsa = FIDHCDC01
usnOriginatingChange = 59672396
timeLastOriginatingChange = 2009-06-04 12:20:12
VersionLastOriginatingChange = 46
Out-of-date attribute lastLogonTimestamp on FIDSRDC01 (writeable)
usnLocalChange = 217894
LastOriginatingDsa = FIDHCDC01
usnOriginatingChange = 50908973
timeLastOriginatingChange = 2009-05-25 12:04:15
VersionLastOriginatingChange = 45
......................... UKAYCDC01 failed test ObjectsReplicated
REPLICATION-RECEIVED LATENCY WARNING
FIALEDC03: Current time is 2009-06-05 00:16:47.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
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.
......................... FIALEDC03 failed test frsevent
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/05/2009 01:30:37
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/05/2009 01:30:37
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/05/2009 01:30:37
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/05/2009 01:30:37
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/05/2009 01:30:37
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/05/2009 01:30:37
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/05/2009 01:30:37
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/05/2009 01:30:37
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/05/2009 01:30:37
Event String: The Knowledge Consistency Checker (KCC) was
An Warning Event occured. EventID: 0x8000061E
Time Generated: 06/05/2009 01:30:37
Event String: All domain controllers in the following site that
An Error Event occured. EventID: 0xC000051F
Time Generated: 06/05/2009 01:30:37
Event String: The Knowledge Consistency Checker (KCC) has
An Warning Event occured. EventID: 0x80000749
Time Generated: 06/05/2009 01:30:37
Event String: The Knowledge Consistency Checker (KCC) was

......................... FIALEDC03 failed test kccevent
REPLICATION-RECEIVED LATENCY WARNING
UKMOLDC02: Current time is 2009-06-05 00:16:47.
DC=dynea,DC=net
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
[Replications Check,FIDSRDC01] No replication recently attempted:
From FIALEDC03 to FIDSRDC01
Naming Context: CN=Schema,CN=Configuration,DC=dynea,DC=net
The last attempt occurred at 2009-06-04 02:53:23 (about 22 hours
ago).
[Replications Check,FIDSRDC01] No replication recently attempted:
From FIDHCDC01 to FIDSRDC01
Naming Context: CN=Schema,CN=Configuration,DC=dynea,DC=net
The last attempt occurred at 2009-06-04 18:55:57 (about 6 hours
ago).
[Replications Check,FIDSRDC01] No replication recently attempted:
From FIALEDC03 to FIDSRDC01
Naming Context: CN=Configuration,DC=dynea,DC=net
The last attempt occurred at 2009-06-04 07:59:22 (about 17 hours
ago).
[Replications Check,FIDSRDC01] No replication recently attempted:
From FIDHCDC01 to FIDSRDC01
Naming Context: CN=Configuration,DC=dynea,DC=net
The last attempt occurred at 2009-06-04 12:59:45 (about 12 hours
ago).
[Replications Check,FIDSRDC01] No replication recently attempted:
From FIALEDC03 to FIDSRDC01
Naming Context: DC=dynea,DC=net
The last attempt occurred at 2009-06-04 09:34:58 (about 16 hours
ago).
[Replications Check,FIDSRDC01] No replication recently attempted:
From FIDHCDC01 to FIDSRDC01
Naming Context: DC=dynea,DC=net
The last attempt occurred at 2009-06-04 09:35:48 (about 16 hours
ago).
[Replications Check,FIDSRDC01] No replication recently attempted:
From FIALEDC03 to FIDSRDC01
Naming Context: DC=eu,DC=dynea,DC=net
The last attempt occurred at 2009-06-04 02:53:23 (about 22 hours
ago).
REPLICATION-RECEIVED LATENCY WARNING
FIDSRDC01: Current time is 2009-06-05 00:16:48.
DC=dynea,DC=net
Last replication recieved from BEGENDC01 at 2009-06-04
09:22:58.
Last replication recieved from SGSGDC02 at 2009-06-04 09:34:54.
Last replication recieved from UKAYCDC01 at 2009-06-04
09:23:00.
Last replication recieved from DEERKDC01 at 2009-06-04
09:22:57.
Last replication recieved from HUKAZDC02 at 2009-06-04
09:22:57.
Last replication recieved from NZNEPDC04 at 2009-06-04
09:22:55.
Last replication recieved from PLTRZDC01 at 2009-06-04
09:22:59.
Last replication recieved from NOLILDC01 at 2009-06-04
09:22:57.
Last replication recieved from CHGUADC02 at 2009-05-14
03:24:34.
Last replication recieved from FIHAMDC01 at 2009-06-04
09:22:56.
Last replication recieved from FIALEDC03 at 2009-06-04
09:34:56.
Last replication recieved from THHATDC01 at 2009-06-04
09:22:56.
Last replication recieved from CHSHADC01 at 2009-06-04
09:22:57.
Last replication recieved from UKMOLDC02 at 2009-06-04
09:23:00.
Last replication recieved from VNHCMDC01 at 2009-05-08
03:52:59.
Last replication recieved from SGSGDC01 at 2009-06-04 09:34:58.
Last replication recieved from IECORDC02 at 2009-06-04
09:22:58.
Last replication recieved from FIKITDC01 at 2009-06-04
09:22:57.
Last replication recieved from ATKREDC01 at 2009-06-04
09:22:56.
Last replication recieved from MANSMDC01 at 2009-06-04
09:22:49.
Last replication recieved from FRBREDC01 at 2009-06-04
09:22:58.
Last replication recieved from NLDELDC01 at 2009-06-04
09:22:58.
Last replication recieved from INJAKDC01 at 2009-06-04
09:22:59.
Last replication recieved from FIALEDC01 at 2009-06-04
09:34:55.
Last replication recieved from THBANDC01 at 2009-06-04
09:31:40.
Last replication recieved from FIDHCDC01 at 2009-06-04
09:35:48.
Last replication recieved from CHBEIDC01 at 2009-06-04
08:49:46.
Last replication recieved from FIDHCDC02 at 2009-06-04
09:35:45.
Last replication recieved from INMEDDC02 at 2009-06-04
08:52:39.
*Warning: Remote bridgehead VNHCM\VNHCMDC01 is not eligible as a
bridgehead due to too many failures. Replication may be disrupted
into the local site FIALE.
*Warning: Remote bridgehead CHGUA\CHGUADC02 is not eligible as a
bridgehead due to too many failures. Replication may be disrupted
into the local site SGSG.


Best regards,

Toni
Toni Rantanen
2009-06-05 11:17:01 UTC
Permalink
Hi All,

I just would like to add to my previous posting that issue with file copy
from VNHCMDC01 to a server in same LAN happens also with CHGUADC02. I have
even tested to copy 91 KB file (with Windows file share) from CHGUADC02 an
other server in same LAN and it fails with same error message "Cannot
copy [filename]: The specified network name is no longer available".

Could this be something to cause replication issues as well?

More difficult question, how to fix the problem? :) I have tried to search
solutions for this issue but haven't been able to find one yet.

Best regards,

Toni
Ace Fekay [Microsoft Certified Trainer]
2009-06-05 15:08:23 UTC
Permalink
Post by Toni Rantanen
Hi All,
I just would like to add to my previous posting that issue with file copy
from VNHCMDC01 to a server in same LAN happens also with CHGUADC02. I have
even tested to copy 91 KB file (with Windows file share) from CHGUADC02 an
other server in same LAN and it fails with same error message "Cannot
copy [filename]: The specified network name is no longer available".
Could this be something to cause replication issues as well?
More difficult question, how to fix the problem? :) I have tried to search
solutions for this issue but haven't been able to find one yet.
Best regards,
Toni
Absolutely it will cause problems with replication.

Ok, so this brings up some questions:
Are there any services disabled?
What if any, were the most recent changes, such as insallations, service
packs, updates, etc?
Any local firewall or 3rd party AV or security apps installed?
IPSec policy running?

Ace
Toni Rantanen
2009-06-05 19:33:02 UTC
Permalink
Post by Ace Fekay [Microsoft Certified Trainer]
Absolutely it will cause problems with replication.
Are there any services disabled?
What if any, were the most recent changes, such as insallations, service
packs, updates, etc?
Any local firewall or 3rd party AV or security apps installed?
IPSec policy running?
Ace
Hi Ace,

I have checked services on CHGUADC02 and VNHCMDC01 (and just in case on
FIALEDC01 and SGSGDC01 too) and there is no services disabled. I compared
service list to a working DC service list and it was identical. All our DC's
are almost identical hardware.

I doubt that any recent changes have caused. These servers have been on SP2
for quite a long time so that definetely is not a problem. Latest changes to
both servers were Windows updates installation on last month but CHGUADC02
replication problems have started couple of days before update installation
so this is not a problem as well.

There is no local firewall running on the DC's. 3rd party AV is installed
and I have tested to unload it but the problem still occurs. This issue is
not caused by AV.

We are not using IPSec at all. So this isn't either causing the issue.

Do you have any other ideas on how to proceed troubleshooting?

Best regards,

Toni
Ace Fekay [Microsoft Certified Trainer]
2009-06-06 01:45:02 UTC
Permalink
Post by Toni Rantanen
Post by Ace Fekay [Microsoft Certified Trainer]
Absolutely it will cause problems with replication.
Are there any services disabled?
What if any, were the most recent changes, such as insallations, service
packs, updates, etc?
Any local firewall or 3rd party AV or security apps installed?
IPSec policy running?
Ace
Hi Ace,
I have checked services on CHGUADC02 and VNHCMDC01 (and just in case on
FIALEDC01 and SGSGDC01 too) and there is no services disabled. I compared
service list to a working DC service list and it was identical. All our DC's
are almost identical hardware.
I doubt that any recent changes have caused. These servers have been on SP2
for quite a long time so that definetely is not a problem. Latest changes to
both servers were Windows updates installation on last month but CHGUADC02
replication problems have started couple of days before update
installation
so this is not a problem as well.
There is no local firewall running on the DC's. 3rd party AV is installed
and I have tested to unload it but the problem still occurs. This issue is
not caused by AV.
We are not using IPSec at all. So this isn't either causing the issue.
Do you have any other ideas on how to proceed troubleshooting?
Best regards,
Toni
Toni,

Read the following and let me know what you think...
======================================================================================================
======================================================================================================
Slow file transfer and connectivity with Windows 2003 SP2, Windows 2008, SBS
2003 SP2 and SBS 2008, and Vista
System Error 64
System Error 53
Shares disconnect after a server has been running for a period of time such
as a couple of weeks and a restart fixes it temporarily.


This may be due to the new RSS TCP Chimney Offload feature enabled on 2003
SP2 and newer servers.

TCP Chimney Offload overview:

TCP Chimney Offload is a networking technology that helps transfer the
workload from the CPU to a network adapter during network data transfer. In
Windows Server 2008, TCP Chimney Offload enables the Windows networking
subsystem to offload the processing of a TCP/IP connection to a network
adapter that includes special support for TCP/IP offload processing.

TCP Chimney Offload is available in all versions of Windows Server 2008 and
Windows Vista. Both TCP/IPv4 connections and TCP/IPv6 connections can be
offloaded if the network adapter supports this feature.


Two ways to handle it.
1. Disable RSS using the netsh command (preferred)
2. Disable RSS in the registry


1. Disable RSS using the netsh command:
(From http://support.microsoft.com/kb/951037)

netsh interface tcp set global rss=disabled
netsh interface tcp set global autotuninglevel=disabled
Reboot the server

2. Disable RSS in the Registry
(From http://support.microsoft.com/kb/927695):

Add a DWORD registry key value for
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableRSS
and setting it to 0. A reboot is required to make the value go in to
effect.
Set DisableTaskOffload in the Registry
Use the steps in KB 904946 to create a DWORD value for
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DisableTaskOffload
and set it to 1.
A reboot is required to make this value go in to effect.


More info on the subject...

Information about the TCP Chimney Offload, Receive Side Scaling, and Network
Direct Memory Access features in Windows Server 2008
http://support.microsoft.com/kb/951037

You cannot host TCP connections when Receive Side Scaling is enabled in
Windows Server 2003 with Service Pack 2
http://support.microsoft.com/?id=927695

Vista slow after SP2 installed on Windows 2003 Server (SBS or non-SBS) or
using Windows 2008?
http://msmvps.com/blogs/bradley/archive/2007/04/04/vista-slow-after-sp2-installed.aspx

Windows 2003 service pack 2 known issues on Small Business Server 2003
http://support.microsoft.com/kb/555912/en-us

Susan Bradley: Vista slow after SP2 installed?
http://msmvps.com/blogs/bradley/archive/2007/04/04/vista-slow-after-sp2-installed.aspx

You experience intermittent communication failure between computers that are
running Windows XP or Windows Server 2003
http://support.microsoft.com/?id=904946

Common Networking Issues After Applying Windows Server 2003 SP2 on SBS:
http://blogs.technet.com/sbs/archive/2007/04/24/common-networking-issues-after-applying-windows-server-2003-sp2-on-sbs.aspx
======================================================================================================
======================================================================================================

Ace
Toni Rantanen
2009-06-09 13:38:02 UTC
Permalink
Hi Ace,

And sorry for my late reply.

First of all, my issue has been solved! The fix was to create a DWORD value
for
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DisableTaskOffload
and set it to 1 on servers VNHCMDC01 and CHGUADC02. EnableRSS registry
setting with value 0 was already in place.

Thank you Ace very much for this tip!!

We are having about 25 domain controllers with all of these having almost
exactly same hardware and OS + patch level. Do you have any idea why only
these two servers were having this issue? What is your recommendation, should
I implement this same setting on other DC's as well (even if there is no
replication issues on the domain currently)?

Best regards,

Toni
Ace Fekay [Microsoft Certified Trainer]
2009-06-09 13:46:13 UTC
Permalink
Post by Toni Rantanen
Hi Ace,
And sorry for my late reply.
First of all, my issue has been solved! The fix was to create a DWORD value
for
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\DisableTaskOffload
and set it to 1 on servers VNHCMDC01 and CHGUADC02. EnableRSS registry
setting with value 0 was already in place.
Thank you Ace very much for this tip!!
We are having about 25 domain controllers with all of these having almost
exactly same hardware and OS + patch level. Do you have any idea why only
these two servers were having this issue? What is your recommendation, should
I implement this same setting on other DC's as well (even if there is no
replication issues on the domain currently)?
Best regards,
Toni
Good to hear it worked! I don;t know why just the two servers, but I would
recommend making the changes consistent across the board on all DCs. It
keeps consistency with settings and builds on each DC and your change
managment documentation, as well to insure there are no other prolems that
may result from this issue in the future.

Cheers!

Ace
Ace Fekay [Microsoft Certified Trainer]
2009-06-04 05:06:49 UTC
Permalink
Post by Ace Fekay [Microsoft Certified Trainer]
Hi Toni,
Lot's of info. I had to actually draw it out on paper to get a better
'view' of it.
The ping times between Sites FIALE and VNHCM, 421.8/930.7/2403.9 ms, are
kind of high. Even the lowest one at 421 is kind of high, especially if
that is the minimal one. That would explain RPC failing. What other type
of traffic is on this line?
Which site is the central site?
How are the sites connected? In a mesh, or do you have it as a hub and
spoke?
Ace
Also, forgot to ask, why are those additional search suffixes on the DCs?

Ace

Loading...