RE: New server not resolving names.
- From: Rick Boza <rickb@xxxxxxxxxxx>
- To: Exchange List <exchangelist@xxxxxxxxxxxxx>
- Date: Mon, 13 Dec 2004 11:09:53 -0500
When you say the names are not resolving, what is happening exactly? What
error code does the NDR generate (it's either a 400 or 500 level code).
That's a good place to start.
Could they resolve when they were on the 5.5 server?
Does mail flow between the 5.5 and the E2K3 servers?
Is the E2K3 box in the same org, or are you doing a Greenfield installation?
When you say 'moved them over to the domain' it makes me think Greenfield,
so how are you doing that, how are you updating directories, and what are
you expecting to happen that isn't working?
What directory synchronization facility do you have in place?
Don't get caught up in the Exchange versus imail piece, this should be SMTP
mail transfers and what you have on the back end won't matter.
On 12/13/04 10:29 AM, "John Tolmachoff (Lists)"
<johnlist@xxxxxxxxxxxxxxxxxxx> wrote:
> http://www.MSExchange.org/
>
> OH boy, Exchange and Imail. In Exchange 2000, there is a setting "send all
> unresolved users to this server" type setting. Is there such a setting in
> Exchange 5.5?
>
> John Tolmachoff
> Engineer/Consultant/Owner
> eServices For You
>
>
>> -----Original Message-----
>> From: Byron Kendrick [mailto:bkendrick@xxxxxxxxxxxxxxxxx]
>> Sent: Monday, December 13, 2004 7:09 AM
>> To: [ExchangeList]
>> Subject: [exchangelist] New server not resolving names.
>>
>> http://www.MSExchange.org/
>>
>> We have just recently begun the migration of our Exchange 5.5 server to
>> the new W2k3 server. I have moved serveral users over to the domain but I
>> am having a problem with the new server trying to resolve names for
>> students who are not on Exchange. The students email accounts reside on
>> an I-Mail server in a separate untrusted domain. The new server will have
>> to route mail through the SMTP gateway located on a Sun box that holds the
>> aliases table.
>>
>> I will be more than glad to answer any questions.
>>
>> TIA
>> byron
>>
>> ------------------------------------------------------
>> List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
>> Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
>> Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
>> ------------------------------------------------------
>> Other Internet Software Marketing Sites:
>> World of Windows Networking: http://www.windowsnetworking.com
>> Leading Network Software Directory: http://www.serverfiles.com
>> No.1 ISA Server Resource Site: http://www.isaserver.org
>> Windows Security Resource Site: http://www.windowsecurity.com/
>> Network Security Library: http://www.secinf.net/
>> Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
>> ------------------------------------------------------
>> You are currently subscribed to this MSEXchange.org Discussion List as:
>> johnlist@xxxxxxxxxxxxxxxxxxx
>> To unsubscribe visit
> http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
>> Report abuse to listadmin@xxxxxxxxxxxxxx
>
>
> ------------------------------------------------------
> List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
> Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
> ------------------------------------------------------
> Other Internet Software Marketing Sites:
> World of Windows Networking: http://www.windowsnetworking.com
> Leading Network Software Directory: http://www.serverfiles.com
> No.1 ISA Server Resource Site: http://www.isaserver.org
> Windows Security Resource Site: http://www.windowsecurity.com/
> Network Security Library: http://www.secinf.net/
> Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com
> ------------------------------------------------------
> You are currently subscribed to this MSEXchange.org Discussion List as:
> rickb@xxxxxxxxxxx
> To unsubscribe visit http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
> Report abuse to listadmin@xxxxxxxxxxxxxx
Other related posts:
