I am currently stuck installing an exchange 2007 edge server on a virtual machine with its own NIC. All the other roles have been installed, not including single copy cluster, on my main server running 2003. This is also my DNS, AD, and IIS server. The virtual machine runs off Virtual Server 2005 R2 on the box I previously mentioned. At the moment everything other the the edge server functions properly and I have confirmed the installs on both machines. My problem is that when I try to import the .xml file from my hub transport and run start-edgesynchronization, I get the following error which I have pasted at the end of this post. I have already gone through the preparation process and setup DNS so that both computers can see each other. I have registered both hosts on the DNS server and defined the DNS suffix on the Edge server's NIC. I checked both the boxes (Register this connection's addresses in DNS & Use this connection's DNS suffix in DNS registration). I manually added the hosts to WINDOWS\system32\drivers\etc\hosts on both machines (the hub was defined on the edge and the edge was defined on the hub). I found a post here on TechNet at the following link: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=584666&SiteID=17 I have tried everything within this post to solve this problem with no luck. I removed the certificate from the edge and ran the new-edgesubscription from the hubk. I was concerned that I may have missed a step that called for unregistering the edge server but I cannot find information on this anywhere, so I'm assuming it automatimaticalled unregisters when you run new-edgesubscription. I am able to ping all iterations of both computers as mentioned in the thread which I have pasted below. 1) <hostMachine> 2) thundercleese 3) <hostMachine>.thundercleese.com 4) thundercleese.com I was unable to ping the domain suffix without ".com", is that a problem? Please help! I am losing sleep over this one!Result : CouldNotConnect Type : General Name : (removed for security)FailureDetails : The LDAP server is unavailable. StartUTC : 9/29/2006 3:17:39 AM EndUTC : 9/29/2006 3:17:40 AM Added : 0 Deleted : 0 Updated : 0 Scanned : 0 TargetScanned : 0

I just noticed something strange when I run get-edgesubscription on the hub I get the following: Name: MAILSite: [domain].comDomain: [domain].com now when I run this same command on the edge, I get this: Name: mailSite: Domain [domain].com I have heard that changing the computer to caps can make the difference. What about the lack of the site parameter?

Still having the same problem, any guesses?

Hi, The first thing I would check is DNS. Specifically, check and make sure that the IP address for the Edge Transport server is correct on the DNS server used by the Hub Transport server. By coincidence, I just ran into this problem in my own lab. I forgot that I had mistakenly left the Edge Server enabled for DHCP, and when it booted up, it did not have the same address as before. But it also did not register its new address in DNS because my DNS server only allows secure updates. So I had a stale entry in DNS and after correcting it, and then doing an IPconfig /flushdns on the Hub Transport server, everything worked fine again. As a quick test, ping the Edge Transport server from the Hub Transport server and verify that you have connectivity to the correct server. Also, if there are any firewalls in the way, you'll want to make sure you open the correct ports (50389 and 50636). Hope this helps.

Scott, Nice call. The same thing happened to us, with the old "only allow secure updates". This fixed it. Thanks for your input.

I hadthe same error during Beta 2 testingnot caused by name resolution problems but by a non-standard topology. I have a lab machine that supports EM64T but not VT. So I had the 64-bit version of E2K7 running on host Windows Server 2003 64-bit R2Domain Controller as a typical install (Mailbox, HUBand CAS roles). I set upthe Edge server as a32-bit versionof E2K7 running on a virtual machine (same lab machine). I don't know if it was a 64-bit/32-bit incompatibility, Beta 2, or just the fact the Hub was running on a DC but the Hub could not find the LDAP service on the Edge server. This error drove me crazy for a couple of days. To work around itI set up a dedicated hub transport server (32-bit) on another virtual machine and imported the subscription.Themember server Hub was able to sync no problem. I know this is not anything you would do in production but though it might help someone that was attemptinga similar lab config.

Hello, I am facing the same error as above: We have installed the edge server out of the domain. And we have the recommended setup for the Hub Transport servers. When i run the cmdlet "Get-EdgeSubscriptions" on the edge server, the output is: Name: MyServer Site: Domain:Mydomain.com I am not sure why the "Site" is empty. Is there any configuration that has to be done? Is something wrong, or it's the default behaviour? Regards, Sri

I ended up rebuilding the system and somehow got it working; however, it now pulls up multiple errors. So there is still something I am missing. I have laid out the steps that ended up working to an extent below: Deployed hub on domain controller. Setup new virtual machine connected to NIC ReinstalledOS for edge transporton a workgroup (with identical name to domain) and named computer EDGE (obviously the name is erroneous to the problem, only listed to simplify these steps) Gave it static IP address, registered the FQDN (with suffix) and pointed it to DNS server (also domain controller) Confirmed I was able to ping each machine: - Using FQDN: edge.domain.com from [domain controller] and [domain controller].domain.com from the EDGE machine - Using IP addresses (all static) -Using WINS: EDGE from [domain controller] and [domain controller] from EDGE Installed edge transport role on EDGE After going through the process of exporting the subscription etc. the edge server was able to connect This seemed to work fine for a while, but now is pulling up errors like I said. Any ideas why this would be happening?