Re: Outlook Web Access / Remote Web Workplace
- From: Joe <joe@xxxxxxxxxxxxxx>
- Date: Wed, 18 Jul 2007 10:17:21 +0100
JAH wrote:
Thank you both for your assistance. I am unable to however ascertain
the appropriate steps to correct this from either of your respones.
Mikael: Do you have any other information on FQDN? I don't know
anything about this.
Kevin: I am unsure how the certificate process works, please explain.
There will be a name by which your IP address can also be reached,
though it may be something generic like dsl-1-2-3-4.isp.net based
on the IP address. It's fairly cheap to lease a domain name which
has some relevance to your company, and the organisation you obtain
the name from will set up a link to your IP address.
So you can now type something like https://mycompany.com/remote into
a web browser to reach RWW, or set up a link on a page to it as you
have done. The certificate used with the RWW and OWA site (which is a
secure one, even if you use http:// to reach it) must agree exactly
with what you type into the browser (before the slash) as that is the
primary reason for secure web sites, so that the user is warned if
they get diverted to a fake site. So you need to re-run the CEICW and
give it the new domain name, and it will make a new certificate based
on that.
Now, a connection to that address will give you the message that the
certificate is not trusted. That's because it was issued by your SBS,
and not by one of the recognised security companies which are programmed
into your browser. If you accept the invitation to inspect the
certificate, you will be given an option to install it if you are
satisfied it is the one you expect to see, and if you install it, the
browser won't complain again. Every time someone connects from a browser
which has not yet had the certificate installed, this must be done. For
most people, that's only once.
A completely separate issue is that you say the users click on a 'mail'
link to a page which 'redirects' to your SBS. This will *always* cause
a browser error message, as I said above, this is exactly the kind of
thing that the secure web site system is intended to warn about. What
you need on your external web page is a direct link, not redirected, to
your SBS using the same address which would be typed in a browser, and
then that message won't happen. This part is all you really need to do
at the moment, as it is possible to continue to access RWW using an IP
address, as long as the certificate also matches that. But it's
generally the more dubious web sites which use only IP addresses, and
for a legitimate business to do so looks a bit unprofessional, to say
the least.
.
- Follow-Ups:
- References:
- Prev by Date: Re: Cant see out to .co.uk from inside my .local domain (forward l
- Next by Date: Re: Maximum size for individual mailbox
- Previous by thread: Re: Outlook Web Access / Remote Web Workplace
- Next by thread: Re: Outlook Web Access / Remote Web Workplace
- Index(es):
Relevant Pages
|
