asked on

Introducing Exchange 2003 server into a Single Domain with a Exchange 2000 domain Controller.

Long story short....I want to remove my old exchange 2000 server because of hardware issues. I purchased a new server which came with Windows 2003 already loaded. As I began to consult technicians I found that Exchange 2000 would not run on Windows 2003. I purchased Exchange 2003 for the new server. Now I upgraded my PDC to Windows 2003 also and correctly followed the process of Forrest Prep & Domain Prep (I only have one domain) and brought the PDC up with few problems. By the way my Exchange 2000 box is also a DC. I loaded Exchange 2003 on my new server and joined it into the domain as a DC with the Exchange 2000 server being the master database(I did the preps in the correct order and also did the Exchange 2003 Management correctly on the exchange 2000 server). In addition I also have Mailsweeper for SMTP loaded on the Exchange 2000 box as well. I changed the Exchange mode from mixed to Native since I have no old Exchange 5.5 or Nt 4.0 servers. Everything appears to be in order but the Exchange boxes will not communicate with each other. I successfully moved a couple of mailboxes but the ones on the new server cannot send or recieve mail. On the 2000 server I am getting this error message every couple of hours in the application viewer with Types 1 thru 4. They are as follows-
Event Type:      Warning
Event Source:      MSExchangeMTA
Event Category:      Directory Access
Event ID:      9302
Date:            4/3/2006
Time:            2:23:34 PM
User:            N/A
Computer:      EXCHANGE
Description:
The transport configuration type 4 for the directory entry CN=MICROSOFT MTA,CN=EXCHANGE,CN=SERVERS,CN=FIRST ADMINISTRATIVE GROUP,CN=ADMINISTRATIVE GROUPS,CN=HBCONET,CN=MICROSOFT EXCHANGE,CN=SERVICES,CN=CONFIGURATION,DC=HBCONET,DC=COM is not one of the supported values. Reconfigure the transport configuration type in the identified directory entry. [BASE IL OPERATOR 24 217] (8)

Any Help would be appreciated,
Chris

Sembee

You do know that is best practise for Exchange to be installed on a member server, not a domain controller? It performs a lot happier on a member server.
If you have brought the Windows 2003 server in as a DC, did you forest prep and domain prep for Windows 2003 beforehand? If not, then you should do so.

Which order did you do the work? Exchange first, or DCPROMO? If it was Exchange first, then you have a broken Exchange installation. The role of the Exchange server should not be changed once it has Exchange installed. I would remove Exchange, DCPROMO the box out, wipe it and rebuild. Do things in the correct order next time.

Is this machine also a global catalog? If it isn't, and it is going to remain a domain controller then it needs to be made a GC.

Ensure that you don't have a smarthost configured on the SMTP VS of the existing Exchange server.
ESM, Servers, <your server>, Protocols, SMTP. Right click on the default SMTP VS and choose Properties. Click on Delivery and then Advanced. Ensure that smart host is clear. If you need to use a smart host for delivery, then use an SMTP Connector instead.

You need to get replication of the traffic sorted before you move any mailboxes, as you need to get the system folders replicating. This article at MS KB explains what you need to do when it comes to removing the original server: http://support.microsoft.com/default.aspx?kbid=307917
At this time, do everything up to, but excluding removing the replicas and removing the original server.

Simon.

HBCONET

ASKER

Yes I'm aware that Exchange should be a member server but don't have that option available and Yes I did dc promo before I loaded Exchange 2003.. But I do have a smart host on the exchange 2000 server listed as 127.0.0.1 for the Mailsweeper for Smtp which is loaded on the same server. You suggested I use a SMTP connector but which server should be configured as the bridgehead?

HBCONET

ASKER

Forgot to tell you the Exchange 2003 is also a GC

Sembee

You can't use 127.0.0.1 as a smart host in a multiple server environment. Therefore you will have to look at the configuration of the Mailsweeper application to see how it works with remote servers.
The bridgehead can be both servers at this time.

Simon.

HBCONET

ASKER

Well I checked my Mimesweeper for SMTP 5.2 product and it is listing on Port 25 and it resides on my new Exchange 2003 server. It is forwarding all mail to the Old Exchange 2000 Server on Port 20025. this is working flawlwessly. I removed all smarthost. My exchange 2000 is sending and recieving ok however I can only send email from my New Exchange 2003 Server but still cannot receive because the two exchanges are not communicating. On the Old Exchange I am still getting Event Id 9302 for Types 1 thru 4 everyday. On the Exchange 2003 server I am getting this error everyday:
Event Type:      Error
Event Source:      MSExchangeFBPublish
Event Category:      General
Event ID:      8276
Date:            4/21/2006
Time:            2:00:09 AM
User:            N/A
Computer:      HBCEXCHANGE
Description:
Site folder could not be opened for duplicate message deletion on virtual machine HBCEXCHANGE. The error number is 0x8004010f.

For more information, click http://www.microsoft.com/contentredirect.asp.
Still trying,
Chris

ASKER CERTIFIED SOLUTION

Sembee

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

HBCONET

ASKER

Simon,
Thanks for you input it looks like the Mailsweeper program was my culprit all along. I have sucessfully moved all the mailboxes and mail is flowing freely. I am proceeding with the removal of the original 2000 Exchange box following the above removal path you mentioned earlier. I still am having some problems with the AOL domain not excepting my mail. It seems to just sit in the Queue for AOL Remote Delivery stating the connection was dropped due to smtp protocol event sink???

Any suggestions
Chris

Sembee

AOL are very picky.
Make sure that your reverse DNS, server name announcement etc are all set correctly.
http://www.amset.info/exchange/dnsconfig.asp

Failing that, you will probably have to use an SMTP Connector to route email via your ISP, at least while you sort it out:
http://www.amset.info/exchange/smtp-connector.asp

Take a look at their postmaster site for more information: http://postmaster.info.aol.com/trouble/

Simon.

HBCONET

ASKER

Thanks,

Chris

HBCONET

ASKER

someone@aol.com on 4/25/2006 10:00 PM
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<mail.hoffmanbeverage.com #5.7.1 smtp;501 5.7.1 This system is not configured to relay mail (r) from <me@hoffmanbeverage.com> to <someone@aol.com> for HBCEXCHANGE.hbconet.com>

HBCONET

ASKER

Sorry,

HBCONET

ASKER

The above message is still being sent as a bounce back even after configuring an smtp connector????

Sembee

You have set the SMTP Connector to use your ISPs server?
If so, you may have to speak to them to see whether you need to authenticate when sending through their server, or whether they need to adjust something at their end. Some ISPs restrict their servers to relay for email addresses they know about.

Simon.

HBCONET

ASKER

ok now the postmaster@hoffmanbeverage is not receving mail and is bouncing back with this message.

cscott@hoffmanbeverage.com
(Was addressed to cscott@hoffmanbeverage.com)
Delivery failed

Unable to deliver to destination domain
AuthHostNotFound

Sembee

Haven't seen that message before.

"AuthHostNotFound" throws next to nothing up in Google. It isn't an Exchange message.

Did you speak to your ISP?

Simon.