• RSS
  • Twitter
  • FaceBook

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

New Exchange 2010 (coexist) Not sending emails

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2010] >> Migration >> New Exchange 2010 (coexist) Not sending emails Page: [1]
Login
Message << Older Topic   Newer Topic >>
New Exchange 2010 (coexist) Not sending emails - 6.Dec.2010 12:54:17 PM   
jharlow

 

Posts: 16
Joined: 20.Apr.2010
Status: offline
Currently we have one Exchange 2003 server and the newly installed exchange 2010 server. Before I create a routing group between the two servers (apparently not created for some reason during install); I want to make sure email is able to be sent out from the new server.  I created a new mailbox and migrated it to the new exchange server. In attempt to send email, it seems to be wanting to go through the old server (the following organization rejected your message: ex03.domain.com). I already configured a new SMTP connection on the new server that points to our anti-virus/spam utility) but it continues to use the old server and of course fails due to authentication issues.  That is for another day. Frankly, I want the new server to send emails instead of routing it through the old server. 

What am I missing?
Post #: 1
RE: New Exchange 2010 (coexist) Not sending emails - 6.Dec.2010 1:37:16 PM   
travis.sheldon

 

Posts: 359
Joined: 16.Sep.2010
Status: offline
Please provide the result from the following from your 2010 hub server

get-sendconnector | fl AddressSpaces,Auth*,*DNS*,Enabled,HomeMtaServerId,Identity,Source*

(in reply to jharlow)
Post #: 2
RE: New Exchange 2010 (coexist) Not sending emails - 6.Dec.2010 2:57:48 PM   
jharlow

 

Posts: 16
Joined: 20.Apr.2010
Status: offline
AddressSpaces                : {SMTP:*;5}
AuthenticationCredential     :
DNSRoutingEnabled            : False
UseExternalDNSServersEnabled : False
Enabled                      : True
HomeMtaServerId              : EX03SERVER
Identity                     : Generic SMTP
SourceIPAddress              : 0.0.0.0
SourceRoutingGroup           : First Routing Group
SourceTransportServers       : {EX03SERVER}

AddressSpaces                : {SMTP:*;1}
AuthenticationCredential     :
DNSRoutingEnabled            : False
UseExternalDNSServersEnabled : False
Enabled                      : True
HomeMtaServerId              : EXCH2010
Identity                     : New SMTP Server
SourceIPAddress              : 0.0.0.0
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {EXCH2010}

(in reply to jharlow)
Post #: 3
RE: New Exchange 2010 (coexist) Not sending emails - 6.Dec.2010 3:26:22 PM   
travis.sheldon

 

Posts: 359
Joined: 16.Sep.2010
Status: offline
It looks like DNS routing isn't enabled..I wonder if the connector is using the 2003 server as a smart host.

please run

get-sendconnector | fl SmartHosts*


Prior to installing Exchange, did you run
quote:

setup /PrepareLegacyExchangePermission

(in reply to jharlow)
Post #: 4
RE: New Exchange 2010 (coexist) Not sending emails - 6.Dec.2010 3:35:24 PM   
jharlow

 

Posts: 16
Joined: 20.Apr.2010
Status: offline
Two smarthosts came up. Both the same which is our Cisco IronPort (spam/virus) solution. 

I did not run that command prior to installation. I did prep AD and upgraded both AD and Exchange to native modes. That command did not come up during the pre-deployment tool.  Setup was set to default...

(in reply to travis.sheldon)
Post #: 5
RE: New Exchange 2010 (coexist) Not sending emails - 6.Dec.2010 4:41:34 PM   
travis.sheldon

 

Posts: 359
Joined: 16.Sep.2010
Status: offline
I would recommend reading the following: http://technet.microsoft.com/en-us/library/aa997914.aspx

You can run setup /PrepareLegacyExchangePermission after an install completes if you forgot to run it before.

I don't think that is causing the issue at hand, but it will cause other issues down the road.

What is the result of the following (Change the target email address):

Test-Mailflow -TargetEmailAddress "test@remotedomain.com" -Verbose


