Hello, Here my config: Microsoft Windows Server 2003, Enterprise Edition x64 - R2 Version 5.2.3790 ServicePack 2 Nu 3790 Type x64 **** Microsoft Exchange Environnement: Exchange Server 2007 Microsoft Corporation Version : 08.01.0263.00 --> I currently have a probleme with the edge Synch. I worked before but since Idid the Edge Subscription (following the procedure: http://www.msexchange.org/articles_tutorials/exchange-server-2007/planning-architecture/uncovering-exchange-2007-edge-transport-server-part3.html) I now get the below pb. So Any new user created can NOT be identify and if a mail from outside come to that new mailbox I got the error message user unknow, however it works internaly. I am using self signed certificate (different certificate from edge and HUB= different thumbprint -->I woudl like to know if there is any way to actualize the synchro to allow news users to work properly? (Update ADAM or Edge??) --> I would be very pleased to get any help to solve my issue [PS]>Start-EdgeSynchronization Result : CouldNotConnect Type : General Name : CN=SERVEX01,CN=Servers,CN=Exchange Administrative Group (FYDIBOHFXxLT),CN=Administrative Groups,CN=comany,CN =Microsoft Exchange,CN=Services,CN=Configuration,DC=comany,DC=intra FailureDetails : The LDAP server is unavailable. StartUTC : 09/04/2010 14:14:55 EndUTC : 09/04/2010 14:14:56 Added : 0 Deleted : 0 Updated : 0 Scanned : 0 TargetScanned : 0 Result : CouldNotConnect Type : General Name : CN=SERVEX02,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=comany,CN =Microsoft Exchange,CN=Services,CN=Configuration,DC=comany,DC=intra FailureDetails : The LDAP server is unavailable. StartUTC : 09/04/2010 14:14:56 EndUTC : 09/04/2010 14:14:56 Added : 0 Deleted : 0 Updated : 0 Scanned : 0 TargetScanned : 0

It seems Edge sync worked before. Have you checked event ID on both hub and edge? if you get certificate expired warning, you will have to create new certificate, and Re-subscribe the Edge Transport server specified in the event description. For more information, see Subscribing the Edge Transport Server to the Exchange Organization.

if your certificate have changed somehow (expired, updated etc) you need to resubscribe the edgesubscribtion again.The same goes if you have added or removed a HUB or Edge server. lasse at humandata dot se, http://anewmessagehasarrived.blogspot.com

Dear, it seems ADAM is unable to connect to LDAP server, could you confirm that you have opened all necessary ports for communication between Internal Servers and Edge Server? (LDAP: Port 50389/TCP Secure LDAP: Port 50636/UDP SMTP: Port 25/TCP Optional: enable RDP: Port 3389/TCP) Secondly check whether your HUB Transport and Edge Transport are using a valid transport certificate or not? if certificate has expired then renew the certificate and re-subscribe the Edge on all Hub Transport Servers. and also check the event log on Edge and Hub to get the actual error/warning, if there is any, do let us know. Regards MYM

Hello, Sorry for the delay.. From the hubcas to the Edge: LDAP: Port 50389/TCP --> OK Secure LDAP: Port 50636/UDP --> OK SMTP: Port 25/TCP --> OK We have planned to resubscribe the edgesubscribtion again this Thursday. I'll keep you posted!

Hi, this problem also same with me: but I cannot get error a certificate expired. after i run command start-edgesyanchronization the email still stuck in queue hub server. Result : Success Type : Recipients Name : CN=KKLWES02,CN=Servers,CN=Exchange Administrative Group (FYDIB OHF23SPDLT),CN=Administrative Groups,CN=rurallink,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rurallink,DC=gov,DC= my FailureDetails : StartUTC : 4/13/2010 1:43:34 PM EndUTC : 4/13/2010 1:43:34 PM Added : 0 Deleted : 0 Updated : 0 Scanned : 1335 TargetScanned : 0 Result : Success Type : Configuration Name : CN=KKLWES02,CN=Servers,CN=Exchange Administrative Group (FYDIB OHF23SPDLT),CN=Administrative Groups,CN=rurallink,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rurallink,DC=gov,DC= my FailureDetails : StartUTC : 4/13/2010 1:43:34 PM EndUTC : 4/13/2010 1:43:34 PM Added : 0 Deleted : 0 Updated : 0 Scanned : 345 TargetScanned : 0 Result : Success Type : Configuration Name : CN=KKLWES02,CN=Servers,CN=Exchange Administrative Group (FYDIB OHF23SPDLT),CN=Administrative Groups,CN=rurallink,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rurallink,DC=gov,DC= my FailureDetails : StartUTC : 4/13/2010 1:43:34 PM EndUTC : 4/13/2010 1:43:34 PM Added : 0 Deleted : 0 Updated : 0 Scanned : 345 TargetScanned : 0 Result : Success Type : Recipients Name : CN=KKLWES02,CN=Servers,CN=Exchange Administrative Group (FYDIB OHF23SPDLT),CN=Administrative Groups,CN=rurallink,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rurallink,DC=gov,DC= my FailureDetails : StartUTC : 4/13/2010 1:43:34 PM EndUTC : 4/13/2010 1:43:34 PM Added : 0 Deleted : 0 Updated : 0 Scanned : 1335 TargetScanned : 0 Result : Success Type : Recipients Name : CN=KKLWES01,CN=Servers,CN=Exchange Administrative Group (FYDIB OHF23SPDLT),CN=Administrative Groups,CN=rurallink,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rurallink,DC=gov,DC= my FailureDetails : StartUTC : 4/13/2010 1:43:34 PM EndUTC : 4/13/2010 1:43:34 PM Added : 0 Deleted : 0 Updated : 0 Scanned : 1335 TargetScanned : 0 Result : Success Type : Configuration Name : CN=KKLWES01,CN=Servers,CN=Exchange Administrative Group (FYDIB OHF23SPDLT),CN=Administrative Groups,CN=rurallink,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rurallink,DC=gov,DC= my FailureDetails : StartUTC : 4/13/2010 1:43:34 PM EndUTC : 4/13/2010 1:43:34 PM Added : 0 Deleted : 0 Updated : 0 Scanned : 345 TargetScanned : 0 Result : Success Type : Configuration Name : CN=KKLWES01,CN=Servers,CN=Exchange Administrative Group (FYDIB OHF23SPDLT),CN=Administrative Groups,CN=rurallink,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rurallink,DC=gov,DC= my FailureDetails : StartUTC : 4/13/2010 1:43:34 PM EndUTC : 4/13/2010 1:43:34 PM Added : 0 Deleted : 0 Updated : 0 Scanned : 345 TargetScanned : 0 Result : Success Type : Recipients Name : CN=KKLWES01,CN=Servers,CN=Exchange Administrative Group (FYDIB OHF23SPDLT),CN=Administrative Groups,CN=rurallink,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=rurallink,DC=gov,DC= my FailureDetails : StartUTC : 4/13/2010 1:43:34 PM EndUTC : 4/13/2010 1:43:34 PM Added : 0 Deleted : 0 Updated : 0 Scanned : 1335 TargetScanned : 0 I also re-subcription a xml file. Please help me to troubleshoot queue email in hub transport. Ezzy

Hi Ezzy, Your question is not same as OP's. Please open a new thread. By the way, if you ask a new question, please provide more information, for example: the error code of mails in the queue. Frank Wang

HEllo, I followed the process to renewed the Edge subscription (Export xml file to the Hubcas etc..) and lost the mail flow. In fact I had to connect to the EMC on the edge and click on "Edge transport" from the left panel. I did then a right click "properties" on the "Edge transport" from the middle panel. The DNS where based on the second Network card... SO I changed it and it came back to normal. I need to also mentioned that I has the service lanmanserver caused me some pb as it suddenly has stopped... Everything is back to normal now. Thanks to everyone for your input and I hope my feedback could help someone. Graig