Why would SourceTransportServers be null? RGC's require source and target entries. Costs are all at 1. Link-state routing updates have been disabled. I did not make RGC's bidirectional but I did create corresponding RGCs in all of the Exchange 2003 RGs to correspond with the RGs on the 2007 side.
Carl Rimmel Lead Server Engineer, Wintel Platform BBDO Detroit ________________________________ From: Michael B. Smith [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 6:41 PM To: MS-Exchange Admin Issues Subject: RE: Cannot send from Exchange 2007 to Exchange 2003 I'm surprised to see SourceTransportServers non-null. Are the costs for all the RGC's the same? Did you disable link-state routing updates? Did you make the RGC's bidirectional? Regards, Michael B. Smith MCSE/Exchange MVP http://TheEssentialExchange.com From: Rimmel, Carl [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 2:38 PM To: MS-Exchange Admin Issues Subject: RE: Cannot send from Exchange 2007 to Exchange 2003 As far as I can tell, I see a perfectly healthy RoutingGroupConnector (see below): TargetRoutingGroup : Addomain Cost : 10 TargetTransportServers : {EX06WDET, EX07WDET, EX05WDET, EX022K3} ExchangeLegacyDN : /o=PentaMark Worldwide/ou=Exchange Administrativ e Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Co nnections/cn=DetroitE2K7 to ADDOMAIN PublicFolderReferralsEnabled : True SourceRoutingGroup : Exchange Routing Group (DWBGZMFD01QNBJR) SourceTransportServers : {EX91WDET, EX01WDET} HomeMTA : Microsoft MTA HomeMtaServerId : EX91WDET MaxMessageSize : unlimited AdminDisplayName : ExchangeVersion : 0.1 (8.0.535.0) Name : DetroitE2K7 to ADDOMAIN DistinguishedName : CN=DetroitE2K7 to ADDOMAIN,CN=Connections,CN=Exc hange Routing Group (DWBGZMFD01QNBJR),CN=Routing Groups,CN=Exchange Administrative Group (FYDIBO HF23SPDLT),CN=Administrative Groups,CN=Addomain, CN=Microsoft Exchange,CN=Services,CN=Configurati on,DC=addomain,DC=org Identity : DetroitE2K7 to ADDOMAIN Guid : 183f4c7c-333a-46ed-a18d-d4621544437c ObjectCategory : addomain.org/Configuration/Schema/ms-Exch-Routin g-Group-Connector ObjectClass : {top, msExchConnector, msExchRoutingGroupConnect or} WhenChanged : 2/25/2008 10:49:55 AM WhenCreated : 2/21/2008 2:26:23 PM OriginatingServer : AD02WDET.addomain.org IsValid : True Carl Rimmel Lead Server Engineer, Wintel Platform BBDO Detroit ________________________________ From: John Cook [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 2:33 PM To: MS-Exchange Admin Issues Subject: RE: Cannot send from Exchange 2007 to Exchange 2003 Have you run Show-RoutingGroupConnector form Powershell? What does it show? John W. Cook System Administrator Partnership For Strong Families 315 SE 2nd Ave Gainesville, Fl 32601 Office (352) 393-2741 x320 Cell (352) 215-6944 Fax (352) 393-2746 MCSE, MCTS, MCP+I,CompTIA A+, N+ From: Rimmel, Carl [mailto:[EMAIL PROTECTED] Sent: Monday, February 25, 2008 2:06 PM To: MS-Exchange Admin Issues Subject: Cannot send from Exchange 2007 to Exchange 2003 We are transitioning from Exchange 2003 to Exchange 2007. We have installed a CAS, HUB Transport and Mailbox server (with HUB Transport role also installed). When the first HUB server was installed, it automatically created the necessary routing group connectors to allow email flow between 2003 and 2007 and it worked fine. We recently deleted these connectors and recreated them as we have multiple routing groups which require new routing group connectors to efficiently route mail. Ever since creating the new connectors, we are only able to receive email from 2003 to 2007 but are unable to send from 2007 to 2003. The Queue Viewer indicates the following: 451 5.7.3 Cannot achieve Exchange Server authentication I have checked to make sure "Integrated Windows Authentication" is checked on the 2003 SMTP virtual servers and they are all checked. Also, all of the 2003 servers are correctly listed as members of the ExchangeLegacyInterop" group. This is happening on every connector we created. Any ideas would be great. Thanks, Carl Please consider the environment before printing this e-mail. This message and any attachments contain information, which may be confidential or privileged. If you are not the intended recipient, please refrain from any disclosure, copying, distribution or use of this information. Please be aware that such actions are prohibited. If you have received this transmission in error, kindly notify us by e-mail to [EMAIL PROTECTED] We appreciate your cooperation. ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
