Exchange 03 to 07
Ok did a few searches and did not see anything and am not sure if i am missing something simple.. I have built an 07 server and we have a 03 server.. I have set up a test users mailbox on my 07 server.. (created user in AD) added mailbox from 07 manager) I can send mail from my 07 user to boxes on the 03 server..and if i cc my 07 users he gets the mail to.. I can not send from my 03 box to my 07 user.. I get mesage delayed and than a few hours laterfailed.. I feel like i may have missed something basic in my set up / connectors / transports.. can someone point me in the right direction..David
June 4th, 2009 3:28am
On the 2007 box open ESM and do a get-routinggroupconnector | fl * then check your source and target transport servers to make sure you have an 03 and 07 server there to send mail between the 2 routing groups.
It sound like the routinggroupconnector from 2003 to 2007 may be incorrectly configured. also whats the error from the failure message you get back?
Sr. Exchange Engineer - Constellation Energy
Free Windows Admin Tool Kit Click here and download it now
June 4th, 2009 5:43pm
I check the routing groups.. looks like my 03 box is there... I have the first group & target group I dont want to copy all the info here but both servers are in there... as each others target & source...
June 4th, 2009 6:55pm
Hi,
I belive that you have given name of exchange 2003 BH server as routing server when installed first exchange 2007 trasnport role.Try to create RGC between 2003 and 2007 using below cmdlet and check further.
New-RoutingGroupConnector -Name "Interop RGC" -SourceTransportServers "Ex2007Hub1.contoso.com" -TargetTransportServers "Ex2003BH1.contoso.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $tru
The first routing group connector is created when the first Hub Transport server role is installed on a computer in the Exchange organization. Before you create additional routing group connectors, perform this procedure on every Exchange2000and Exchange2003server in the organization. When you suppress minor link state updates, the servers that are running Exchange2000and Exchange2003will not mark connectors as down. This procedure will make sure that earlier versions of Exchangewill only use least cost routing and will not try to calculate an alternative route.How to Suppress Link State Updates ::http://technet.microsoft.com/en-us/library/aa996728.aspx
Anil
Free Windows Admin Tool Kit Click here and download it now
June 5th, 2009 4:24pm
Do you have smarthost configured on
Default SMTP
Virtual server of Exchange 2003? This happens if it is configured,
remove
smarthost from there and create a SMTP connector configured with
smarthost for
that mail delivery...
How to find Default SMTP Virtual
Server has
smarthost?
EMS -> Exchange 2003 ->
Protocols ->
SMTP -> Default SMTP Virtual Servers -> Properties -> Delivery
->
Advance -> SmartHost option, make sure nothing is
here...
Amit Tank | MVP: Exchange Server
| MCITP: EMA
| MCSA:
M | http://ExchangeShare.WordPress.com
June 7th, 2009 5:46pm
Yes we have an ironport and the smarthost was on the defualt SMTP.. cleared it and that works...what is the underlying issue with this?
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2009 1:53am
Some caveats are there while configuring SmartHost on SMTP Virutal Server, refer below article for further details...
Configuring a Smart Host on a SMTP Virtual Server
http://technet.microsoft.com/en-us/library/aa996082(EXCHG.65).aspxAmit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com
June 9th, 2009 8:46am
perfect thank you - 1 more question ..I now have 2 connectors... the one i created above and i am assuming the one that was created during install - going both ways on both serversInterOp RGC andMAILSERV to MAILSERVER Is it safe to assume (for cleanup purposes and practice) I can use the cmdlet to remove both connectors and than recreate 1
Free Windows Admin Tool Kit Click here and download it now
June 9th, 2009 3:10pm
Have you created additional routing group connector with New-RoutingGroupConnector? If so yes you can remove just that with below cmdlet.
Remove-RoutingGroupConnector
http://technet.microsoft.com/en-us/library/aa998645.aspxAmit Tank | MVP Exchange Server | MCITP: EMA | MCSA: M | http://ExchangeShare.WordPress.com
June 9th, 2009 3:55pm