I face a possible problem with Edge Synchronization on Exchange 2007. Mails can not get routed to- and from my domain, the queues on hub and edge fill up, so I am really desperately searching for a solution.
Setup: Essential Business Server 2008 with Exchange 2007 SP2. German version.
MessagingServer: Hub, Mailbox, CA
All "standard" according to MS installation whitepaper.
Mail-delivery/routing has worked fine ever since initial installation, there was no change in HW, nor was any software recently installed.
When executing Test-EdgeSynchronyzation on hub, this is what I get:
Name : ReefSecurity
LeaseType : 0
ConnectionResult : Failed
FailureDetail : Für den Edge-Transport-Server 'ReefSecurity.Reefd
iver.lan' wurden keine EdgeSync-Anmeldeinformatio
nen auf dem lokalen Hub-Transport-Server gefunden
. Entfernen Sie das Edge-Abonnement, und abonnier
en Sie den Edge-Transport-Server erneut.
LeaseExpiry : 01.01.0001 00:00:00
LastSynchronized : 01.01.0001 00:00:00
CredentialStatus : Skipped
TransportServerStatus : Skipped
TransportConfigStatus : Skipped
AcceptedDomainStatus : Skipped
SendConnectorStatus : Skipped
MessageClassificationStatus : Skipped
RecipientStatus : Skipped
CredentialRecords : Number of credentials 0
FailureDetail plainly translated: "No EdgeSync-logon-information was found for Edge-Transport-Server ... on local Hub-Transport-Server. Delete Edge-subscription, and re-subscribe to Edge-Transport-Sever".
I have done some research, this is what I have tested & done so far:
PING from Edge to Hub works both via IP and FQDN
NSLOOKUP on Edge for FQDN <Hub> delivers IP
NSLOOKUP on Edge for IP <Hub> fails (non-existend domain)
TELNET from Edge to Hub on port 25 works
TELNET from Edge to Hub on port 50636 does not work (blocked by firewall)
PING from Hub to Edge for FQDN fails
PING from Hub to Edge for IP fails
NSLOOKUP on Hub for FQDN <Edge> delivers IP
NSLOOKUP on Hub for IP <Edge> fails (non-existend domain)
TELNET from Hub to Edge via FQDN on port 25 works
TELNET from Hub to Edge via FQDN on port 50636 works
On Edge, the logs show following errors
On Hub, the logs show following errors
MSExchange EdgeSync, 1032
Get-ExchageCertificate | fl shows only valid certificates on Edge and Hub
Several times, I have recreated new subscriptions on Edge and renewed on Hub with- and without deleting the EdgeSubscription on Hub; Start-EdgeSynchronization was executed, however there was no detail-log afterwards like I saw some people had in their threads. This is what I get when executing Start-EdgeSynchronization in Hub:
So far, all actions to no avail - my mail queues keep growing.
Again - mail flow has worked just fine all the time with stated setup; There are no invalid certificates in the ExchangeStore from what I can tell.
I am definitely no AD- and Exchange-expert, so I hope there is someone out there who has seen such a problem before and who can lead me though the necessary steps.
Thanks in advance.