Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Exchange Connectivity Problem 1

Status
Not open for further replies.

Smeglor

IS-IT--Management
Jan 16, 2004
70
US
Hello,

I have an Exchange 2003 server in our network and I keep getting Topology and LDAP errors. It seems to disconnect authentication from our PDC and BDC. For no apparent reason, the Exchange server will become unavailable causing users to get the login box from Outlook which keeps popping up. During this time I ran netdiag which fails to find domain controllers or group controllers but dcdiag works fine. I can also ping and browse both DCs. I see that its not a network connectivity issue since I can ping and browse and when I browse a DCs files I am not prompted for a password. When the Exchange server get unavailable, it lasts for about 15 minutes then reconnects to one of the DCs and everything is fine for a while. Netlogon also fails either before or after the initial Topology errors. I tried adding the MaxDgrambuffer registry trick but it didnt work. ONCE Exchange comes back online with the PDC and BDC netdiag works fine, all passed. Here are some of the logs as I get about 50-60 Topology and LDAP errors in a row when Exchange does this.

Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2102
Date: 4/15/2004
Time: 7:16:06 AM
User: N/A
Computer: EXCHANGESERVER
Description:
Process MAD.EXE (PID=952). All Domain Controller Servers in use are not responding:
PDC.internalnetwork.com
BDC.internalnetwork.com


For more information, click
Event Type: Information
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2070
Date: 4/15/2004
Time: 7:16:06 AM
User: N/A
Computer: EXCHANGESERVER
Description:
Process MAD.EXE (PID=952). DSAccess lost contact with domain controller PDC.internalnetwork.com. Error was 80040951 (). DSAccess will attempt to reconnect with this domain controller when it is reachable.

For more information, click
Event Type: Warning
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2107
Date: 4/15/2004
Time: 7:16:06 AM
User: N/A
Computer: EXCHANGESERVER
Description:
Process MAD.EXE (PID=952). DSAccess failed to obtain an IP address for DS server PDC.internalnetwork.com, error 11004. This host will not be used as a DS server by DSAccess.

For more information, click
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2119
Date: 4/15/2004
Time: 7:16:07 AM
User: N/A
Computer: EXCHANGESERVER
Description:
Process MAD.EXE (PID=952). Error DNS_ERROR_RCODE_NAME_ERROR (0x8007232b) occurred when DNS was queried for the service location (SRV) resource record used to locate a domain controller for domain internalnetwork.com
The query was for the SRV record for _ldap._tcp.dc._msdcs.internalnetwork.com
Common causes of this error include the following:
- The DNS SRV records required to locate a domain controller for the domain are not registered in DNS. These records are registered with a DNS server automatically when a domain controller is added to a domain. They are updated by the domain controller at set intervals. This computer is configured to use DNS servers with following IP addresses:
192.168.X.X
192.168.X.X

- One or more of the following zones do not include delegation to its child zone:
internalnetwork.com
INTERNAL.com
com
. (the root zone)
For information about correcting this problem, type in the command line:
hh tcpip.chm::/sag_DNS_tro_dcLocator_messageE.htm

For more information, see Help and Support Center at
Event Type: Warning
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2107
Date: 4/15/2004
Time: 7:16:07 AM
User: N/A
Computer: EXCHANGESERVER
Description:
Process MAD.EXE (PID=952). DSAccess failed to obtain an IP address for DS server PDC.internalnetwork.com, error 11004. This host will not be used as a DS server by DSAccess.

For more information, click
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: LDAP
Event ID: 2066
Date: 4/15/2004
Time: 7:19:11 AM
User: N/A
Computer: EXCHANGESERVER
Description:
Process INETINFO.EXE (PID=1640). An LDAP Notify call failed - Server=BDC.internalnetwork.com Error code=800704d5. Base DN=CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=Internal,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=internal,DC=internalps,DC=com, Filter=, Scope=1.

For more information, click
Event Type: Error
Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2114
Date: 4/15/2004
Time: 7:21:09 AM
User: N/A
Computer: EXCHANGESERVER
Description:
Process MAD.EXE (PID=952). Topology Discovery failed, error 0xffffffff.

For more information, click
Event Type: Error
Event Source: MSExchangeSA
Event Category: General
Event ID: 9153
Date: 4/15/2004
Time: 7:27:00 AM
User: N/A
Computer: EXCHANGESERVER
Description:
Microsoft Exchange System Attendant reported an error '0x80004005' when setting DS notification.

For more information, click
Event Type: Error
Event Source: POP3SVC
Event Category: Authentication
Event ID: 1019
Date: 4/15/2004
Time: 7:29:59 AM
User: N/A
Computer: EXCHANGESERVER
Description:
MDAGetInfo() failed with error 0x80004005.

For more information, click Data:
0000: 5c 09 1b 00 \...


Heres the Netlogn Error from the System Eventlog

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 4/15/2004
Time: 7:30:05 AM
User: N/A
Computer: EXCHANGESERVER
Description:
This computer was not able to set up a secure session with a domain controller in domain INTERNAL due to the following:
The RPC server is unavailable.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.

For more information, see Help and Support Center at Data:
0000: 17 00 02 c0 ...À

Any help will be greatly appreciated.


I don't know sir...I guess its broke.
 
80040951 bacically means the netlogon service wasn't up on the DC. 11004 means the IP destination was unreachable. Then you get the 8007232b thatthe SRV records for the DC weren't registered, and down the slippery slope you went.

From the scenario, I would deduce that:

1. The DC which Exchange was using for the configuration container was rebooted.

2. The DC points to itself for DNS.



When a DC points to itself for DNS, this can be a problem on reboot because netlogon starts before the DNS service. That's why the SRV records don't get registered. Try:

1. on the DC in question restart the netlogon service.
2. on the DC in question ipconfig /registerdns
3. on the DC in question nbtstat -RR

That should reregister all the required records.

 
Thanks for the reply. I gave it a try and will see how it goes. Thanks again.

I don't know sir...I guess its broke.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top