alanhardisty

You will need a 3rd party App to be able to sync the GAL to the contacts unfortunately. I can't recommend one as I've never used one.

That sounds like the contacts are syncing just fine - there just aren't any contacts to sync. You won't see the GAL - it doesn't sync, but it can be searched. Alan

Still here. Firstly check the contacts are enabled via Setup> Mail, Contacts and Calendars>Select the Account> Is contacts enabled? If not, enable it. If it is, then press the Home button and open up Contacts. Select Groups (Top Left) and see which set of contacts are being displayed. You may want to turn off Suggested contacts and enable Contacts / other contacts folders. If that doesn't solve the problem, then something is very wrong somewhere!!

Well done - it's all in the detail!! Glad you got it working and hopefully it will stay that way. My blog should be there for many years and will get updated with any new info I find, so if you have further problems, please re-visit it. Best wishes

You're welcome - I wouldn't be here if it wasn't for someone posting a link to my blog article! Good news on the progress you made after putting in the different server name. The ASP.NET can be changed happily - but having said that, I have seen some servers work happily with v2.0 so for now please just leave it alone. The 500 error is detailed on my article too - which involves blowing away the Exchange IIS virtual directories and letting Exchange recreate them (follow Method 2 of KB883380 to achieve this). If that doesn't resolve the problem and you still get the 500 error, then you are looking at a DNS problem (most likely) and that is usually only something I can guide you on with hands-on unfortunately. The error basically means that Exchange can't find itself internally using DNS. You are also at the point where Microsoft will no longer support you because Exchange 2003 Extended Support is no more. Hopefully you are planning to migrate to Exchange 2010 then 2013 at some point in the very near future!

The IP Address of the Exchange Server is the Public IP Address that points mail to it from the web (assuming it receives mail directly). You can go to What Is My IP | The IP Address Experts Since 1999 from the Exchange server to see it's Public IP Address if you aren't sure.

PC's will use other protocols to communicate with the server e.g., HTTPS for Outlook (RPC over HTTPS) or SMTP / POP3 / IMAP for non-Exchange accounts. They can't use Activesync. It is basically a protocol developed for mobile communications. No - you won't see it listed under Exchange - it is built-in to the software and isn't something you can add/remove, so therefore you won't see it listed anywhere.

No - nothing is required on any Personal Computer. Activesync is a protocol and is installed on the Exchange server. All mobile devices implement the Activesync Protocl and this allows the communications to take place without the device having to go near a computer. As long as communications are working properly and you get green ticks on the Microsoft test Site, then you should just add the account to the mobile device (iPhone / iPad / Android Device etc) and voila!

It's not the most promising start! Unless you see SUCCESS - then assume the port is either closed, blocked, filtered or some other issue that will cause problems with Activesync. Alan

Exchange 2003 works happily with Activesync, even with SP1, but it works much better and is much easier to configure with SP2 installed. If you run through my blog article page that pantscat posted (Exchange 2003 and Activesync Configuration and Troubleshooting | Alan Hardisty's Blog - All Things IT Related), it should walk you through the settings you need on your server and then help you fix any problems after testing on the test site at https://testexchangeconnectivity.com If after running through my blog article you are still stuck, I should be able to guide you further - but it is likely you have an internal DNS problem if you have exhausted my article. Alan

Incorrect settings in IIS can cause exactly that - I have seen it dozens of times. Please work your way through my blog from the top and check everything, especially that you have Exchange 2003 SP2 installed. Alan

Okay - so the same issue reported, yet the account works! "The following authentication methods are enabled, but they aren't allowed authentication methods for this service. Methods: Negotiate, NTLM" Have you checked my article I linked earlier? http://alanhardisty.wordpress.com/2010/03/05/activesync-not-working-on-exchange-2010-when-inherit-permissions-not-set/

CAS server in Exchange 2003??

Okay - please post the https://testexchangeconnectivity.com results for your manager. Thanks Alan

Is Activesync disabled in Active Directory Users and Computers for this user or is the inherited permissions missing for the user as per my other blog (also applicable to Exchange 2003) and already mentioned in this thread earlier: Activesync Working But Only For Some Users On Exchange 2007 / 2010 « Alan Hardisty's Blog – All Things IT Related Alan

Which bit - the internal config using Wi-Fi or the test using the test tool?

That is still showing: "The following authentication methods are enabled, but they aren't allowed authentication methods for this service. Methods: Negotiate, NTLM" Which may be ISA causing the problem. Can you configure a phone internally using Wi-Fi and have it sync happily? In my blog there is a link to a test tool (AccessmyLAN) which you can download and use to test internally to rule out the ISA server. Please download it and test internally if you can't setup an account on Wi-Fi internally. Alan

Okay - the Domain / Realm could have been fine as they were, but no worries for now. Have you re-tested on https://testexchangeconnectivity.com? If not, please do, if you have, what are the results? Alan

Leave the Connect to the internet Wizard for now and just change your IIS settings for the Microsoft-Server-Activesync virtual directory please.

Okay - let's not worry about ISA right now. Please change the authentication on the Microsoft-Server-Activesync virtual directory as per my earlier comment, run iisreset, re-test and see where you are. Thanks Alan

As you have OWA working, you will have port 443 open, so you can skip that part, but having ISA server will make the process a lot harder. Was ISA configured using the SBS Connect To The Internet Wizard as this auto-creates the ISA rules accordingly correctly or manually created? Alan

Sure - here you go: Exchange 2003 and Activesync Configuration and Troubleshooting « Alan Hardisty's Blog – All Things IT Related Alan

Okay - from your test results: "The following authentication methods are enabled, but they aren't allowed authentication methods for this service. Methods: Negotiate, NTLM" Please use my article and change your Microsoft-Server-Activesync authentication settings as they are incorrect. Once changed, run iisreset from a command prompt and then re-test on the test site. Alan

Is your Exchange 2003 server part of SBS 2003? If not, do you have Forms-Based Authentication (FBA) enabled for OWA (pretty login screen)? If you do, please follow KB817379 (Exchange ActiveSync and Outlook Mobile Access errors occur when SSL or forms-based authentication is required for Exchange Server 2003) and add the Exchange-OMA virtual directory as you have SSL on the Exchange Virtual Directory in IIS and you have to have one with no SSL enabled for Activesync to work properly. If you don't have FBA enabled, please run through my article on my blog that AJWhite1970 posted. Thanks Alan