NEED HELP - EXCHANGE ACTIVESYNC (EAS) will not connect to Exchange Server

If I could make a suggestion - 

Exchange Server 2003 and 2007 support TWO methods of connection.

Exchange Protocol and ActiveSync.

Microsoft calls them both "ActiveSync" which can be confusing. There are well known issues with Exchange server 2003. In fact the same problems existed in iOS and Android until many platforms created a more "accepting" mail client with a compatibility mode to recognize Exchange 2003 Activesync vs. "true" ActiveSync.

More times than not, for the folks in this thread indicating a problem, it may be an issue on the server itself. There is one "how to" located here:

http://support.microsoft.com/?kbid=817379

Before people say I didn't read the thread because the same config works on WIndows Phone and other devices, yes, I did. Windows Phone, like iOS and Android, support a multitude of protocols that Surface RT doesn't (POP3 is a good example). So even if you setup your Exchange connection, the Windows Phone client may have negotiated to IMAP instead (you'll get the same connectivity for the most part and IMAP support push and is part of the default Exchange 2003 mobile setup).

This is NOT a domain join issue, but I also believe this may be a configuration matter with your server. It's not that the server is configured incorrectly, just that it needs to be tweaked to be Surface friendly.

My Surface has been running flawlessly, connected to Exchange, since 10 minutes after I unboxed it.

The other stopper, although I seriously doubt this one, is that you've hit the limit on the number of mobile devices the server is allowing per user. I don't believe you can clear this yourself in Exch2k3 - I believe that wasn't available until 2k7. You can try though, if you login to Webmail using the external URL, go to options -> mobile device and you can see all the registered devices and clear them.

For reference, the readout from the Exchange server for my Surface is below:

]

I also hate to say this, but part of the issue may also be some nuances in how Exchange 2003 ActiveSync works. Is it a "bug" for MS to not have in their 2013 mail client support for a server that is a decade old? 

There are a massive number of improvements available in ActiveSync and mobile device management in Exchange Server 2007.

I'm a tad off track by the sounds of it then  :-)

Sorry guys I'm now at a total loss, I really can't explain what I did but mine has been working fine since configuring it earlier last week.

I'm fully updated both from Desktop updates and Store updates. Running Exchange 2010 sp2 with most recent rollup fixes installed to the servers.

Steve

A few seem to be missing the point. It has nothing to do with domain joining or certs. Its about the inability to connect to Exchange. I have 2 servers, 1 2007 and 1 2010. The 2007 is a basic install with no SSL just simple http connections the 2010 is fully SSL'ed with one cert. you should be able to connect via SSL or Non-SSL however I cannot connect either way. I can connect every other device that exists to both servers (iPads, iPhones, Androids, etc) via SSL and Non-SSL.

Once you have an account on the mail app, only got this to happen twice but still doesnt connect, you do have an option for no ssl, so the cert route is a red herring.

I have both a self signed and a third part certificate installed on my front end server with IIS services assigned to the 3rd party one.

An exchange self signed certificate can't be used as there is no way of Win RT to trust the source.

For a certificate to be valid the three main checks are:

A. The FQDN (fully qualified domain name) must match the common name or alternative name in the certificate.

B. The certificate must be in date, not expired and Win RT must have the correct date set.

C. The certificate source must be trusted.

So when looking to resolve issue C above, if you're not wanting to use a paid 3rd party certificate then you must use a company certificate authority and install the companies CA certificate to Win RT so that its trusted. The server admin will need to configure this and dish out a copy of the CA root certificate. A few internet searches may be needed to help setting this up.

All in all certificates is a real pain to manage and can be really confusing. I agree with other comments that a fix is needed to give the option to ignore security issues. Microsoft should look to bring this device in line with other devices to remain competitive.

The information above is given on what I suspect the problem to be - based on what I've read on this thread, apologies if I'm totally off track. 

Best of luck

Steve