Re: Exchange 2000 errors (2102, 9554 2070)
From: Dave Howe [MSFT] (daveh_at_online.microsoft.com)
Date: 04/19/04
- Next message: Ferdinand: "Re: instant reply"
- Previous message: Dave Howe [MSFT]: "Re: Warning MSExchangeDSAccess event 2105"
- In reply to: Ciaran: "Exchange 2000 errors (2102, 9554 2070)"
- Next in thread: Ciaran: "Re: Exchange 2000 errors (2102, 9554 2070)"
- Reply: Ciaran: "Re: Exchange 2000 errors (2102, 9554 2070)"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 19 Apr 2004 08:55:42 -0400
On Sun, 18 Apr 2004 10:36:02 -0700, Ciaran <cmadden@abacus.ie> wrote:
>Hi,
>I have an ongoing problem with my exchange 2000 server (non domain controller, windows 2000 sp4, exchange sp3 + post sp3 patch) loosing connectivity to all other domain controllers. It happens every 30 mins. I have increased the DSAccess logging to see what’s going on.
> it starts with store.exe loosing contact with all of the domain controllers (event ID 2070) then store.exe reports all domain controllers are not responding (event ID 2102). this is followed by a couple of event ID 9554's. then in a second or couple of minutes the exchange server finds all of the domain controllers.
> I have logged a call with Microsoft on this but no joy. I would really appreciate any help any one could give.
>
>I have done the usuall fix's: run forestprep domainprep, all security permissions seem to be fine. I have tried manually specifying DC's, GC's, Config Dc's.
>
>Thanks
>Ciaran
>From the Exchange server, open two command prompt windows. In the
first window, ping one of the GCs by NetBIOS name. In the other
window, ping the same GC by IP address, as follows:
Window 1:
ping -t 192.168.254.1 > pingGCbyIP.txt
Window 2:
ping -t gc1 > pingGCbyName.txt
After an outage, check both output files. If the ping by Name fails
but the ping by IP address does not, then you have a DNS lookup
problem. If the ping by IP and ping by Name both fail at the same
time, then you have a connectivity issue.
For DNS issues:
Make sure the Exchange server is configured to query ONLY internal
DNS servers, not public (ISP) DNS servers. The local DNS server
should be configured to forward any unresolvable requests to a public
DNS server.
For Connectivity issues:
Start with the basics. Check the NIC, check the patch cable, check
the port on the switch, etc.
Hope some of this helps.
--- Dave Howe Microsoft PSS This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: Ferdinand: "Re: instant reply"
- Previous message: Dave Howe [MSFT]: "Re: Warning MSExchangeDSAccess event 2105"
- In reply to: Ciaran: "Exchange 2000 errors (2102, 9554 2070)"
- Next in thread: Ciaran: "Re: Exchange 2000 errors (2102, 9554 2070)"
- Reply: Ciaran: "Re: Exchange 2000 errors (2102, 9554 2070)"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|