Software

Ask something
Discussion Locked

Exchange 5.5 - 2K Migration

0 helpful
11 replies

by surrealx

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Exchange 5.5 - 2K Migration
I have recently introduced an Exchange 2000 server into my one Single 5.5 server environment, with the plan to fully migrate. I moved one mailbox over to the Exchange 2000 server to test that everything would work. The Custom Recipients have been populated over to the Active Directory, and they are all created as disabled users. The problem that I am having is sending e-mail to any external e-mail addresses that are on the same domain of this exchange server for example:
If I send an e-mail to a an e-mail address that exists as a Custom Recipient on the server, but is on the same @company.com domain as the e-mail account of our server, I get the following NDR:
? A configuration error in the e-mail system caused the message to bounce between two servers or to be forwarded between two recipients. Contact your administrator. ?
However when I send to other custom recipients that are not on the same @company.com domain.
If I send to an e-mail address that is not a custom recipient, but is on our @company.com domain I get the following NDR:
The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
However I can sent to all other e-mail addresses that are not Custom Recipients and are not on our @company.com domain.

I exhausted TechNet on this issue, so I am hoping for answers only from people who have had a similar problemand have actually fixed it. But please feel free to post a response if you have a pretty confident idea.

11 replies

by dynamo2003

You mentioned that you disbled the user's account. I don't think that the recipient would receive messages if the user account is dissbled. Try enabling the user accounts and see if it makes any diffrence. The mailbox functions with a valid domain account in Exchange and if the account is disabled then the mailbox can't function.

by a.grogan

In your recipient policy - have a look at what domain you E2K Server is in charge of message delivery to - Suspect it will be - make sure the E2K server is not Responsible for Delivering mail to (it will still deliver locally).

Then on you SMTP Virtual Server make sure that all mail with unresolved recipients are passed put to your 5.5 server.

by surrealx

Answer 2 has fixed half the problem. I am now able to send to e-mail addresses that do not exist within the AD, but do on our company domain. However I am still unable to send to custom recipients on the AD, that are on our Company domain. Answer 1 and 3 were unhelpfull.

by maxwell edison

Please excuse my previous answer. I was researching a solution to a different Exchange question, and I pasted that reply into this question by mistake.

Nonetheless, if you are unable to send mail to custom recipients on AD, perhaps you could look at linking the user to the appropriate Exchange mailbox by using Active Directory Services Interfaces (ADSI). Since it's common to associate a primary Windows account with a mailbox, a Windows account can be linked with a custom recipient. This link is created by storing the security identifier (SID) of the Windows account in an attribute on the object in the directory.

Microsoft article Q251390 titled, "HOW TO: Find Exchange Recipients Associated With an NT Account", discusses that process.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q251390

(REMOVE SPACES from the pasted URL)

The sample code in the article uses ADSI along with a resource kit object from the Platform SDK (Software Development Kit) to find all of the mailboxes linked to a particular Windows NT account.

The following link has further information on the process, including articles, discussions, resources, samples and tools, all related to Active Directory Services Interface.

http://www.slipstick.com/dev/adsi.htm

(REMOVE SPACES from the pasted URL)

Good luck,

Maxwell

This discussion is closed to new replies.