You can also pipe the results to a file

Test-Mailflow -TargetEmailAddress "test@remotedomain.com" -Verbose > \emailtest.txt 

(in reply to jharlow)
Post #: 6
RE: New Exchange 2010 (coexist) Not sending emails - 6.Dec.2010 6:34:45 PM   
jharlow

 

Posts: 16
Joined: 20.Apr.2010
Status: offline
This was in the emailtest.txt


RunspaceId         : 0cdcd9fc-9817-4b77-81fd-dd767024b98c
TestMailflowResult : *FAILURE*
MessageLatencyTime : 00:00:00
IsRemoteTest       : True
Identity           :
IsValid            : True

This is what was the echo on the screen:

[PS] C:\Windows\system32>Test-Mailflow -TargetEmailAddress "xxxx@gmail.com" -Verbose > \emailtest.txt
VERBOSE: [23:13:14.023 GMT] Test-Mailflow : Active Directory session settings for 'Test-Mailflow' are: View Entire
Forest: 'False', Default Scope: 'domain', Configuration Domain Controller: 'wright1.domain',
Preferred Global Catalog: 'wright3.domain', Preferred Domain Controllers: '{ wright3.domain }'
VERBOSE: [23:13:14.038 GMT] Test-Mailflow : Runspace context: Executing user: domain/Power
Users/Administrator, Executing user organization: , Current organization: , RBAC-enabled: Enabled.
VERBOSE: [23:13:14.038 GMT] Test-Mailflow : Beginning processing &
VERBOSE: [23:13:14.069 GMT] Test-Mailflow : Instantiating handler with index 0 for cmdlet extension agent "Admin Au
Log Agent".
VERBOSE: [23:13:14.069 GMT] Test-Mailflow : Current ScopeSet is: { Recipient Read Scope: {{, }}, Recipient Write
Scopes: {{, }}, Configuration Read Scope: {{, }}, Configuration Write Scope(s): {{, }, }, Exclusive Recipient Scope
{}, Exclusive Configuration Scope(s): {} }
VERBOSE: [23:13:14.069 GMT] Test-Mailflow : Searching objects "EXCH2010" of type "Server" under the root "$nul
VERBOSE: [23:13:14.085 GMT] Test-Mailflow : Previous operation run on domain controller 'wright1.domain'.
VERBOSE: [23:13:14.101 GMT] Test-Mailflow : Searching objects "SystemMailbox{890a07b9-83f3-4e82-a700-09d94b593768}"
type "ADSystemMailbox" under the root "$null".
VERBOSE: [23:13:14.101 GMT] Test-Mailflow : Previous operation run on global catalog server 'wright3.domain
VERBOSE: [23:13:14.101 GMT] Test-Mailflow : Admin Audit Log: Entered Handler:Validate.
VERBOSE: [23:13:14.101 GMT] Test-Mailflow : Admin Audit Log: Entered ClassFactory:InitializeConfig.
VERBOSE: [23:13:14.116 GMT] Test-Mailflow : Admin Audit Log: Exited ClassFactory:InitializeConfig.
VERBOSE: Testing mail flow.
VERBOSE: [23:13:14.148 GMT] Test-Mailflow : Resolved current organization: .
VERBOSE: [23:17:14.329 GMT] Test-Mailflow : Admin Audit Log: Entered Handler:OnComplete.
VERBOSE: [23:17:14.344 GMT] Test-Mailflow : Ending processing &

Hmmm..

(in reply to travis.sheldon)
Post #: 7
RE: New Exchange 2010 (coexist) Not sending emails - 6.Dec.2010 8:13:29 PM   
travis.sheldon

 

Posts: 359
Joined: 16.Sep.2010
Status: offline
What's the result of

get-message | fl

(in reply to jharlow)
Post #: 8
RE: New Exchange 2010 (coexist) Not sending emails - 7.Dec.2010 8:55:56 AM   
jharlow

 

