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

RE: Still not routing e-mails

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Message Routing >> RE: Still not routing e-mails Page: <<   < prev  1 [2] 3   next >   >>
Login
Message << Older Topic   Newer Topic >>
Limited time MSExchange.org offer! -- 1.Sep.2008 1:00:00 PM
TechGenix and SolarWinds have partnered to provide free copies of SolarWinds Exchange Monitor to all visitors who join the MSExchange.org Forums. SolarWinds Exchange Monitor is a handy desktop dashboard that continuously monitors Microsoft Exchange to deliver real-time insight into Exchange services, mail queue sizes, and host server health. Learn more about Exchange Monitor and the free offer!
RE: Still not routing e-mails - 20.Jun.2006 8:08:10 PM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
Here is what I see....

Under Directory Access on the Exchange server I have both DCs listed (a total of four entries - 2 for each (PDC - Config & DC; BDC - GC & DC))
Exchange 2003 is loaded on an Windows 2003 Server (Enterprise) and the DCs are both Windows 2000 (latest SPs)
Yes - All new accounts that I have designated in ADS Users and Computers (Exchanger Server only for now) work fine.  I have four up right now.  I'm hesitiate to add anymore if I have to rebuild again or something like that.

The Exchange server is still in the domain (from the My Computer properties and from the ADS Computer list).

The Exchange Domain Server group has the exchange server listed (the only one) and the Exchange Enterprise Servers lists the Exchange Domain Server group.

I believe that is all good.  Could this be a side effect from the reinstallation?  Would a repair installation correct this?  Just curious.  If I can get this corrected I'm good to go!  Thanks for your help on this Liquid22!

_____________________________

Texman

(in reply to liquid22)
Post #: 21
RE: Still not routing e-mails - 20.Jun.2006 8:16:27 PM   
liquid22

 

Posts: 108
Joined: 24.Nov.2004
From: Houston
Status: offline
No problem on the help. :) 

Well your config seems okay from what I can tell.

The only other thought I had is when first step of the install, forestprep, did you run that from the server that you were installing Exchange on?  The forestprep and domainprep steps need to be ran from the DC that holds the FSMO roles.  The account used during the install also has to be at least a member of the Enterprise Admins or Domain Admins and Schema Admins groups (which most likely it was).

If you didn't run setup /forestprep and setup /domainprep from the DC holding the FSMO role re-run those from the DC.  I don't think a full reinstall will be necessary but it might be.

To check which DC holds that role open AD, right-click on your domain and select Operations Master.  There should be three tabs listed and in small installs typically one DC holds all 3 roles. 

(in reply to texmansru47)
Post #: 22
RE: Still not routing e-mails - 20.Jun.2006 10:04:25 PM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
I did run setup /forestprep and /domainprep from the PDC proper to the installation.  However from this discovery it looks like the main player in my DCs is the BDC.  I will try to run from there.  I hope this resolves it, since I truly am not looking for a completet reinstallation again.

But if I must.  I will write back after the forestprep and domainprep.

Thanks,


_____________________________

Texman

(in reply to liquid22)
Post #: 23
RE: Still not routing e-mails - 20.Jun.2006 10:34:02 PM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
/forestprep and /domainprep have been completed... the same problem exists.

Honestly, I cannot see where the freaking problem is?  ADS sees the server, DNS sees the server, the server sees the freaking mailboxes, so what the heck is the freaking deal? No wonder MS gets so much hate mail.  the KISS method is completely ignored.  This configuration should be working.  I ahve this one freaking problem and it starting to sound like I have to rebuild the darn server AGAIN!!!!   This is crazy!  There HAS to be a better way of getting this to resolve the darn server and user accounts in Outlook... ther has to be outside of a rebuild.

Thanks,


_____________________________

Texman

(in reply to texmansru47)
Post #: 24
RE: Still not routing e-mails - 21.Jun.2006 5:32:14 PM   
liquid22

 

Posts: 108
Joined: 24.Nov.2004
From: Houston
Status: offline
I agree there has to be a way to resolve this without a full rebuild again.

It doesn't make sense to me either to be honest with you.  Maybe now that forestprep and domainprep have been run from the FSMO server maybe Exchange should be reinstalled in recoverymode to correct any potential errors.  The command is "setup /disasterrecovery" and when the wizard starts it should read Disaster Recovery from the install options. 

If that doesn't work it may be time to open a ticket with M$. 

