We were setup with 1 Exchange 2003 Enterprise server (Well call this Server1) functioning as both the frontend/backend rolls. A division of our company moved and was now sitting across the WAN and comlained about slow email (they get huge attachments). So we built an exchange 2003 standard server (Server2). It also functions as both the frontend/backend rolls. The idea is that if that division ever seperated from our company (there has been talk of that for a while) that it would be an easy cut over this way. The 2 servers talk to each other without a problem and we can manage each server via 1 system manager console via either server or non exchange computer such as my desktop.
We have activesync turned on at the global level and users on Server1 can connect via local IP or across the Internet with our firewall NATing the address. We can have SSL on or off as well as require certificates. Users on Server2 however are unable to connect at all. We put a wireless access point on the network and tested multiple devices. They all error out saying they cannot connect to the server. That same device is able to access webmail via the local network 10.2.x.x/exchange or via the internet.
ActiveSync is a global setting and we've looked at all IIS properties and they appear to be the same on both servers.
We have reset the virtual directories following this KB article http://support.microsoft.com/kb/883380
We do have a single Blackberry server that does not share hardware with either exchange server. Users on both exchange servers are able to use BlackBerry devices without issue.
At this point we are at a lose of what else to look for. Does anyone have any thoughts? Is it possible that Exchange does not allow ActiveSync to multiple servers setup the way we have it and requires a true frontend server to do this? I doubt it since webmail does work, but don't know for sure.