Outlook 2003 and Exchange 2003 connectivity issues after Active Directory Upgrade
Hi,
We have a non-profit school who just ran the AD upgrade on our Windows 2003 Servers. Most things seem to work fine except Outlook client cannot connect to the exchange server.
Here was the previous setup:
All servers were Windows 2003 R2 with current SP's
One Forest, One Domain, One DC.
Server DC01 - AD + DNS + Global Catalog Server ( 10.0.0.4 ) ( This is the old DC+DNS )
Server DHCP ( 10.0.0.5 ) ( This is the DHCP server )
Server Exchange ( Exchange 2003 ) (10.0.0.10) ( This is the exchange server )
Server DC1 ( 10.0.0.6 ) ( This is the new DC and DNS )
Ran the ADPREP(Forestprep, DomainPrep, RODCPREP ) on the old DC01 server. ( No errors )
Logged on the NonMember Windows 2008 64Bit server and added the role of Active Directory Domain Services. Ran the Active Directory Domain Services Installation wizard (dcpromo.exe). ( No Errors)
Chose the additional Domain Controller Options with DNS and Global Catalog as defaults.
Moved the FSMO roles to the new DC1
Modified the DHCP server to show the new DNS server name/ip. All clients now have the new DNS server name.
Logged on the old DC01 and attempted to demote it but that failed so ran the /force option and then cleaned up the metadata. Removed the old DC01 from the sites and services, domain controllers OU and DNS.
So, after the restart of all workstations, devices can logon and access shares.
Users can access email via OWA but if they attempt to open Outlook 2003 then it times out and tells us that the exchange server cannot be found and whether you would like to work offline.
I have searched almost everywhere and just cannot find a solution, so need your help.
I have not yet manually promoted the new Global Catalog DC1 to the address site, the domain, or the forest. Do I need to do that ? Since the DC01 was a GC do I need App Server pointed to the offline global catalog server to poin to a live global catalog server ? If I need to do all this then how do I that ?
Thanks
We have a non-profit school who just ran the AD upgrade on our Windows 2003 Servers. Most things seem to work fine except Outlook client cannot connect to the exchange server.
Here was the previous setup:
All servers were Windows 2003 R2 with current SP's
One Forest, One Domain, One DC.
Server DC01 - AD + DNS + Global Catalog Server ( 10.0.0.4 ) ( This is the old DC+DNS )
Server DHCP ( 10.0.0.5 ) ( This is the DHCP server )
Server Exchange ( Exchange 2003 ) (10.0.0.10) ( This is the exchange server )
Server DC1 ( 10.0.0.6 ) ( This is the new DC and DNS )
Ran the ADPREP(Forestprep, DomainPrep, RODCPREP ) on the old DC01 server. ( No errors )
Logged on the NonMember Windows 2008 64Bit server and added the role of Active Directory Domain Services. Ran the Active Directory Domain Services Installation wizard (dcpromo.exe). ( No Errors)
Chose the additional Domain Controller Options with DNS and Global Catalog as defaults.
Moved the FSMO roles to the new DC1
Modified the DHCP server to show the new DNS server name/ip. All clients now have the new DNS server name.
Logged on the old DC01 and attempted to demote it but that failed so ran the /force option and then cleaned up the metadata. Removed the old DC01 from the sites and services, domain controllers OU and DNS.
So, after the restart of all workstations, devices can logon and access shares.
Users can access email via OWA but if they attempt to open Outlook 2003 then it times out and tells us that the exchange server cannot be found and whether you would like to work offline.
I have searched almost everywhere and just cannot find a solution, so need your help.
I have not yet manually promoted the new Global Catalog DC1 to the address site, the domain, or the forest. Do I need to do that ? Since the DC01 was a GC do I need App Server pointed to the offline global catalog server to poin to a live global catalog server ? If I need to do all this then how do I that ?
Thanks
If you did not transfer FSMO rolls to the new domain controller, and you forced the old one down, that could explain your problems.
http://support.microsoft.com/kb/255504
That link will tell you how to seize the rolls in 2000 or 2003. It should be similar in 2008.
http://support.microsoft.com/kb/255504
That link will tell you how to seize the rolls in 2000 or 2003. It should be similar in 2008.
ASKER
The FSMO roles were transferred before the old DC01 was forced out. Used the transfer command.
Should I still run the seize command ?
The new DC1 does show all roles ( Schema Master, Domain Naming Master, PDC, RID Pool Manager, Infrastructure Master ).
Should I still run the seize command ?
The new DC1 does show all roles ( Schema Master, Domain Naming Master, PDC, RID Pool Manager, Infrastructure Master ).
OK. Since your demotion of the old DC didn't go well, have you done anything in ADSI Edit to remove refrences to it?
http://support.microsoft.com/kb/216498
The above link gives instruction for manually removing a DC.
Having a clean active directory is huge for having exchange work right.
http://support.microsoft.com/kb/216498
The above link gives instruction for manually removing a DC.
Having a clean active directory is huge for having exchange work right.
ASKER
I will try that also. Here are some of the symptoms as mentioned earlier also.
Cannot logon to the exchange server as a DomainUser.
Get the following error when Logged on as Local Admin and opening up System Manager:
The RPC server is unavailable
Facility: Win32
ID no: c00706ba
Exchange System Manager
I also have these errors in the Eventviewer:
MSExchangeSA, NSPI Proxy
NSPI Proxy can contact Global Catalog DC1.xx 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 DC1.xx as soon as possible.
Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 2/12/2009
Time: 11:11:52 AM
User: N/A
Computer: EXCHANGE
Description:
LDAP Bind was unsuccessful on directory dc01.xx for distinguished name ''. Directory returned error:[0x51] Server Down.
Event Type: Error
Event Source: MSExchangeSA
Event Category: RFR Interface
Event ID: 9143
Date: 2/12/2009
Time: 11:11:52 AM
User: N/A
Computer: EXCHANGE
Description:
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.
Event Type: Error
Event Source: MSExchangeSA
Event Category: RFR Interface
Event ID: 9074
Date: 2/12/2009
Time: 11:14:30 AM
User: N/A
Computer: EXCHANGE
Description:
The Directory Service Referral interface failed to service a client request. RFRI is returning the error code:[0x3f0].
Cannot logon to the exchange server as a DomainUser.
Get the following error when Logged on as Local Admin and opening up System Manager:
The RPC server is unavailable
Facility: Win32
ID no: c00706ba
Exchange System Manager
I also have these errors in the Eventviewer:
MSExchangeSA, NSPI Proxy
NSPI Proxy can contact Global Catalog DC1.xx 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 DC1.xx as soon as possible.
Event Type: Error
Event Source: MSExchangeAL
Event Category: LDAP Operations
Event ID: 8026
Date: 2/12/2009
Time: 11:11:52 AM
User: N/A
Computer: EXCHANGE
Description:
LDAP Bind was unsuccessful on directory dc01.xx for distinguished name ''. Directory returned error:[0x51] Server Down.
Event Type: Error
Event Source: MSExchangeSA
Event Category: RFR Interface
Event ID: 9143
Date: 2/12/2009
Time: 11:11:52 AM
User: N/A
Computer: EXCHANGE
Description:
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.
Event Type: Error
Event Source: MSExchangeSA
Event Category: RFR Interface
Event ID: 9074
Date: 2/12/2009
Time: 11:14:30 AM
User: N/A
Computer: EXCHANGE
Description:
The Directory Service Referral interface failed to service a client request. RFRI is returning the error code:[0x3f0].
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The system cannot log you on due to the following error:
The RPC server is unavailable