bdorsey63
asked on
Windows SBS 2008 and Mobile 6 certificate issue
I have an issue I need help with on Small Business server 2008 and Windows Mobile. I am trying to sync over the internet.
I am running the following:
SBS 2008 64bit
Exchange 2007 (thebuildt in version)
Self signed certificate
Windows mobile 6.2 on a Samsung I 760
The SBS server is behind a firewall, and I am port forwarding 443 from the firewall to the internal SBS server address.
I have followed the MS document for Over the air sync, and it keeps failing with a certificate error.
http://wmexchangesetup.com/Solution.aspx?tag=64%2c65%2c54%2c59%2c60%2c61%2c39%2c80%2c82%2c83
I have added the cert using the package. I have tried manually adding the certificate.
Nothing seems to work.
OWA is working andI can login with the password and user id, from the "mobile id"
Where do I start trouble shooting this problem?
I am running the following:
SBS 2008 64bit
Exchange 2007 (thebuildt in version)
Self signed certificate
Windows mobile 6.2 on a Samsung I 760
The SBS server is behind a firewall, and I am port forwarding 443 from the firewall to the internal SBS server address.
I have followed the MS document for Over the air sync, and it keeps failing with a certificate error.
http://wmexchangesetup.com/Solution.aspx?tag=64%2c65%2c54%2c59%2c60%2c61%2c39%2c80%2c82%2c83
I have added the cert using the package. I have tried manually adding the certificate.
Nothing seems to work.
OWA is working andI can login with the password and user id, from the "mobile id"
Where do I start trouble shooting this problem?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I read the article. In it it states:
mail.example.com (this is the common name, the name that your MX records point to will be used for OWA,IMAP/POP3/SMTP and Exchange ActiveSync - plus it is the reverse DNS record on your static IP address)
I am not using this SBS server on the internet directly. And my MX record points to a different ip address, than where my SBS server is located.
The MX records points to an outsourced IP address at a hosting company. I relay outbound emal thru them. And I use the pop connector to get the email from the remote accounts.
The ip address for my firewall currently does not resolve to my domian name. It is a business level IP address I get from quest, into my business location. I am forwarding 443 traffic to my internal exchange server. I was hoping to just use an IP address to active sync, and not a resolved domain name.
Is it still possible to Over the air sync with the way I have it setup.
mail.example.com (this is the common name, the name that your MX records point to will be used for OWA,IMAP/POP3/SMTP and Exchange ActiveSync - plus it is the reverse DNS record on your static IP address)
I am not using this SBS server on the internet directly. And my MX record points to a different ip address, than where my SBS server is located.
The MX records points to an outsourced IP address at a hosting company. I relay outbound emal thru them. And I use the pop connector to get the email from the remote accounts.
The ip address for my firewall currently does not resolve to my domian name. It is a business level IP address I get from quest, into my business location. I am forwarding 443 traffic to my internal exchange server. I was hoping to just use an IP address to active sync, and not a resolved domain name.
Is it still possible to Over the air sync with the way I have it setup.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Activesync will work using an IP address but activesync only needs port 443 pen and forwarded to work so you are there nearly.
I would setup an fqdn in dns and setup a certificate using the fqdn.
I would setup an fqdn in dns and setup a certificate using the fqdn.
ASKER
Akhater,
"I read the article. In it it states:
mail.example.com (this is the common name, the name that your MX records point to will be used for OWA,IMAP/POP3/SMTP and Exchange ActiveSync - plus it is the reverse DNS record on your static IP address)"
That was a quote from the document.
"I read the article. In it it states:
mail.example.com (this is the common name, the name that your MX records point to will be used for OWA,IMAP/POP3/SMTP and Exchange ActiveSync - plus it is the reverse DNS record on your static IP address)"
That was a quote from the document.
ASKER
Thanks for the help.
The last problem was the FQDN , I had to add an A record to DNS and it worked.
I did not use a 3rd party certificate. I used the internal. SBS creates a "packaged certificate." This is not the certificate that worked on the mobile. The mobile certificate must match the OWA cert. In my case, remote.xxxx.com
The last problem was the FQDN , I had to add an A record to DNS and it worked.
I did not use a 3rd party certificate. I used the internal. SBS creates a "packaged certificate." This is not the certificate that worked on the mobile. The mobile certificate must match the OWA cert. In my case, remote.xxxx.com
If you get a 3rd party certificate you will need to do nothing on WM, if you install your own CA then you will need to d/l the root CA certificate and install it on WM just by double click on it.
OWA is working but Outlook Anywhere/Active sync won't work