exchange slowing down, outlook freeze
exchange slowing down, outlook freeze. Sometimes outlook reports that he could not connect to the exchange server. All exchange services are running!?
Also check the RPC dialogue box on the client end for the server name.
Is it showing your DC name or Exchange server Name?
>>>> veera.
Is it showing your DC name or Exchange server Name?
>>>> veera.
ASKER
It is like my two domain controllers are crashing
I get this errors in the event log > application log:
LDAP Bind was unsuccessful on directory dc.offices.netmedia.hr for distinguished name ''. Directory returned error:[0x51] Server Down.
Process INETINFO.EXE (PID=424). Topology Discovery failed, error 0xffffffff.
Process MAD.EXE (PID=3724). All Global Catalog Servers in use are not responding:
primari domain controller
sec domain controller
Background thread FDoBuildCatalog halted on database "First Storage Group\Mailbox Store (EXCHANGE)" due to error code 0x80004005.
I get this errors in the event log > application log:
LDAP Bind was unsuccessful on directory dc.offices.netmedia.hr for distinguished name ''. Directory returned error:[0x51] Server Down.
Process INETINFO.EXE (PID=424). Topology Discovery failed, error 0xffffffff.
Process MAD.EXE (PID=3724). All Global Catalog Servers in use are not responding:
primari domain controller
sec domain controller
Background thread FDoBuildCatalog halted on database "First Storage Group\Mailbox Store (EXCHANGE)" due to error code 0x80004005.
No, Hopefully It is not DC issue. To make sure check the health of your DCs through Event Viewer.
It should be your network issue. We faced the same issue for 6 months. Actually our SMTP connectors go down frequently. Then randomly we used to get the same event what you mentioned here. Finally we traced it to be a network (LAN) issue.
Check your cables running between switches to DCs and Exchange servers. If it is connected to a Layer 3/ layer 2 switch, try to change the switch port.
>>>> Veera.
It should be your network issue. We faced the same issue for 6 months. Actually our SMTP connectors go down frequently. Then randomly we used to get the same event what you mentioned here. Finally we traced it to be a network (LAN) issue.
Check your cables running between switches to DCs and Exchange servers. If it is connected to a Layer 3/ layer 2 switch, try to change the switch port.
>>>> Veera.
ASKER
I get this event log in event viewer > application
Process MAD.EXE (PID=2816). All Domain Controller Servers in use are not responding:
primary domain controller
secondary domain controller
Process MAD.EXE (PID=2816). All Domain Controller Servers in use are not responding:
primary domain controller
secondary domain controller
ASKER
i run dcdiag and netdiag both gave error
Can you post those DCDiag and NetDiad results?
>>>> Veera.
>>>> Veera.
ASKER
this is what i run on my dc controller
C:\Documents and Settings\davy>dcdiag /v
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine dc, is a DC.
* Connecting to directory service on server dc.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... DC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC
Starting test: Replications
* Replications Check
* Replication Latency Check
CN=Schema,CN=Configuration
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
CN=Configuration,DC=office
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
DC=offices,DC=netmedia,DC=
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
* Replication Site Latency Check
......................... DC passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC DC.
* Security Permissions Check for
DC=ForestDnsZones,DC=offic
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=offic
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=office
(Configuration,Version 2)
* Security Permissions Check for
DC=offices,DC=netmedia,DC=
(Domain,Version 2)
......................... DC passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\DC\netlogon
Verified share \\DC\sysvol
......................... DC passed test NetLogons
Starting test: Advertising
The DC DC is advertising itself as a DC and having a DS.
The DC DC is advertising as an LDAP server
The DC DC is advertising as having a writeable directory
The DC DC is advertising as a Key Distribution Center
The DC DC is advertising as a time server
The DS DC is advertising as a GC.
......................... DC passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=DC,CN=Servers,
Site-Name,CN=Sites,CN=Conf
Role Domain Owner = CN=NTDS Settings,CN=DC,CN=Servers,
Site-Name,CN=Sites,CN=Conf
Role PDC Owner = CN=NTDS Settings,CN=DC,CN=Servers,
e-Name,CN=Sites,CN=Configu
Role Rid Owner = CN=NTDS Settings,CN=DC,CN=Servers,
e-Name,CN=Sites,CN=Configu
Role Infrastructure Update Owner = CN=NTDS Settings,CN=DC,CN=Servers,
=Default-First-Site-Name,C
......................... DC passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 5105 to 1073741823
* dc.offices.netmedia.hr is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 2605 to 3104
* rIDPreviousAllocationPool is 2605 to 3104
* rIDNextRID: 2848
......................... DC passed test RidManager
Starting test: MachineAccount
Checking machine account for DC DC on DC DC.
* SPN found :LDAP/dc.offices.netmedia.
* SPN found :LDAP/dc.offices.netmedia.
* SPN found :LDAP/DC
* SPN found :LDAP/dc.offices.netmedia.
* SPN found :LDAP/917e9ea7-84ba-4fa9-b
etmedia.hr
* SPN found :E3514235-4B06-11D1-AB04-0
a5-9e9797813b38/offices.ne
* SPN found :HOST/dc.offices.netmedia.
* SPN found :HOST/dc.offices.netmedia.
* SPN found :HOST/DC
* SPN found :HOST/dc.offices.netmedia.
* SPN found :GC/dc.offices.netmedia.hr
......................... DC passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... DC passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
DC is in domain DC=offices,DC=netmedia,DC=
Checking for CN=DC,OU=Domain Controllers,DC=offices,DC=
n domain DC=offices,DC=netmedia,DC=
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=DC,CN=Servers,
me,CN=Sites,CN=Configurati
tion,DC=offices,DC=netmedi
Object is up-to-date on all servers.
......................... DC passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... DC passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
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.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 12/13/2007 08:10:46
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800034C5
Time Generated: 12/13/2007 08:15:30
(Event String could not be retrieved)
......................... DC failed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minut
es.
......................... DC passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0x00000457
Time Generated: 12/13/2007 14:24:22
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 12/13/2007 14:24:28
(Event String could not be retrieved)
......................... DC failed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=DC,OU=Domain Controllers,DC=offices,DC=
on
CN=DC,CN=Servers,CN=Defaul
C=offices,DC=netmedia,DC=h
are correct.
The system object reference (frsComputerReferenceBL)
CN=TEST002,CN=Domain System Volume (SYSVOL share),CN=File Replication S
ervice,CN=System,DC=office
and backlink on
CN=DC,OU=Domain Controllers,DC=offices,DC=
The system object reference (serverReferenceBL)
CN=TEST002,CN=Domain System Volume (SYSVOL share),CN=File Replication S
ervice,CN=System,DC=office
and backlink on
CN=NTDS Settings,CN=DC,CN=Servers,
N=Configuration,DC=offices
are correct.
......................... DC passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError
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 : offices
Starting test: CrossRefValidation
......................... offices passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... offices passed test CheckSDRefDom
Running enterprise tests on : offices.netmedia.hr
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... offices.netmedia.hr passed test Intersite
Starting test: FsmoCheck
GC Name: \\dc.offices.netmedia.hr
Locator Flags: 0xe00003fd
PDC Name: \\dc.offices.netmedia.hr
Locator Flags: 0xe00003fd
Time Server Name: \\dc.offices.netmedia.hr
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\dc.offices.netmedia.hr
Locator Flags: 0xe00003fd
KDC Name: \\dc.offices.netmedia.hr
Locator Flags: 0xe00003fd
......................... offices.netmedia.hr passed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS
C:\Documents and Settings\davy>
C:\Documents and Settings\davy>dcdiag /v
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine dc, is a DC.
* Connecting to directory service on server dc.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 2 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DC
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... DC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DC
Starting test: Replications
* Replications Check
* Replication Latency Check
CN=Schema,CN=Configuration
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
CN=Configuration,DC=office
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
DC=offices,DC=netmedia,DC=
Latency information for 4 entries in the vector were ignored.
4 were retired Invocations. 0 were either: read-only replicas
and are not verifiably latent, or dc's no longer replicating this nc. 0 had no
latency information (Win2K DC).
* Replication Site Latency Check
......................... DC passed test Replications
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC DC.
* Security Permissions Check for
DC=ForestDnsZones,DC=offic
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=offic
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=office
(Configuration,Version 2)
* Security Permissions Check for
DC=offices,DC=netmedia,DC=
(Domain,Version 2)
......................... DC passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\DC\netlogon
Verified share \\DC\sysvol
......................... DC passed test NetLogons
Starting test: Advertising
The DC DC is advertising itself as a DC and having a DS.
The DC DC is advertising as an LDAP server
The DC DC is advertising as having a writeable directory
The DC DC is advertising as a Key Distribution Center
The DC DC is advertising as a time server
The DS DC is advertising as a GC.
......................... DC passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS Settings,CN=DC,CN=Servers,
Site-Name,CN=Sites,CN=Conf
Role Domain Owner = CN=NTDS Settings,CN=DC,CN=Servers,
Site-Name,CN=Sites,CN=Conf
Role PDC Owner = CN=NTDS Settings,CN=DC,CN=Servers,
e-Name,CN=Sites,CN=Configu
Role Rid Owner = CN=NTDS Settings,CN=DC,CN=Servers,
e-Name,CN=Sites,CN=Configu
Role Infrastructure Update Owner = CN=NTDS Settings,CN=DC,CN=Servers,
=Default-First-Site-Name,C
......................... DC passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 5105 to 1073741823
* dc.offices.netmedia.hr is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 2605 to 3104
* rIDPreviousAllocationPool is 2605 to 3104
* rIDNextRID: 2848
......................... DC passed test RidManager
Starting test: MachineAccount
Checking machine account for DC DC on DC DC.
* SPN found :LDAP/dc.offices.netmedia.
* SPN found :LDAP/dc.offices.netmedia.
* SPN found :LDAP/DC
* SPN found :LDAP/dc.offices.netmedia.
* SPN found :LDAP/917e9ea7-84ba-4fa9-b
etmedia.hr
* SPN found :E3514235-4B06-11D1-AB04-0
a5-9e9797813b38/offices.ne
* SPN found :HOST/dc.offices.netmedia.
* SPN found :HOST/dc.offices.netmedia.
* SPN found :HOST/DC
* SPN found :HOST/dc.offices.netmedia.
* SPN found :GC/dc.offices.netmedia.hr
......................... DC passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... DC passed test Services
Test omitted by user request: OutboundSecureChannels
Starting test: ObjectsReplicated
DC is in domain DC=offices,DC=netmedia,DC=
Checking for CN=DC,OU=Domain Controllers,DC=offices,DC=
n domain DC=offices,DC=netmedia,DC=
Object is up-to-date on all servers.
Checking for CN=NTDS Settings,CN=DC,CN=Servers,
me,CN=Sites,CN=Configurati
tion,DC=offices,DC=netmedi
Object is up-to-date on all servers.
......................... DC passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... DC passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
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.
An Warning Event occured. EventID: 0x800034C4
Time Generated: 12/13/2007 08:10:46
(Event String could not be retrieved)
An Warning Event occured. EventID: 0x800034C5
Time Generated: 12/13/2007 08:15:30
(Event String could not be retrieved)
......................... DC failed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minut
es.
......................... DC passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0x00000457
Time Generated: 12/13/2007 14:24:22
(Event String could not be retrieved)
An Error Event occured. EventID: 0x00000457
Time Generated: 12/13/2007 14:24:28
(Event String could not be retrieved)
......................... DC failed test systemlog
Test omitted by user request: VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference)
CN=DC,OU=Domain Controllers,DC=offices,DC=
on
CN=DC,CN=Servers,CN=Defaul
C=offices,DC=netmedia,DC=h
are correct.
The system object reference (frsComputerReferenceBL)
CN=TEST002,CN=Domain System Volume (SYSVOL share),CN=File Replication S
ervice,CN=System,DC=office
and backlink on
CN=DC,OU=Domain Controllers,DC=offices,DC=
The system object reference (serverReferenceBL)
CN=TEST002,CN=Domain System Volume (SYSVOL share),CN=File Replication S
ervice,CN=System,DC=office
and backlink on
CN=NTDS Settings,CN=DC,CN=Servers,
N=Configuration,DC=offices
are correct.
......................... DC passed test VerifyReferences
Test omitted by user request: VerifyEnterpriseReferences
Test omitted by user request: CheckSecurityError
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 : offices
Starting test: CrossRefValidation
......................... offices passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... offices passed test CheckSDRefDom
Running enterprise tests on : offices.netmedia.hr
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... offices.netmedia.hr passed test Intersite
Starting test: FsmoCheck
GC Name: \\dc.offices.netmedia.hr
Locator Flags: 0xe00003fd
PDC Name: \\dc.offices.netmedia.hr
Locator Flags: 0xe00003fd
Time Server Name: \\dc.offices.netmedia.hr
Locator Flags: 0xe00003fd
Preferred Time Server Name: \\dc.offices.netmedia.hr
Locator Flags: 0xe00003fd
KDC Name: \\dc.offices.netmedia.hr
Locator Flags: 0xe00003fd
......................... offices.netmedia.hr passed test FsmoCheck
Test omitted by user request: DNS
Test omitted by user request: DNS
C:\Documents and Settings\davy>
ASKER
C:\Documents and Settings\davy>netdiag
..........................
Computer Name: DC
DNS Host Name: dc.offices.netmedia.hr
System info : Windows 2000 Server (Build 3790)
Processor : x86 Family 6 Model 8 Stepping 6, GenuineIntel
List of installed hotfixes :
KB890046
KB893756
KB896358
KB896422
KB896424
KB896428
KB896727
KB899587
KB899588
KB899589
KB899591
KB900725
KB901017
KB901214
KB902400
KB903235
KB904706
KB904942
KB905414
KB908519
KB908531
KB910437
KB911280
KB911562
KB911564
KB911567
KB911927
KB912919
KB914388
KB914389
KB917159
KB917344
KB917422
KB917537
KB917734
KB917953
KB918439
KB918899
KB920214
KB920670
KB920683
KB921398
KB921883
KB922616
Q147222
Netcard queries test . . . . . . . : Passed
Per interface results:
Adapter : Local Area Connection
Netcard queries test . . . : Passed
Host Name. . . . . . . . . : dc
IP Address . . . . . . . . : 192.168.0.4
Subnet Mask. . . . . . . . : 255.255.255.0
Default Gateway. . . . . . : 192.168.0.10
Dns Servers. . . . . . . . : 192.168.0.4
192.168.0.80
AutoConfiguration results. . . . . . : Passed
Default gateway test . . . : Passed
NetBT name test. . . . . . : Passed
WINS service test. . . . . : Skipped
There are no WINS servers configured for this interface.
Global results:
Domain membership test . . . . . . : Passed
NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{3ED88272-897B
1 NetBt transport currently configured.
Autonet address test . . . . . . . : Passed
IP loopback ping test. . . . . . . : Passed
Default gateway test . . . . . . . : Passed
NetBT name test. . . . . . . . . . : Passed
Winsock test . . . . . . . . . . . : Passed
DNS test . . . . . . . . . . . . . : Passed
PASS - All the DNS entries for DC are registered on DNS server '192.168.0.4'
and other DCs also have some of the names registered.
[WARNING] The DNS entries for this DC cannot be verified right now on DNS
server 192.168.0.80, ERROR_TIMEOUT.
Redir and Browser test . . . . . . : Passed
List of NetBt transports currently bound to the Redir
NetBT_Tcpip_{3ED88272-897B
The redir is bound to 1 NetBt transport.
List of NetBt transports currently bound to the browser
NetBT_Tcpip_{3ED88272-897B
The browser is bound to 1 NetBt transport.
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Passed
Trust relationship test. . . . . . : Skipped
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
C:\Documents and Settings\davy>
Did you run this on both DCs?
What is the event ID associated with this issue?
>>>> veera.
What is the event ID associated with this issue?
>>>> veera.
ASKER
Here are the errors on the primary domain controller:
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6525
Date: 13.12.2007
Time: 8:35:08
User: N/A
Computer: DC
Description:
A zone transfer request for the secondary zone colocation.mplus.net was refused by the master DNS server at 192.168.254.100. Check the zone at the master server 192.168.254.100 to verify that zone transfer is enabled to this server. To do so, use the DNS console, and select master server 192.168.254.100 as the applicable server, then in secondary zone colocation.mplus.net Properties, view the settings on the Zone Transfers tab. Based on the settings you choose, make any configuration adjustments there (or possibly in the Name Servers tab) so that a zone transfer can be made to this server.
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6525
Date: 13.12.2007
Time: 8:35:08
User: N/A
Computer: DC
Description:
A zone transfer request for the secondary zone colocation.mplus.net was refused by the master DNS server at 192.168.254.100. Check the zone at the master server 192.168.254.100 to verify that zone transfer is enabled to this server. To do so, use the DNS console, and select master server 192.168.254.100 as the applicable server, then in secondary zone colocation.mplus.net Properties, view the settings on the Zone Transfers tab. Based on the settings you choose, make any configuration adjustments there (or possibly in the Name Servers tab) so that a zone transfer can be made to this server.
ASKER
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6525
Date: 13.12.2007
Time: 8:35:08
User: N/A
Computer: DC
Description:
A zone transfer request for the secondary zone colocation.mplus.net was refused by the master DNS server at 192.168.254.100. Check the zone at the master server 192.168.254.100 to verify that zone transfer is enabled to this server. To do so, use the DNS console, and select master server 192.168.254.100 as the applicable server, then in secondary zone colocation.mplus.net Properties, view the settings on the Zone Transfers tab. Based on the settings you choose, make any configuration adjustments there (or possibly in the Name Servers tab) so that a zone transfer can be made to this server.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Source: DNS
Event Category: None
Event ID: 6525
Date: 13.12.2007
Time: 8:35:08
User: N/A
Computer: DC
Description:
A zone transfer request for the secondary zone colocation.mplus.net was refused by the master DNS server at 192.168.254.100. Check the zone at the master server 192.168.254.100 to verify that zone transfer is enabled to this server. To do so, use the DNS console, and select master server 192.168.254.100 as the applicable server, then in secondary zone colocation.mplus.net Properties, view the settings on the Zone Transfers tab. Based on the settings you choose, make any configuration adjustments there (or possibly in the Name Servers tab) so that a zone transfer can be made to this server.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Check this:
==========================
To verify that the primary DNS server is configured to allow zone transfers from the secondary DNS server
1. On the primary DNS server, click Start, point to All Programs, click Administrative Tools, and then click DNS.
2. In the console tree, double-click the DNS server.
3. In the console tree, double-click Forward Lookup Zones or Reverse Lookup Zones, as applicable.
4. Right-click the zone, click Properties, and then click the Zone Transfers tab.
5. Ensure that the Allow zone transfers check box is selected.
If zone transfer fails with Event ID 6525 Zone transfer for secondary zone <zone_name> refused by master server and the master server allows dynamic updates for the zone, these failures are due to the zone transfer throttling mechanism, and they are expected. This mechanism limits the number of zone transfers to allow regular dynamic updates to take place.
http://207.46.196.114/windowsserver/en/library/547be1bb-1a55-465b-a39c-e326d31e1cf71033.mspx?mfr=true
>>>> Veera.
==========================
To verify that the primary DNS server is configured to allow zone transfers from the secondary DNS server
1. On the primary DNS server, click Start, point to All Programs, click Administrative Tools, and then click DNS.
2. In the console tree, double-click the DNS server.
3. In the console tree, double-click Forward Lookup Zones or Reverse Lookup Zones, as applicable.
4. Right-click the zone, click Properties, and then click the Zone Transfers tab.
5. Ensure that the Allow zone transfers check box is selected.
If zone transfer fails with Event ID 6525 Zone transfer for secondary zone <zone_name> refused by master server and the master server allows dynamic updates for the zone, these failures are due to the zone transfer throttling mechanism, and they are expected. This mechanism limits the number of zone transfers to allow regular dynamic updates to take place.
http://207.46.196.114/windowsserver/en/library/547be1bb-1a55-465b-a39c-e326d31e1cf71033.mspx?mfr=true
>>>> Veera.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
what will happen if i allow zone transfers check box is checked?
1. It could be network related issues - Speed/congession/Duplex settings.
2. It could be your server performance - Hardware/OS/Exchange.
3. It could be the client side issue.
Check Event Logs on the server. If nothing specific, enable necessary diagnostic logging on Exchange and keep monitoring the event logs.
Is it happening for the whole day or only at certain duration?
NOTE: To get quick response and resolution, always provide clear details of the issue.
>>>> Veera.