Exchange 2007 Edge Transport Server
Hi all, I have a client with a green fields Exchange 2007 enviroment. Part of the enviroment consists of 2x Edge Transport Servers in the DMS, and 2x Hub Transport servers. I can create an edge subscription all ok, and sucessfully process this and start and complete an edge sync. This seems to work fine for several days, and then fails with an error "The supplied credential is invalid." which can be seen when i run Test-EdgeSynchronisation cmd. if i recreate my edge subscription, all works well again for another few days till it fails again. Im still in the process of trying to get more info. I have searched on this and not found anything usefull so far.. any ideas?? Cheers Lucas
February 3rd, 2011 7:45am

Hello Do you have port 50636 open edge server can resolve dns ? Have you checked the certificate? You can also refer to this article for verify the settings http://www.bunkerhollow.com/blogs/matt/archive/2008/06/04/reset-edge-transport-server.aspx Thanks Mhussain
Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2011 11:46am

From within your domain, create a zone. For example, techno.com. Within the zone, add the IP addresses of the edge servers. When you subscribe, hub uses its FQDN to communicate using the connectors. Please post if there are progress with this. Hope this helps.
February 4th, 2011 8:36pm

Hi Mhussain, The ports are open, and the edge server can resolve the HT servers due to host file configuration. HT can resolve edge from DNS. Certificates seem to be ok, i have checked the config etc, also i belive the are fine as everything works for a few days and then stops till a re-subscription has been done. Im really not sure what could be casuing it to die every few days. Cheers
Free Windows Admin Tool Kit Click here and download it now
February 6th, 2011 11:50pm

sorry, just to clarify, your sugesting an additional zone just for the Edge servers? from a name space point of view they are using the same space as the internal AD at the moment. Additionally this would require a reinstall of the Egde Servers yeah?
February 6th, 2011 11:55pm

I doubt very much that a namespace issue will cause this. The Edge server's name is not really that important as long as it is resolvable. I'm not sure why they will start losing credentials. That is a funny one as they are supposed to be kept in sync using the Edge Sync process. Can you confirm that their Windows Time configurations are accurate?Casper Pieterse, Principle Consultant - UC, Dimension Data South Africa, Microsoft Certified Master: Exchange 2007 / 2010
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2011 6:06am

I have checked the time multiple times, and time/date/time zone all all correct and accurate and in sync. the thing that is puzzling is that the sync between BOTH edge transport servers drops.
February 7th, 2011 6:40am

The zone should match the primary dns suffix of your edge. For example, if your edge fqdn is server1.microsoft.com(IP 192.168.1.1), your internal zone should be microsoft.com with a host of 192.168.1.1. Keep us posted.
Free Windows Admin Tool Kit Click here and download it now
February 7th, 2011 6:29pm

I belive i have found the solution... maybe.. ill know tomorrow... http://social.technet.microsoft.com/Forums/en-US/exchangesvrtransport/thread/9a21a34a-e51f-4894-84dd-f043ef788958 the key words are as follows. Check if the "Microsoft Exchange credential service" is running in the EDGE server. If this service is not running while the subscriptuion is done, the HUB server will not be able to replicate the ESRA accounts to the EDGE server and hence after 24 hours(default subscription expiration time), the subscription becomes invalid. i found that the service wouldnt start under local system as it is meant to. Changed it to Local Admin account, and the service started! so, fingers crossed this has resolved the issue. Cheers
February 9th, 2011 5:01am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics