QGSmith
asked on
iphone connection to the server failed - sbs 2003
Hi
We have a sbs 2003 server with OMA enabled. OMA is working. The use can login into OMA from any domain computer and see his email. Port 25, 80 and 443 is enabled on the (Cisco 800) router firewall. (ISA is not enabled on the server). When we try connect with the iPhone it gives the error "connection to the server failed".
We have deleted and re-created the iPhone account settings.
To access OMA from any Internet connection. We use: https://www.companydomainname.com/oma
My iPhone settings are configured as follows:
Correct email address:
domain: companydoman (not companydomain.local)
Username: username onyl (not email address)
pass: password
server name: www.mycompanydomain.com/oma
Please advise why we are unable to conenct with the "connection to server failed" error
SSL is selected under I-phone account settings.
Thanks
Regards
Quintin
We have a sbs 2003 server with OMA enabled. OMA is working. The use can login into OMA from any domain computer and see his email. Port 25, 80 and 443 is enabled on the (Cisco 800) router firewall. (ISA is not enabled on the server). When we try connect with the iPhone it gives the error "connection to the server failed".
We have deleted and re-created the iPhone account settings.
To access OMA from any Internet connection. We use: https://www.companydomainname.com/oma
My iPhone settings are configured as follows:
Correct email address:
domain: companydoman (not companydomain.local)
Username: username onyl (not email address)
pass: password
server name: www.mycompanydomain.com/oma
Please advise why we are unable to conenct with the "connection to server failed" error
SSL is selected under I-phone account settings.
Thanks
Regards
Quintin
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Make sure you have exchange sp2 installed
ASKER
Resovled! We configured Iphone to choose (other) as mail account setup instead of Exchange account setup. We also choose mail.companydomain.com as the mail server address with SSL enabled. This seem to have worked for us. Thanks for all your help.
Just revisiting this
server name: www.mycompanydomain.com/oma
That should be the DNS of your exchange server. The /oma part is probably what makes that fail.
server name: www.mycompanydomain.com/oma
That should be the DNS of your exchange server. The /oma part is probably what makes that fail.
ASKER
No. I just used mail.mycompanydomain.com for the server name.
Important to have ports: 443,193 and 993 open.
Make sure to setup an OTHER mail accoint on the iphone not and not EXCHANGE account.
I couldn't get the exchange account to work with my server for some reason with ot without SSL.
Important to have ports: 443,193 and 993 open.
Make sure to setup an OTHER mail accoint on the iphone not and not EXCHANGE account.
I couldn't get the exchange account to work with my server for some reason with ot without SSL.
This is not a solution to an ActiveSync issue. Because the author has 993 open to his server, the iPhone is making an IMAP connection when selecting the "other" type account. iPhones will try this type of connection first when using the "other" account type.
I realize this is closed but I fixed my ActiveSync problem tonight by confirming that the Security on my AD user had the check box for Inherited Permissions checked (found after clicking the Advanced button on the Security tab). Before it was checked, I received the "failure to connect to server" each time I attempted to retrieve mail. Each of our users who have reported ActiveSync problems have been found to not have this box checked. As soon as we checked that box and waited for AD to sync the change (about 5 minutes), their problems with getting mail were solved.
Scott
Scott
Also you need to make sure RPC/HTTPS is enabled for ActiveSync to work.
http://www.microsoft.com/windowsmobile/en-us/help/synchronize/activesync45.mspx
http://www.msexchange.org/tutorials/Exchange-2003-Mobile-Messaging-Part1-Microsoft-DirectPush-technology.html