Re: CEICW after loading third party certificate
- From: thejamie <thejamie@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sun, 26 Jul 2009 20:04:02 -0700
IF I understand this correctly...
Assuming the SOA (Start of Authority) is MyServer.MyDomain.com, I would
request a certificate called by the same name,
or put another way,
if the name of my server were REMOTE as in log into \\REMOTE\Users\MyLogin,
then the common name should be remote.mydomain.com.
Taking yet another approach, if the website name is Remote, then the
appropriate common name would also be remote.mydomain.com.
Either way, the ability to verify with an SSL certificate should work.
Furthermore, avoid publishing.mydomain.com because that one is part of the
way that ISA 2004 is setup.
--
Regards,
Jamie
"SuperGumby [SBS MVP]" wrote:
the actual choice of name doesn't much matter and there's a couple of.
choices that can work, depending on how much you want to spend.
simplest: Choose a name for the server and get a cert with that name. The
use of mail.whatever is common for mail servers but not a necessity, and
IMHO not appropriate for SBS as it gives SO MUCH more than simply mail.
remote.etc or location.etc work for me.
harder and more expensive: get multiple certs that apply to each name you
wish to address the server by. mail.etc gets a cert, as does remote.etc, and
each cert is linked to only those functions it serves.
easy but most expensive cert: wildcard cert, the one cert serves all
functions but various functions are accessed using different names.
"thejamie" <thejamie@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0C22E9E9-9171-4598-821A-34E2C43DDA0B@xxxxxxxxxxxxxxxx
Robbin,
I put this on a back burner but am at it again. There are two explanatory
web sites online that still exist for SBS 2003:
http://www.smallbizserver.net/Articles/tabid/266/articleType/ArticleView/ArticleID/283/PageID/470/Default.aspx
and
http://blogs.technet.com/sbs/archive/2007/08/21/how-to-install-a-public-3rd-party-ssl-certificate-on-iis-on-sbs-2003.aspx
The first suggests the use of remote.company.com (as in remote web) and
the
second mail.company.com (as in exchange web and also will match the MX
record). These don't seem like random choices, so I am hoping someone
might
be able to explain why those chose that particular combination.
--
Regards,
Jamie
""Robbin Meng [MSFT]"" wrote:
Hello Jamie,
Thanks for your detailed response.
First, does OWA works internal when using internal client to access it?
and RWW website?
Regarding the KB328917, it is for ISA 2000 not directly for ISA 2004, so
there are some difference on the instructions. I am looking for the
instructions of configuring Web Proxy
Client. Web proxy clients can authenticate with the ISA Firewall, in
contrast to SecureNET clients, which cannot authenticate with the ISA
Firewall.
Moreover, have you tried re-run CEICW and don't choose the Godaddy cert,
instead, use SBS self assigned cert. On the "Web Server Certificate"
page, choose "Create a new
Web server certificate" and key in your public domain name in the box?
Does OWA RWW etc webstie work then?
By the way, I suggest you download and install the ISA server 2004 SP3 on
the SBS 2003 server and then check how it works.
ISA Server 2004 Service Packs
http://technet.microsoft.com/en-us/forefront/edgesecurity/bb734832.aspx
Thanks for your time.
Best regards,
Robbin Meng(MSFT)
Microsoft Online Newsgroup Support
- Follow-Ups:
- Re: CEICW after loading third party certificate
- From: SuperGumby [SBS MVP]
- Re: CEICW after loading third party certificate
- References:
- Re: CEICW after loading third party certificate
- From: SuperGumby [SBS MVP]
- Re: CEICW after loading third party certificate
- Prev by Date: Re: RWW and OWA not working after updates
- Next by Date: Re: CEICW after loading third party certificate
- Previous by thread: Re: CEICW after loading third party certificate
- Next by thread: Re: CEICW after loading third party certificate
- Index(es):
Relevant Pages
|
Loading