Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium


Exchange 2003 Connection over HTTPS in Outlook 2007-2010

Posted on 2011-02-28
Medium Priority
Last Modified: 2012-06-27
I've got two (2) Exchange 2003 servers that host our email for our domain.

On the first Exchange box, I am able to connect people to the server on the LAN, as well as via HTTPS with those users who are more remote. iPhone users are able to connect this email server without difficultly. The public name of the server is the same as the local domain name of the server. This machine is called exchange.ourdomain.com

So, our public domain name, ourdomain.com, happens to also be the local windows domain name, ourdomain.com -- I didn't set this up, but this is the way it is.

The second Exchange box, also on the same LAN, has a name exchangesrv.ourdomain.com. I am able to connect users to this server on the LAN, but am having trouble connecting them via HTTPS for those who are remote and want to still use Outlook 2007 or 2010. iPhone users are able to connect this email server without difficultly, as well.

The server has a DIFFERENT public name (but forwarded to the correct IP address) than the local domain name. So, this second server uses, let's say, exchangesrv.ourotherdomain.com, which forward to the IP address necessary. Again, iPhones can connect and do Active Sync with no problem. But not users in Outlook.

This second server has an SSL certificate that appears to be working just fine, but for whatever reason, when I attempt to add the Exchange users's email account in Outlook using Connect using my LAN options, etc.

Any ideas why this might not be working? My head is spinning trying to figure this thing out.
Question by:efoiadmin
  • 6
  • 4
  • 2
  • +1
LVL 74

Expert Comment

by:Glen Knight
ID: 35001219
I am a little confused.

You have 2 servers part of Thessaly domain/exchange org?

If so then you need a front end server, especially if you only have a single IP address.

Author Comment

ID: 35001275
Yes, 2 servers part of the same local domain.
I have set up each one on their own public IP address. Should I set the front-end server box on one or both?
Each of the 2 servers has mailboxes on it.
LVL 12

Expert Comment

ID: 35002443
Ideally you should have a frontend and backend scenario as mentioned by demazter.

Since you are connecting directly to the second box, outlook will look for certificate, do you have a registered cert with fqdn as your second box fqdn?
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why


Author Comment

ID: 35002561
I do have a registered cert with the fqdn for the 2nd box, yes.
LVL 74

Accepted Solution

Glen Knight earned 1336 total points
ID: 35004300
The problem with both servers having mailboxes is that they will not proxy for each other.
If you actually need 2 mailbox servers they you will also need a front end server.  You would then configure a single public IP and A record for the front end server.

This will then automatically proxy for the 2 mailbox servers and negate the need for 2 URL's which is probably quite confusing for your users.
LVL 10

Assisted Solution

JaredJ1 earned 664 total points
ID: 35005629
Demazter is correct in that you should probably have a single Front End server and then your existing two mailbox servers could become backend servers. This would be best practice, however, this will require you to purchase a new certificate and additional server/exchange licenses. There's no reason why you shouldn't be able to get your existing configuration working though.

What are the errors that you are getting? Have you checked to see if RPC over HTTP has been installed on this second server?
LVL 74

Assisted Solution

by:Glen Knight
Glen Knight earned 1336 total points
ID: 35005633
the problem is if they use the wrong server then it will not work, the user will receive an error.

And, I suspect this is what is happening.

Author Comment

ID: 35010501
Some bullet points to clarify the situation:

1. Users do not go to the incorrect address, nor are they confused. There are very few mailboxes on the new server (5 total), and these people have been specifically provided the correct URL. Other users are not brought in on this conversation, so there is no cause for confusion among them.

2. I do have licensing to install/configure another Exchange server to be front-end only, if need be.

3. If I could simply connect over SSL using Outlook to the 2nd server, I wouldn't be asking the question.

4. I have no desire to completely re-configure my environment. That is not at all a viable solution. There must be something small (or big!) that I'm missing to get this working correctly.

Other than the face that I can't get Outlook to remotely connect to the 2nd Exchange box, everything is working well.  We added a second Exchange server because we were running out of disk space on the first one. So, unfortunately, though the setup doesn't meet some people's ideal (or mine, for that matter), this is the environment I am working with.

Thanks in advance for any solutions that help!

I will check on RPC being enabled.

Author Comment

ID: 35010561
RPC is enabled.

Author Comment

ID: 35011214
Does it matter that the FQDN of the local machine is exchangesrv.ourdomain.com and the fqdn of the ssl cert and the ip address are being accessed from exchangesrv.ourOTHERdomain.com?

For iPhones, it doesn't seem to present a problem. Just for Outlook. Webmail continues to work properly though.
LVL 10

Expert Comment

ID: 35017439
The certificate should be fine. iPhones are actually using a different method - they are getting mail via ActiveSync, not RPC over HTTP.

What are the errors you receive when trying to use Outlook remotely?

Author Comment

ID: 35018105
Doh! I had typed up the specific errors, but guess I never pressed Submit!

Here are the typical steps I'm using, and the errors along the way, to setup Outlook for remote access. These steps work on Server1 but not on Server2.

-- Open Outlook to configure new Exchange account
-- Choose manual settings for the account
-- Select Microsoft Exchange or compatible account
-- Enter Server2's FQDN in the Server field: server2.ourdomain.com
-- Enter username in the User Name field: username
-- Click 'More Settings'
-- Select 'Connection' Tab
-- Check 'Connect to Microsoft Exchange using HTTP'
-- Click 'Exchange Proxy Settings' button
-- Enter Server2 FQDN in the https:// field
-- Ensure NTLM Authentication is selected (it is by default)
-- Click 'OK' button
-- Choose 'Security' Tab
-- Check 'Always prompt for logon credentials' box
-- Set 'Logon network security' to Password Authentication (NTLM)
-- Click 'Apply' button
-- Click 'OK' button
[No errors up to this point]
[Now back on Outlook's main 'Server Settings' page, ready to click 'Next']
-- Click 'Next' button
-- Prompt for credentials pops up, and I enter appropriate credentials using ourdomain\username, and the user's network password
-- Press 'OK' button
[Here's where the errors begin]
-- Outlook appears to time out here, screen may go white for a moment, or it appears as though nothing is happening

[ERROR: The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.]

-- Press 'OK' button to click off the error
-- A "mini" server settings dialog appears, and I have a chance to press 'Check Name' if I'd like.
-- Clicking 'Check Name' or 'OK' produces a timeout again... Window title bar displays (Not Responding) while Outlook is checking for stuff.

[ERROR: The name cannot be resolved. The connection to Exchange is unavailable. Outlook must be online or connected to complete this action.] Essentially the same error as above.

After clicking through the errors just to get off the setup screens and get to Finish, opening Outlook then produces the same errors again.
LVL 74

Expert Comment

by:Glen Knight
ID: 35331146
This question has been classified as abandoned and is being closed as part of the Cleanup Program. See my comment at the end of the question for more details.

Featured Post

[Webinar On Demand] Database Backup and Recovery

Does your company store data on premises, off site, in the cloud, or a combination of these? If you answered “yes”, you need a data backup recovery plan that fits each and every platform. Watch now as as Percona teaches us how to build agile data backup recovery plan.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will help to fix the below errors for MS Exchange Server 2016 I. Certificate error "name on the security certificate is invalid or does not match the name of the site" II. Out of Office not working III. Make Internal URLs and Externa…
Often, the users face difficulty in accessing Outlook 2016 PST files on Windows 10 computer. One of the reasons behind it is the improper functioning of MS Outlook when the user tries to open it. MS Outlook suddenly stops working, or it will not op…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
Suggested Courses
Course of the Month14 days, 16 hours left to enroll

578 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question