Posts: 16
Joined: 20.Apr.2010
Status: offline
[PS] C:\Windows\system32>get-message | fl
RunspaceId        : 0cdcd9fc-9817-4b77-81fd-dd767024b98c
Subject           : Backfill Request
InternetMessageId : <3966D839789EAF4B8DC904916D47E0280E1851@exch2010.domain>
FromAddress       : PublicFolderDatabase0400587658@domain.com
Status            : Ready
Size              : 4.244 KB (4,346 bytes)
MessageSourceName : FromLocal
SourceIP          : 255.255.255.255
SCL               : -1
DateReceived      : 12/6/2010 1:00:54 PM
ExpirationTime    : 12/8/2010 1:00:54 PM
LastError         : There is currently no route to the mailbox database.
RetryCount        : 0
Recipients        :
ComponentLatency  :
MessageLatency    : 18:48:21.7191072
DeferReason       : None
Priority          : Normal
MessageIdentity   : exch2010\Unreachable\46
Queue             : exch2010\Unreachable
Identity          : exch2010\Unreachable\46
IsValid           : True

RunspaceId        : 0cdcd9fc-9817-4b77-81fd-dd767024b98c
Subject           : Backfill Request
InternetMessageId : <3966D839789EAF4B8DC904916D47E0280E1855@exch2010.domain>
FromAddress       : PublicFolderDatabase0400587658@domain.com
Status            : Ready
Size              : 4.213 KB (4,314 bytes)
MessageSourceName : FromLocal
SourceIP          : 255.255.255.255
SCL               : -1
DateReceived      : 12/7/2010 12:50:55 AM
ExpirationTime    : 12/9/2010 12:50:55 AM
LastError         : There is currently no route to the mailbox database.
RetryCount        : 0
Recipients        :
ComponentLatency  :
MessageLatency    : 06:58:20.6513280
DeferReason       : None
Priority          : Normal
MessageIdentity   : exch2010\Unreachable\54
Queue             : exch2010\Unreachable
Identity          : exch2010\Unreachable\54
IsValid           : True
[PS] C:\Windows\system32>

Seems to be reporting issues with Public Folders, which I haven't even gotten too yet.

(in reply to travis.sheldon)
Post #: 9
RE: New Exchange 2010 (coexist) Not sending emails - 7.Dec.2010 9:24:05 AM   
travis.sheldon

 

Posts: 359
Joined: 16.Sep.2010
Status: offline
Generally that error means the routinggroup wasn't created..but your previous update shows the connector was created "Exchange Routing Group (DWBGZMFD01QNBJR)"

I've seen some post that they had to recreate either the public folder database or mailbox database (depending on which wasn't routing) -- I've also see others where the inheritable permission on the databases were removed in ADSI..

http://www.google.com/search?sourceid=chrome&ie=UTF-8&q=There+is+currently+no+route+to+the+mailbox+database.+exchange+2010

Unfortunately you'll have to do a bit of digging :(

(in reply to jharlow)
Post #: 10
RE: New Exchange 2010 (coexist) Not sending emails - 7.Dec.2010 12:59:45 PM   
jharlow

 

Posts: 16
Joined: 20.Apr.2010
Status: offline
Does not look like a permissions issue. I checked ASDI under the Ex03 server and permissions for Exchange Servers and Exchanged Trusted Subsystem was inherited.

I wonder if I should just uninstall and reinstall. Maybe something just got screwed up during the install...

If it matters any, I am getting the following errors in the event log:

The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 ex03.domain in Routing Group CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain in routing tables with the timestamp 12/7/2010 5:07:18 PM.

Cannot find route to Mailbox Server CN=ex03,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain for store CN=Public Folder Store (EX03),CN=First Storage Group,CN=InformationStore,CN=EX03,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain in routing tables with timestamp 12/7/2010 5:07:18 PM. Recipients will not be routed to this store.
Cannot find route to Mailbox Server CN=ex03,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain for store CN=Mailbox Store (ex03),CN=First Storage Group,CN=InformationStore,CN=ex03,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain in routing tables with timestamp 12/7/2010 5:07:18 PM. Recipients will not be routed to this store.

