• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

remote DC down preventing Exch2K from working

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2000] >> General >> remote DC down preventing Exch2K from working Page: [1] 2   next >   >>
Login
Message << Older Topic   Newer Topic >>
remote DC down preventing Exch2K from working - 7.Nov.2006 1:50:10 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
We have one W2K AD Domain and two sites.  Our remote site has a DC running DNS, GC, DHCP and WINS for computers there.  Our main site has the Exchange 2K server and three DC's with two of them being GC's and DHCP servers.  We also use DFS to do replication between the sites in order to supply faster data to the remote site.  All our servers are updated using WSUS so they have the latest SP's.  Last night at our remote site it appears that we lost power and that the UPS didn't keep the DC running and it appears to have restarted about three times in attempts to get going again but it was estentually off from 10:22pm to about 6:35am.  During this time our Exchange server quit allowing people to connect with Outlook and when I found out at about 10:45pm I noticed that the IS service had stopped as well as the MS Exchange System Attendant.  The events in the Exchange Application event viewer are the following:
Time        Source        Category       Event
10:22pm   MSExchangeDSAccess   Topology   2102
(Process MAD.exe, all DC servers in use are not responding [listed all three DCs at main site and the one remote DC])
10:24pm   MSExchangeDSAccess   Topology   2103
(Process MAD.exe, all DC servers in use are not responding [listed all three DCs at main site and the one remote DC])
10:25pm   MSExchangeSA   NSPI Proxy   9176
NSPI Proxy can contact Global Catalog <remote DC> but it does not support the NSPI service. After a Domain Controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI Clients.  Reboot <remote DC> as soon as possible.
NSPI Proxy can contact Global Catalog IDC2.interconnect-wiring.com but it does not support the NSPI service. After a Domain Controller is promoted to a Global Catalog, the Global Catalog must be rebooted to support MAPI Clients.  Reboot IDC2.interconnect-wiring.com as soon as possible. 

10:25pm   MSExchangeSA   NSPI Proxy   9057
NSPI Proxy cannot contact any Global Catalog that supports the NSPI Service. New clients will be refused until a Global Catalog is available. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients.
10:25pm   MSExchangeSA   RFR Interface   9143  
Referral Interface cannot contact any Global Catalog that supports the NSPI Service. Clients making RFR requests will fail to connect until a Global Catalog becomes available again. After a Domain Controller is promoted to a Global Catalog, it must be rebooted to support MAPI Clients.
10:25pm   MSExchangeSA   RFR Interface   9074
The Directory Service Referral interface failed to service a client request. RFRI is returning the error code:[0x3f0].
10:33pm   MSExchangeDSAccess   Topology   2102
(Process MAD.exe, all DC servers in use are not responding [listed all three DCs at main site and the one remote DC])
{Above events repeat}
10:36pm   MSExchangeSA   General   9154
DSACCESS returned an error '0x80004005' on DS notification. Microsoft Exchange System Attendant will re-set DS notification later.
10:40pm   MSExchangeDSAccess   Topology   2102
(Process MAD.exe, all DC servers in use are not responding [listed all three DCs at main site and the one remote DC])
..
..
During this time I tried rebooting Exchange but to no avail.  Many events later, about 6:30am - someone rebooted the remote DC and then we could reboot the Exchange Server and the Information Store mounted fine. 

My main question is how could a DC running as a GC on a remote site cause our Exchange server to not work when we have three local DC's in our main site and two of them are GC's.

Any thoughts?
Post #: 1
RE: remote DC down preventing Exch2K from working - 7.Nov.2006 2:48:21 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
First is your Exchange also a DC? Second open ESM, right click your server name, properties, dsaccess tab, what servers do you see? Exchange contains two lists of GC's 1. GC's in local site (preferred) and 2. GC's in remote sites.



_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 2
RE: remote DC down preventing Exch2K from working - 7.Nov.2006 2:53:06 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
No, it is not a DC.  I right-clicked Directory Access and found only this one DC at the remote site and Add/Remove buttons are disabled as the "Automatically Discover Servers" checkbox is checked.  Why is it not discovering the local DCs and GCs?

(in reply to jchong)
Post #: 3
RE: remote DC down preventing Exch2K from working - 7.Nov.2006 11:34:55 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
One reason why Ex servers do not discovery proper DC's is because AD sites and services are misconfigured. Can you verify that your DCs are in the correct sites in sites and services? Also run Exchange best practice analyzer.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 4
RE: remote DC down preventing Exch2K from working - 8.Nov.2006 12:54:21 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
I don't see anything misconfigured in AD S&S and I'm running the Analyzer now and it should be done with a baseline in about 20 minutes.  More info then.

(in reply to jchong)
Post #: 5
RE: remote DC down preventing Exch2K from working - 8.Nov.2006 3:24:37 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
I can ping all the DCs and they are authenicating users and seem to be setup right in AD Sites & Services.  What else can I do to figure this out?

Here is some of the output from the Exchange BP Analyzer from the "Directory Access" section:

Directory Access
  Directory Access Topology Rules =
   Win32_PerfRawData_MSExchangeDSAccess_MSExchangeDSAccessCaches.Name="0"
   Exchange_DSAccessDC.Name="DC2.interconnect-wiring.com",Type=0
  Name =DC2.interconnect-wiring.com
  Type =0
  ConfigurationType =1
  IsFast =True
  IsInSync =True
  IsUp =True
  LDAPPort =389
   SiteName =RemoteSite
   Exchange server IW-EXCHANGE belongs to Active Directory site 'Default-First-Site-Name', but DSAccess is using domain controller DC2.interconnect-wiring.com which is a member of Active Directory site 'RemoteSite'. This may cause Exchange server performance degradation.
  1
  2
  3
  4
  5
  6
  Port Verification
  389 389
  187.5
  389 Available
  636 
  250
  636 Available
   Exchange_DSAccessDC.Name="DC2.interconnect-wiring.com",Type=1
  Name =DC2.interconnect-wiring.com
  Type =1
  ConfigurationType =1
  IsFast =True
  IsInSync =True
  IsUp =True
  LDAPPort =389
   SiteName =RemoteSite
   Exchange server IW-EXCHANGE belongs to Active Directory site 'Default-First-Site-Name', but DSAccess is using domain controller DC2.interconnect-wiring.com which is a member of Active Directory site 'RemoteSite'. This may cause Exchange server performance degradation.
  1
  2
  3
  4
  5
  6
  Port Verification
  389 389
  78.125
  389 Available
  636 
  15.625
  636 Available
   Exchange_DSAccessDC.Name="DC2.interconnect-wiring.com",Type=2
  Name =DC2.interconnect-wiring.com
  Type =2
   ConfigurationType =0
   The DSAccess process on server IW-EXCHANGE has been hard-coded to use Active Directory server DC2.interconnect-wiring.com. This configuration is not recommended as it provides limited fail-over options.
  IsFast =True
  IsInSync =True
  IsUp =True
  LDAPPort =3268
   SiteName =RemoteSite
   Exchange server IW-EXCHANGE belongs to Active Directory site 'Default-First-Site-Name', but DSAccess is using global catalog server DC2.interconnect-wiring.com which is a member of Active Directory site 'RemoteSite'. This may cause Exchange server performance degradation.
  1
  2
  3
  4
  5
  6
  Port Verification
  3268 3268
  62.5
  3268 Available
  3269 
  78.125
  3269 Available
   Exchange_DSAccessDC.Name="DC1_1.interconnect-wiring.com",Type=2
  Name =DC1_1.interconnect-wiring.com
  Type =2
   ConfigurationType =0
   The DSAccess process on server IW-EXCHANGE has been hard-coded to use Active Directory server DC1_1.interconnect-wiring.com. This configuration is not recommended as it provides limited fail-over options.
  IsFast =False
  IsInSync =False
   IsUp =False
   The DSAccess process on server IW-EXCHANGE reports that Active Directory server DC1_1.interconnect-wiring.com is not functional.
  LDAPPort =3268
  SiteName =Default-First-Site-Name
  1
  2
  3
  4
  5
  6
  Port Verification
  3268 3268
  0
  3268 Available
  3269 
  0
  3269 Available
   Exchange_DSAccessDC.Name="DC1.interconnect-wiring.com",Type=2

(in reply to dougsymes)
Post #: 6
RE: remote DC down preventing Exch2K from working - 9.Nov.2006 10:12:04 AM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
Looks like you hard coded this config?

The DSAccess process on server IW-EXCHANGE has been hard-coded to use Active Directory server DC1_1.interconnect-wiring.com.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 7
RE: remote DC down preventing Exch2K from working - 9.Nov.2006 1:03:23 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
Here is what DCDIAG says for DC1:

         ......................... DC1 passed test Connectivity

Doing primary tests
 
  Testing server: Default-First-Site-Name\DC1
     Starting test: Replications
        ......................... DC1 passed test Replications
     Starting test: NCSecDesc
        ......................... DC1 passed test NCSecDesc
     Starting test: NetLogons
        ......................... DC1 passed test NetLogons
     Starting test: Advertising
        Warning: DC1 is not advertising as a time server.
        ......................... DC1 failed test Advertising
     Starting test: KnowsOfRoleHolders
        ......................... DC1 passed test KnowsOfRoleHolders
     Starting test: RidManager
        ......................... DC1 passed test RidManager
     Starting test: MachineAccount
        ......................... DC1 passed test MachineAccount
     Starting test: Services
           w32time Service is stopped on [DC1]
           TrkSvr Service is stopped on [DC1]
        ......................... DC1 failed test Services
     Starting test: ObjectsReplicated
        ......................... DC1 passed test ObjectsReplicated
     Starting test: frssysvol
        Error: No record of File Replication System, SYSVOL started.
        The Active Directory may be prevented from starting.

        ......................... DC1 passed test frssysvol
     Starting test: kccevent
        ......................... DC1 passed test kccevent
     Starting test: systemlog
        ......................... DC1 passed test systemlog
 
  Running enterprise tests on : interconnect-wiring.com
     Starting test: Intersite
        ......................... interconnect-wiring.com passed test Intersite
     Starting test: FsmoCheck
        Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
        A Time Server could not be located.
        The server holding the PDC role is down.
        Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355
        A Good Time Server could not be located.
        ......................... interconnect-wiring.com failed test FsmoCheck


We found that the FRS service was disabled and we enabled it and that fixed the frssysvol error listed above.

(in reply to jchong)
Post #: 8
RE: remote DC down preventing Exch2K from working - 9.Nov.2006 2:15:53 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
  The Windows Time Service not running.  This was preventing the DCs to function normally and ExchangeDA from connecting to them.  So I was able to setup ExchangeDA right and DCDIAG output looks good but Exchange Best Practices Analyzer still says the local DC's cannot be contacted.  Mabye I just need to allow some more time.

(in reply to dougsymes)
Post #: 9
RE: remote DC down preventing Exch2K from working - 9.Nov.2006 3:20:07 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
The server holding the PDC role is down.
 
This can also cause an issue. What's the issue with this? Give it some more time, or restart all your Exchangesa service which will restart all exchange related services as well.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 10
RE: remote DC down preventing Exch2K from working - 9.Nov.2006 3:42:52 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
I no longer get the "PDC is down" since starting the Windows Time service.

(in reply to jchong)
Post #: 11
RE: remote DC down preventing Exch2K from working - 9.Nov.2006 3:59:16 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
Good, check the times on all your DCs to ensure that they are correct. Has your Ex picked up your correct server yet? Exchange runs it's GC discovery every 15 mins.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 12
RE: remote DC down preventing Exch2K from working - 9.Nov.2006 5:13:38 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
Its "hardcoded" now...should I put it back to Auto Discovery in order to have it find them?

(in reply to jchong)
Post #: 13
RE: remote DC down preventing Exch2K from working - 10.Nov.2006 12:30:44 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
Came in this morning and it was not good...the Exch2K server is functioning but the network is having a lot of wierd problems.  I just got an Event 2102 from Exchange just now saying it couldn't talk to any of the three local DCs we have.  The overnight Exch BP Analyzer says my IFS is shared and shouldn't be and that it could not connect to any of the DC's.  I ran DCDIAG on the main DC that holds all the roles and these are the parts that failed:


Starting test: Services
TrkSvr Service is stopped on [DC1]
......................... DC1 failed test Services


Starting test: systemlog
An Error Event occured. EventID: 0xC00010DF
Time Generated: 11/10/2006 08:41:27
Event String: A duplicate name has been detected on the TCP
An Error Event occured. EventID: 0x40011006
Time Generated: 11/10/2006 09:19:47
Event String: The connection was aborted by the remote WINS.
......................... DC1 failed test systemlog

The only entries in DNS for DC1 are the following
        (same as parent) and DC1 - both with the static IP it has always had.
 


(in reply to dougsymes)
Post #: 14
RE: remote DC down preventing Exch2K from working - 10.Nov.2006 1:35:10 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
On another DC when I run DCDIAG it says

Starting test: frssysvol
   There are errors after the SYSVOL has been shared.
   The SYSVOL can prevent the AD from starting.

On the 3rd DC when I run DCDIAG it only lists:

Starting test: Services
      TrkSvr Service is stopped on [2KSERVER02]
   ......................... 2KSERVER02 failed test Services

as having failed and from what I find from MS they are saying that TrkSvr should be disabled anyway.


(in reply to dougsymes)
Post #: 15
RE: remote DC down preventing Exch2K from working - 13.Nov.2006 12:55:22 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
Whats the error about duplicate names? Check your dns records as well to see if your dns servers IPs are being used by different hosts.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 16
RE: remote DC down preventing Exch2K from working - 15.Nov.2006 4:38:55 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
For each DC there are two entries in DNS.  One for the UNC and one with "(same as parent folder).  Over the weekend I had an out-source IT support company look over our Exchange settings and they said that there were a lot of permissions settings that were different than usual and they reset them to the default and were able to get the autodiscovery to find the local site DC's.  

(in reply to jchong)
Post #: 17
RE: remote DC down preventing Exch2K from working - 15.Nov.2006 5:21:12 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
If you hard code it to your local dcs, does your Exchange work? I want to find out if it's not the discovery thats the issue, but maybe something inheritely broken with these dcs so it can't use them.

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 18
RE: remote DC down preventing Exch2K from working - 15.Nov.2006 5:25:08 PM   
dougsymes

 

Posts: 33
Joined: 5.Feb.2004
From: Fort Worth
Status: offline
Hard-coding works.  But the Config DC selection only allowed me to pick my remote site DC and I had to edit the registry to enter the local DC I wanted.  The out-source folks said that after they "fixed the permissions" they were able to use discovery to select one of our local DC's

(in reply to jchong)
Post #: 19
RE: remote DC down preventing Exch2K from working - 15.Nov.2006 8:46:22 PM   
jchong

 

Posts: 2516
Joined: 1.Dec.2005
From: Centreville, Virginia
Status: offline
I would be interested in knowing what they fixed, if you find out please share !!

_____________________________

James Chong
MCSE | M+, S+, MCTS, Security+
msexchangetips.blogspot.com

(in reply to dougsymes)
Post #: 20

Page:   [1] 2   next >   >> << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2000] >> General >> remote DC down preventing Exch2K from working Page: [1] 2   next >   >>
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter