Re: local server name
- From: "Karl Burrows" <karlspam@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 31 May 2006 01:16:48 -0400
I think my semantics were poor in my descriptions, but in the proxy
settings, it must match the SSL Certificate exactly. If you used the .local
domain, how are you forwarding to that internal address? Shouldn't your
certificate be the public address (the .com)? If you use the .com for your
SSL, that will forward to your external IP address and you can forward to
the .local server IP address internally. Sounds like you need to have your
certificate provider reissue your certificate to match your .com address. I
use mail.domain.com as the SSL, and requests come to my WAN address and I
forward to the mail.domain.local server. Once you get that resolved, then
you can setup the proxy settings and go back to the login info page of the
wizard and enter your account info and it should then resolve to your local
mail account.
Make sure you cancel your current pending certificate request in IIS and go
through the wizard again to request a new certificate. Forward that file to
your SSL issuer to get your new certificate.
"SP" <na@xxxxxxxxx> wrote in message
news:O$NE4mFhGHA.4304@xxxxxxxxxxxxxxxxxxxxxxx
Hi Karl (and everybody, please jump in)
I'm not able to connect using RPC over HTTP yet. There may some other setup
issues that need to be resolved before doing your steps; however, I copied
and pasted here your steps 1-6. I have some questions relating to Step 4.
-Correct me if I'm wrong. The FQDN mentioned in step 4 is your public FQDN,
right ???
-To match ?? What are we matching ? Is that the Certification Path ?
-Now, assuming we are matching the public FQDN with the Certification Path,
how do I get an SSL certificate to bears my public FQDN ?? Because...right
now, the certification path shown in my SSL certificate is the local FQDN -
my.domain.local.
Thanks
Steve
1. Put in local FQDN for Exchange server;FQDN that matches your SSL certificate;
2. Use local login name (no domain qualifier);
3. Outlook will check name automatically, cancel when it times out;
4. Go to more settings, configure other settings including HTTP Proxy
using
5. Check to use SSL only and check to mutually authenticate (usingmsstd:FQDN on SSL);
6. Once you have done all your configuration for your Exchange setup inMore Settings, go back to first page of Wizard and check name again to have
it resolve.
"Karl Burrows" <karlspam@xxxxxxxxxxxxxxxxxxx> wrote in message
news:eB2LkOIgGHA.3916@xxxxxxxxxxxxxxxxxxxxxxx
Are you using SSL? If so, see my posting a few minutes ago...
"SP" <na@xxxxxxxxx> wrote in message
news:udmOX3DgGHA.4776@xxxxxxxxxxxxxxxxxxxxxxx
Hi
I'm testing my newly installed Exchange server.
Say, from home, I'm running Outlook to connect to Exchange server, I type
the public domain name (ex. mydomain.com) for Microsoft Exchange Server
box,
and after I enter the password, the Microsoft Exchange Server changes (or
resolves) to the internal name of the Exchange server (ie.
server.exchangedomain.local).
This is not correct, right ? I'm thinking it the name should remain as
the
public domain name, right ? If yes, please let me know how I can fix
this.
Thank you
Steve
.
- Follow-Ups:
- Re: local server name
- From: SP
- Re: local server name
- References:
- local server name
- From: SP
- Re: local server name
- From: Karl Burrows
- Re: local server name
- From: SP
- local server name
- Prev by Date: Re: Exchange 2007 Beta1
- Next by Date: Re: Exchange 2007 Beta1
- Previous by thread: Re: local server name
- Next by thread: Re: local server name
- Index(es):
Relevant Pages
|