I am trying to get Exchange active sync to work.

Does OMA work?
https://host.domain.com/oma

Are you using SSL?
If so, when you try to access OMA, do you get a certificate prompt?

Simon.

try this link  http://www.amset.info/exchange/mobile-eas.asp

That page will not help you very much. I forgot it was up there.

Simon.

Sembee,
i did not set up ssl, kind of one step at a time thing.  i do not beleive oma works or i do not know how to find out.  i did try to follow your guide of host.domain.com/oma.  The host is the question, i used the name the mx record points to but got nowhere.  i did go to the system manger and make sure the enable oma was checked.  do i need to do anything else, is the name in the mx record the one i should be using, any ports i got to open, permissions need to be set, dogs need petting?
Thanks

have you tested it from a browser http://www.petri.co.il/configure_oma.htm
443 with ssl is the only port needed opening

If OMA doesn't work, then EAS probably doesn't work either. They share the same backend.

Is this SBS or full product?
Have you got SSL running for Exchange for OWA?

Try using OMA internally from a regular PC: http://servername/oma
You should get a username and password prompt. Enter the username in the format of domain\username
then the password. You should get a plain text version of your mailbox.

Simon.

I do not believe i have ssl running but will check.  I will work though the petre site as well.  below is from dnsstuff and is the only warning in the mail section.  does it effect what i am trying to do?  names changed to protect the stupid (me)  i do know that serveraddress/oma returns get me nowhere.

WARNING: One or more of your mailservers is claiming to be a host other than what it really is (the SMTP greeting should be a 3-digit code, followed by a space or a dash, then the host name). If your mailserver sends out E-mail using this domain in its EHLO or HELO, your E-mail might get blocked by anti-spam software. This is also a technical violation of RFC821 4.3 (and RFC2821 4.3.1). Note that the hostname given in the SMTP greeting should have an A record pointing back to the same server. Note that this one test may use a cached DNS record.

mail.domain.com claims to be non-existent host servername.domain.local:
220 servername.domain.local Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at Tue, 13 Mar 2007 08:26:27 -0400

full product

from a local system using the sever.domain.local/oma address i do get the user name and password prompt.  using the mail.domain.com/oma i get nowhere

what name  in you mx records ?

The error off dnsreport.com is a dns issue - which will not affect this problem.
Do you have the relevant ports open in the firewall? If your email is coming in correctly then the name resolution is working correctly - so you need to look close to home.

If you login locally, do you actually see your mailbox?

Simon.

well maybe this is the issue.  i was advised to use the server name that the world sees our exchange server for mail which i could find in the mx section when looking at dnsstuff.com.  is this the server name i should be using?  if not where do i go to find the server name i need to use to do the server.domain.com/oma?  or are you asking what is the name of our mail server that is in the mx section of the dnsstuff?

when i try using a local computer, on the same network as the server, using the server.domain.local/oma i get the prompt and after inputing username and password i do get the email box for the user.  mail does get through to all of the users from outside and inside.  I guess this goes back to what server name do i use to do the host.server.com/oma.  where do i go to fing the this name?

what ports need to be open through the firewall

443 if your on ssl

what about port 80

if you had a web server you would need 80 open

Ok I opened port 80 and the /oma test worked.  What kind of excitement can I expect by opening this port?

hmmm........thats a new solution can you gety email now

i do not have one of the handhelds with me to test right now but i can use the server.domain.com/oma to get to and see a users email from the internet outside of our network.  this was something that did not work before i opened port 80.  as soon as one of the handhelds come back from lunch i will test this out on a handheld.  so i can also guess that this is working though port 80

EAS and OMA both work over web protocols - so that is why you need to have port 80/443 open.
If you want to test then you should get your hands on the emulator.
http://www.amset.info/pocketpc/emulator.asp

Simon.

you have not ssl functioning right on 443

ok from the handheld i can use the internet explorer and goto server.domain.com/oma i get the user name and password screen and can go further into the mail box.  when i click on the active sync i get error message 0x85010001.  the server address i use in the active sync setup on the hand held is server.domain.com, users name, password the same as i use while doing it though the IE on the handheld.  but i still get sync none error message of 0x8501001

this is what i fouind
Unexpected Exchange mailbox Server error: Server: [server.domain.local] User: [user@domain.com] HTTP status code: [409]. Verify that the Exchange mailbox Server is working correctly.

Ok, following the Link from the event in the event viewer that told me i needed to reset the default virtual directories, i reset the default virtual directories.  then i used the emulator and the sync worked.  I will check with the real handheld on Tuesday.  

Now I am not 100% sure but if you get a sync error code of 0x85010001 I suggest  you follow method one from Microsoft Knowledge Base article 883380.  

Sembee turned me on to looking in the event viewer so I will give him the points.  Sembee I think you have several folks asking about the same error code.  let them know about the Microsoft Knowledge Base article 883380

thanks