(in reply to texmansru47)
Post #: 25
RE: Still not routing e-mails - 21.Jun.2006 6:26:36 PM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
I will process that here shortly.  Thanks for the tip. 

I will report back once I complete this.

Thanks,


_____________________________

Texman

(in reply to liquid22)
Post #: 26
RE: Still not routing e-mails - 21.Jun.2006 6:35:20 PM   
liquid22

 

Posts: 108
Joined: 24.Nov.2004
From: Houston
Status: offline
I'll have my fingers crossed for ya.

(in reply to texmansru47)
Post #: 27
RE: Still not routing e-mails - 21.Jun.2006 8:27:14 PM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
Nope.  Still in the same world of hurt.

Since I have no choice but to reinstall and I do not have a million days for MS to respond to my ticket, what would be the cleanest way to do this rebuild....

1.  Disable/delete mailboxes from the Active Directory Users and Computers
2.  Disable the services
3.  Uninstall Exchange from the server (Control Panel -> Add/Remove Applications)
4.  Uninstall IIS and .NET
5.  Run ADSIEDIT and delete the Exchange Container (it states to use the /removeorg parameter, but I fear this will create too much problems and may not remove just what I desire to remove, so I just delete the container, is this correct?
6.  Reinstall IIS and .NET (if I remove this I may just rebuild the freaking whole server and start clean.
7.  Reinstall Exchange (running Forestprep and domainprep from the DCs)
8.  load updates to exchange.
9.  Try again.

Does this sound about right?

Thanks,


_____________________________

Texman

(in reply to liquid22)
Post #: 28
RE: Still not routing e-mails - 21.Jun.2006 8:30:53 PM   
liquid22

 

Posts: 108
Joined: 24.Nov.2004
From: Houston
Status: offline
Yes that sounds good to me.

At this point I would rebuild the entire server from scratch after you've uninstalled Exchange and removed its references from AD.  In my experience it's best to eliminate as many variables as possible.

Good luck.

(in reply to texmansru47)
Post #: 29
RE: Still not routing e-mails - 21.Jun.2006 8:44:55 PM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
Liquid22,

Question:

Would having the Distributed Transaction Coordinator service in DISABLED setting and being off cause this type of issue I'm having?  Dumby me forgot to reenable it after the last rebuild.

Thanks,


_____________________________

Texman

(in reply to liquid22)
Post #: 30
RE: Still not routing e-mails - 21.Jun.2006 8:46:14 PM   
liquid22

 

Posts: 108
Joined: 24.Nov.2004
From: Houston
Status: offline
Ahh - it just might.  I never even thought about that.  It's definitely worth a shot at this point. :)

(in reply to texmansru47)
Post #: 31
RE: Still not routing e-mails - 21.Jun.2006 8:52:43 PM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
I had just killed the mailboxes and I saw that.  I have reenabled it and rebooting currently.  Hopefully, this will work.  I tried it right after I reenabled everything and it still did not work so I hope a reboot resolves it.

If not, the rebuild will occur... I cannot waste anymore time.  I hate to say.

Thanks,



_____________________________

Texman

(in reply to liquid22)
Post #: 32
RE: Still not routing e-mails - 21.Jun.2006 10:14:11 PM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
Rebuilding the server and the exchange again, from scratch!  Hopefully my troubles will be gone soon.  Liquid 22 - Thanks for all your help.  It was greatly appericated!

Thanks again,



_____________________________

Texman

(in reply to texmansru47)
Post #: 33
RE: Still not routing e-mails - 22.Jun.2006 3:26:01 AM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
I did a complete rebuild of the Exchange Server and reloaded Exchange totally fresh.. That FREAKIN crappy error (cannot match user name).  Is there again.  WHY!!!!!!!   WTF!!!!!!!!!   This is total BS!

_____________________________

Texman

(in reply to texmansru47)
Post #: 34
RE: Still not routing e-mails - 22.Jun.2006 6:42:04 AM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
There has to be a ADS issue:  Attached below is the results from the DCDiag.exe prior to the installation of the exchange server:


Domain Controller Diagnosis
Performing initial setup:
  Done gathering initial info.
Doing initial required tests
 
  Testing server: Default-First-Site-Name\TXBDC
     Starting test: Connectivity
        ......................... TXBDC passed test Connectivity
Doing primary tests
 
  Testing server: Default-First-Site-Name\TXBDC
     Starting test: Replications
        ......................... TXBDC passed test Replications
     Starting test: NCSecDesc
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        ......................... TXBDC failed test NCSecDesc
     Starting test: NetLogons
        ......................... TXBDC passed test NetLogons
     Starting test: Advertising
        ......................... TXBDC passed test Advertising
     Starting test: KnowsOfRoleHolders
        ......................... TXBDC passed test KnowsOfRoleHolders
     Starting test: RidManager
        ......................... TXBDC passed test RidManager
     Starting test: MachineAccount
        ......................... TXBDC passed test MachineAccount
     Starting test: Services
        ......................... TXBDC passed test Services
     Starting test: ObjectsReplicated
        ......................... TXBDC passed test ObjectsReplicated
     Starting test: frssysvol
        ......................... TXBDC passed test frssysvol
     Starting test: frsevent
        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.
        ......................... TXBDC failed test frsevent
     Starting test: kccevent
        An Warning Event occured.  EventID: 0x8000046E
           Time Generated: 06/21/2006   18:32:04
           (Event String could not be retrieved)
        ......................... TXBDC failed test kccevent
     Starting test: systemlog
        ......................... TXBDC passed test systemlog
     Starting test: VerifyReferences
        ......................... TXBDC passed test VerifyReferences
 
  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 : texas
     Starting test: CrossRefValidation
        ......................... texas passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... texas passed test CheckSDRefDom
 
  Running enterprise tests on : texas.natcominc.com
     Starting test: Intersite
        ......................... texas.natcominc.com passed test Intersite
     Starting test: FsmoCheck
        ......................... texas.natcominc.com passed test FsmoCheck
Domain Controller Diagnosis
Performing initial setup:
  Done gathering initial info.
Doing initial required tests
 
  Testing server: Default-First-Site-Name\TXPDC
     Starting test: Connectivity
        ......................... TXPDC passed test Connectivity
Doing primary tests
 
  Testing server: Default-First-Site-Name\TXPDC
     Starting test: Replications
        ......................... TXPDC passed test Replications
     Starting test: NCSecDesc
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        ......................... TXPDC failed test NCSecDesc
     Starting test: NetLogons
        ......................... TXPDC passed test NetLogons
     Starting test: Advertising
        ......................... TXPDC passed test Advertising
     Starting test: KnowsOfRoleHolders
        ......................... TXPDC passed test KnowsOfRoleHolders
     Starting test: RidManager
        ......................... TXPDC passed test RidManager
     Starting test: MachineAccount
        ......................... TXPDC passed test MachineAccount
     Starting test: Services
        ......................... TXPDC passed test Services
     Starting test: ObjectsReplicated
        ......................... TXPDC passed test ObjectsReplicated
     Starting test: frssysvol
        ......................... TXPDC passed test frssysvol
     Starting test: frsevent
        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.
        ......................... TXPDC failed test frsevent
     Starting test: kccevent
        An Warning Event occured.  EventID: 0x8000046E
           Time Generated: 06/21/2006   18:30:17
           (Event String could not be retrieved)
        ......................... TXPDC failed test kccevent
     Starting test: systemlog
        An Error Event occured.  EventID: 0x0000165B
           Time Generated: 06/21/2006   17:46:31
           Event String: The session setup from computer 'USFTWPLEX'
        ......................... TXPDC failed test systemlog
     Starting test: VerifyReferences
        ......................... TXPDC passed test VerifyReferences
 
  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 : texas
     Starting test: CrossRefValidation
        ......................... texas passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... texas passed test CheckSDRefDom
 
  Running enterprise tests on : texas.natcominc.com
     Starting test: Intersite
        ......................... texas.natcominc.com passed test Intersite
     Starting test: FsmoCheck
        ......................... texas.natcominc.com passed test FsmoCheck
Domain Controller Diagnosis
Performing initial setup:
  Done gathering initial info.
Doing initial required tests
 
  Testing server: Default-First-Site-Name\TXPDC
     Starting test: Connectivity
        ......................... TXPDC passed test Connectivity
Doing primary tests
 
  Testing server: Default-First-Site-Name\TXPDC
     Starting test: Replications
        ......................... TXPDC passed test Replications
     Starting test: NCSecDesc
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        ......................... TXPDC failed test NCSecDesc
     Starting test: NetLogons
        ......................... TXPDC passed test NetLogons
     Starting test: Advertising
        ......................... TXPDC passed test Advertising
     Starting test: KnowsOfRoleHolders
        ......................... TXPDC passed test KnowsOfRoleHolders
     Starting test: RidManager
        ......................... TXPDC passed test RidManager
     Starting test: MachineAccount
        ......................... TXPDC passed test MachineAccount
     Starting test: Services
        ......................... TXPDC passed test Services
     Starting test: ObjectsReplicated
        ......................... TXPDC passed test ObjectsReplicated
     Starting test: frssysvol
        ......................... TXPDC passed test frssysvol
     Starting test: frsevent
        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.
        ......................... TXPDC failed test frsevent
     Starting test: kccevent
        An Warning Event occured.  EventID: 0x8000046E
           Time Generated: 06/21/2006   20:30:17
           (Event String could not be retrieved)
        ......................... TXPDC failed test kccevent
     Starting test: systemlog
        ......................... TXPDC passed test systemlog
     Starting test: VerifyReferences
        ......................... TXPDC passed test VerifyReferences
 
  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 : texas
     Starting test: CrossRefValidation
        ......................... texas passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... texas passed test CheckSDRefDom
 
  Running enterprise tests on : texas.natcominc.com
     Starting test: Intersite
        ......................... texas.natcominc.com passed test Intersite
     Starting test: FsmoCheck
        ......................... texas.natcominc.com passed test FsmoCheck
Domain Controller Diagnosis
Performing initial setup:
  Done gathering initial info.
Doing initial required tests
 
  Testing server: Default-First-Site-Name\TXPDC
     Starting test: Connectivity
        ......................... TXPDC passed test Connectivity
Doing primary tests
 
  Testing server: Default-First-Site-Name\TXPDC
     Starting test: Replications
        ......................... TXPDC passed test Replications
     Starting test: NCSecDesc
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        ......................... TXPDC failed test NCSecDesc
     Starting test: NetLogons
        ......................... TXPDC passed test NetLogons
     Starting test: Advertising
        ......................... TXPDC passed test Advertising
     Starting test: KnowsOfRoleHolders
        ......................... TXPDC passed test KnowsOfRoleHolders
     Starting test: RidManager
        ......................... TXPDC passed test RidManager
     Starting test: MachineAccount
        ......................... TXPDC passed test MachineAccount
     Starting test: Services
        ......................... TXPDC passed test Services
     Starting test: ObjectsReplicated
        ......................... TXPDC passed test ObjectsReplicated
     Starting test: frssysvol
        ......................... TXPDC passed test frssysvol
     Starting test: frsevent
        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.
        ......................... TXPDC failed test frsevent
     Starting test: kccevent
        An Warning Event occured.  EventID: 0x8000046E
           Time Generated: 06/21/2006   20:30:17
           (Event String could not be retrieved)
        ......................... TXPDC failed test kccevent
     Starting test: systemlog
        ......................... TXPDC passed test systemlog
     Starting test: VerifyReferences
        ......................... TXPDC passed test VerifyReferences
 
  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 : texas
     Starting test: CrossRefValidation
        ......................... texas passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... texas passed test CheckSDRefDom
 
  Running enterprise tests on : texas.natcominc.com
     Starting test: Intersite
        ......................... texas.natcominc.com passed test Intersite
     Starting test: FsmoCheck
        ......................... texas.natcominc.com passed test FsmoCheck
Domain Controller Diagnosis
Performing initial setup:
  Done gathering initial info.
Doing initial required tests
 
  Testing server: Default-First-Site-Name\TXPDC
     Starting test: Connectivity
        ......................... TXPDC passed test Connectivity
Doing primary tests
 
  Testing server: Default-First-Site-Name\TXPDC
     Starting test: Replications
        ......................... TXPDC passed test Replications
     Starting test: NCSecDesc
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        ......................... TXPDC failed test NCSecDesc
     Starting test: NetLogons
        ......................... TXPDC passed test NetLogons
     Starting test: Advertising
        ......................... TXPDC passed test Advertising
     Starting test: KnowsOfRoleHolders
        ......................... TXPDC passed test KnowsOfRoleHolders
     Starting test: RidManager
        ......................... TXPDC passed test RidManager
     Starting test: MachineAccount
        ......................... TXPDC passed test MachineAccount
     Starting test: Services
        ......................... TXPDC passed test Services
     Starting test: ObjectsReplicated
        ......................... TXPDC passed test ObjectsReplicated
     Starting test: frssysvol
        ......................... TXPDC passed test frssysvol
     Starting test: frsevent
        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.
        ......................... TXPDC failed test frsevent
     Starting test: kccevent
        An Warning Event occured.  EventID: 0x8000046E
           Time Generated: 06/21/2006   23:30:18
           (Event String could not be retrieved)
        ......................... TXPDC failed test kccevent
     Starting test: systemlog
        An Error Event occured.  EventID: 0x00000457
           Time Generated: 06/21/2006   22:42:48
           (Event String could not be retrieved)
        An Error Event occured.  EventID: 0x00000452
           Time Generated: 06/21/2006   22:42:48
           (Event String could not be retrieved)
        An Error Event occured.  EventID: 0x00000457
           Time Generated: 06/21/2006   22:42:49
           (Event String could not be retrieved)
        An Error Event occured.  EventID: 0x00000452
           Time Generated: 06/21/2006   22:42:49
           (Event String could not be retrieved)
        An Error Event occured.  EventID: 0x00000457
           Time Generated: 06/21/2006   22:44:26
           (Event String could not be retrieved)
        An Error Event occured.  EventID: 0x00000452
           Time Generated: 06/21/2006   22:44:27
           (Event String could not be retrieved)
        ......................... TXPDC failed test systemlog
     Starting test: VerifyReferences
        ......................... TXPDC passed test VerifyReferences
 
  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 : texas
     Starting test: CrossRefValidation
        ......................... texas passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... texas passed test CheckSDRefDom
 
  Running enterprise tests on : texas.natcominc.com
     Starting test: Intersite
        ......................... texas.natcominc.com passed test Intersite
     Starting test: FsmoCheck
        ......................... texas.natcominc.com passed test FsmoCheck
Domain Controller Diagnosis
Performing initial setup:
  Done gathering initial info.
Doing initial required tests
 
  Testing server: Default-First-Site-Name\TXBDC
     Starting test: Connectivity
        ......................... TXBDC passed test Connectivity
Doing primary tests
 
  Testing server: Default-First-Site-Name\TXBDC
     Starting test: Replications
        ......................... TXBDC passed test Replications
     Starting test: NCSecDesc
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Schema,CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error NT AUTHORITY\ENTERPRISE DOMAIN CONTROLLERS doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        Error BUILTIN\Administrators doesn't have
           Replicating Directory Changes All
        access rights for the naming context:
        CN=Configuration,DC=texas,DC=natcominc,DC=com
        ......................... TXBDC failed test NCSecDesc
     Starting test: NetLogons
        ......................... TXBDC passed test NetLogons
     Starting test: Advertising
        ......................... TXBDC passed test Advertising
     Starting test: KnowsOfRoleHolders
        ......................... TXBDC passed test KnowsOfRoleHolders
     Starting test: RidManager
        ......................... TXBDC passed test RidManager
     Starting test: MachineAccount
        ......................... TXBDC passed test MachineAccount
     Starting test: Services
        ......................... TXBDC passed test Services
     Starting test: ObjectsReplicated
        ......................... TXBDC passed test ObjectsReplicated
     Starting test: frssysvol
        ......................... TXBDC passed test frssysvol
     Starting test: frsevent
        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.
        ......................... TXBDC failed test frsevent
     Starting test: kccevent
        An Warning Event occured.  EventID: 0x8000046E
           Time Generated: 06/21/2006   23:32:04
           (Event String could not be retrieved)
        ......................... TXBDC failed test kccevent
     Starting test: systemlog
        ......................... TXBDC passed test systemlog
     Starting test: VerifyReferences
        ......................... TXBDC passed test VerifyReferences
 
  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 : texas
     Starting test: CrossRefValidation
        ......................... texas passed test CrossRefValidation
     Starting test: CheckSDRefDom
        ......................... texas passed test CheckSDRefDom
 
  Running enterprise tests on : texas.natcominc.com
     Starting test: Intersite
        ......................... texas.natcominc.com passed test Intersite
     Starting test: FsmoCheck
        ......................... texas.natcominc.com passed test FsmoCheck


The problem is I ran this with the /s: pointing to TXPDC not BDCTX, so it is apparent that the BDC thinks it is master, and will not release it.  I ran the ntsutil /role /connection... trasnfer pdc & transfer RID Master, and apparently nothing.  I would love to figure out what the IT manager did with this network prior to my hire date, he screwed it up bad!  Would ADS being not right create my problem of not being able to find the user list or exchange server when I try to setup outlook?  Right now, that is my only solution, since I completely rebuilt the server from scratch!

Please let me know if I'm in the parkball.

Thanks,


_____________________________

Texman

(in reply to texmansru47)
Post #: 35
RE: Still not routing e-mails - 22.Jun.2006 3:37:20 PM   
liquid22

 

Posts: 108
Joined: 24.Nov.2004
From: Houston
Status: offline
According to this article that error can come up when the 2003 version of DCDiag is ran and there are no 2003 domain controllers.
http://support.microsoft.com/default.aspx?scid=kb;en-us;829306

I think you're in the right ball park.  AD and Exchange are very closely tied together.  Is your domain in Native or Mixed mode?  If you have no NT 4 domain controllers I would make it native.  Also make sure that the DC's are registered in DNS.  Verify that there is an "_msdcs" with your domain controller information listed in DNS.  If the DC's are also the DNS servers make sure they are pointing to themselves under the DNS TCP/IP settings.

In a 2000/2003 domain there really isn't a Primary Domain Controller and a Backup Domain Controller as there was in NT 4.0 domain.  All DC's are considered equals unless you have NT4 machines or NT4 BDC's in which case one DC will pretend it's a PDC for backwards compatilbility. 

You may need to run dcpromo to demote the DC's and re-promote them back, maybe that'll correct the permissions issue.  If you're able to maybe upgrading your DC's to 2003 may be in order now. 

Run dcdiag /v to see if you still get that error.

But I do think the problem is possibly isolated to Active Directory and your DC's.  Might want to run replmon and make sure that they are replicating with each other too.

< Message edited by liquid22 -- 22.Jun.2006 3:53:43 PM >

(in reply to texmansru47)
Post #: 36
RE: Still not routing e-mails - 22.Jun.2006 3:53:15 PM   
liquid22

 

Posts: 108
Joined: 24.Nov.2004
From: Houston
Status: offline
Just an update that dcdiag error is normal if no Windows 2003 domain controllers are present.  Those permissions do not exist on a Win2K DC, only Win2K3 DC's so that may not be the problem.

I would make sure that they are replicating and that they are registered in DNS.  Download and install the 2000 support tools and run dcdiag and see if that reports any errors.

(in reply to liquid22)
Post #: 37
RE: Still not routing e-mails - 22.Jun.2006 4:29:57 PM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
We are in Mixed mode, but both DCs are Windows 2000 SP4.  There are no DCs that are NT 4.0 so I can change this no problem (will this required a reboot?).  The DNS is as follows:

Both DCs (both are the DNS server - Not sure why, but they are) have the "_msdcs" listed and both DNS servers are listed in each of these.  In addition each server has the correct DNS IP addresses setup for the Network Interfaces.  Let me know about the change of the modes (reboot or not) and I will get that completed.  I will also run the replmon as well.

Thanks again,

_____________________________

Texman

(in reply to liquid22)
Post #: 38
RE: Still not routing e-mails - 22.Jun.2006 4:35:54 PM   
liquid22

 

Posts: 108
Joined: 24.Nov.2004
From: Houston
Status: offline
It's not uncommon for DC's to also be DNS servers, especially in smaller setups. 

After you raise the functional level of the domain I do believe it is necessary to reboot all the domain controllers.

When you're at a client PC where you're attempting to configure Outlook when you ping the exchange server (try it both by name and by IP) does it resolve the name to IP and Ip to name?  From both of your DC's I'd also run dcdiag /test:DNS and have it test the DNS functionality and see if any errors are report.

(in reply to texmansru47)
Post #: 39
RE: Still not routing e-mails - 22.Jun.2006 8:19:03 PM   
texmansru47

 

Posts: 68
Joined: 11.Jun.2006
From: Fort Worth, TX
Status: offline
Prior to the upgrade of the mode, the client I'm working on (my PC), I can ping straight IP (doesn't resolve a name) as well as the standard name (usexchsrv) and it resolves the FQDN perfectly... and the ping works.

I cannot process the mode change until about 2:30pm CST today, so I will post when I get that done to see what happens.

Thanks,

Tom

_____________________________

Texman

(in reply to liquid22)
Post #: 40