Exchange 2010 Implementation
talking about edge servers - when you import xml file for edge sync in Exchange Management Console you must choose proper AD site.
You can test connection to your Exchange with telnet but you should try SMTP Queues with queue viewer (you can find it in Toolbox in Exchange Management Console) status of delivery between your internal Exchange servers. What smtp domains are your company
using? The same as external dns? Did you configure external MX record for your US domain pointing to your US Edge server?Regards, Konrad Sagala, MCT, MCSE+M, MCITP: Exchange 2007/2010
January 25th, 2012 11:01am
talking about edge servers - when you import xml file for edge sync in Exchange Management Console you must choose proper AD site.
You can test connection to your Exchange with telnet but you should try SMTP Queues with queue viewer (you can find it in Toolbox in Exchange Management Console) status of delivery between your internal Exchange servers. What smtp domains are your company
using? The same as external dns? Did you configure external MX record for your US domain pointing to your US Edge server?Regards, Konrad Sagala, MCT, MCSE+M, MCITP: Exchange 2007/2010
Free Windows Admin Tool Kit Click here and download it now
January 25th, 2012 11:01am
I've been tasked with setting up Exchange 2010 in our organisation, I've very little experience of Exchange install or topology. I'm getting massive information overload and struggling to sift through what I need for my setup, any help would
be greatly appreciated.
We have two domains within a single forest, site a has a single domain that is the root domain of the forest (UK) . Site b has a single domain that is a child domain within the forest (US). within each domain I've configure two AD sites call UK and
US. Each site shows the two DC's physically on that site and the subnet information for that site. I've setup edge servers in the UK and US domain within the DMZ segment and given them public IP access through the firewall along with
public DNS server addresses. I've also named the edge servers with public domain FQDN and I've added references to the internal AD joined hub servers DNS names by adding references to them in the hosts file to allow for DNS resolution. I've also
setup hub servers within UK and US internal LANs
I've update the AD schema to include Exchange across the forest and I've licensed all the exchange servers.
To the best of my knowledge the firewall ports for both sites allow :
port 50636 from hub to edge
port 25 from internet to edge
port 25 from edge to hub
port 25 from hub to edge
port 53 udp from edge to internet
The problems I have are :
UK can't email US and US can't receive email from outside organisation. I'm also not sure how to check the mail flow to ensure internal mail goes from site UK to US via hubs without going out of the organisation and back in again. I'm assuming
the US not receiving email externally is down to edge sync problems, I attempted to recreate the edge sync by creating the xml file on the edge server and copying it the hub. I created the edge sync with the xml file and it worked but when I attempt
to force synchronisation I got an error "The Start-EdgeSynchronization cmdlet can only be run against a Hub Transport server." I'm running it on the hub transport so I'm confused! The UK edge sync seem to have worked correctly. I've not setup certificates
yet on any of the exchange servers BTW!
How do I configure a hub server to only use the edge server within its corresponding site and is there a way to configure the hub server to use the other sites edge server if the local edge server is down?
When I look at the edge subscription on the hub transport of the US domain it appears to be looking at the UK domain AD site and not the US domain site, is this normal? I was hoping that the two exchange implementations would be less reliant upon
each other AD
Thanks for taking the time to read this.
Regards,
Matt
Matt Dolby
January 28th, 2012 7:23am
talking about edge servers - when you import xml file for edge sync in Exchange Management Console you must choose proper AD site.
You can test connection to your Exchange with telnet but you should try SMTP Queues with queue viewer (you can find it in Toolbox in Exchange Management Console) status of delivery between your internal Exchange servers. What smtp domains are your company
using? The same as external dns? Did you configure external MX record for your US domain pointing to your US Edge server?Regards, Konrad Sagala, MCT, MCSE+M, MCITP: Exchange 2007/2010
Free Windows Admin Tool Kit Click here and download it now
January 28th, 2012 11:04am