Microsoft Exchange cannot find the route to mailbox database CN=Public Folder Store (ex03),CN=First Storage Group,CN=InformationStore,CN=ex03,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain for public folder hierarchy CN=Public Folders,CN=Folder Hierarchies,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain in routing tables with timestamp 12/7/2010 5:07:18 PM.
No route has been created for public folder hierarchy CN=Public Folders,CN=Folder Hierarchies,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain in routing tables with timestamp 12/7/2010 5:07:18 PM. Recipients will not be routed to this public folder. Check the routing logs for further information.
Microsoft Exchange cannot find a route to the source transport server or home MTA server CN=ex03,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain for connector CN=Generic SMTP,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain in routing tables with timestamp 12/7/2010 5:07:18 PM. Microsoft Exchange is ignoring the source transport server.
The Active Directory topology service could not discover any route to connector CN=Generic SMTP,CN=Connections,CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative Groups,CN=domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=domain in the routing tables with the timestamp 12/7/2010 5:07:18 PM. This connector will not be used.


Again, I believe most of these are related to the lack of the routing group between the two servers. I do not really want the two directly *talking* until I can confirm that email is being sent from the new server...

(in reply to travis.sheldon)
Post #: 11
RE: New Exchange 2010 (coexist) Not sending emails - 7.Dec.2010 3:25:16 PM   
travis.sheldon

 

Posts: 359
Joined: 16.Sep.2010
Status: offline
J,

I really think your issue is due to the legacy prep work not being done for the exchange install (Just the setup /prep commands for legacy)

The servers *should* talk to each other..joining Exchange 2010 to your 03 deployment will not modify the current users until you move them.

I think you should run the legacy prep commands that I linked ealier..the error in event log indicates the issue is with the routing groups not existing for coexistence.

(in reply to jharlow)
Post #: 12
RE: New Exchange 2010 (coexist) Not sending emails - 7.Dec.2010 4:38:54 PM   
jharlow

 

Posts: 16
Joined: 20.Apr.2010
Status: offline
The only one mentioned was the legacyPermission prep. I have done that one without any additional success. The other preps are handled through the setup, although I ran those for general measure (PrepareAD and Prepare Domain) PrepareSchema I did run prior to the install. 

From what I have read, most of these if not all are done during the setup now (2010 SP1) which would make sense, as it only mentioned one (PrepareSchema, I believe) in the Pre_Deployment Analyzer.

(in reply to travis.sheldon)
Post #: 13
RE: New Exchange 2010 (coexist) Not sending emails - 8.Dec.2010 9:57:36 AM   
jharlow

 

Posts: 16
Joined: 20.Apr.2010
Status: offline
Ok. I got emails going out from the new server. I had to remove the Smart Host and just use DNS MX records to send. Not sure why when I used SmartHost it was being rejected by the old server. Probably something odd with the way IronPort works.

So now that emails are going out. It is time for the next step. Getting emails to and from the account from/to the old server.

Get-RoutingGroup /FL does not return any responses. Is it safe to assume I need to create one between the EX03 and EX2010 server?

(in reply to jharlow)
Post #: 14
RE: New Exchange 2010 (coexist) Not sending emails - 8.Dec.2010 10:23:42 AM   
travis.sheldon

 

Posts: 359
Joined: 16.Sep.2010
Status: offline
I would check your ironport to make sure there aren't any ACLs or rules preventing you from communicating via SMTP.

You are correct in the sense of creating the routing group for the servers.

(in reply to jharlow)
Post #: 15
RE: New Exchange 2010 (coexist) Not sending emails - 8.Dec.2010 11:39:12 AM   
jharlow

 

Posts: 16
Joined: 20.Apr.2010
Status: offline
Finally getting somewhere with this thing. Email is now routing between servers. Public Folder issue resolved by using the ADSI tool and OAB moved.  Yeah!

Time to start moving mailboxes then I need to change the MX records and so forth.  Thanks for your help.

(in reply to travis.sheldon)
Post #: 16

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2010] >> Migration >> New Exchange 2010 (coexist) Not sending emails Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter