Hi,
Much appreciated if anyone can provide some links or pointers.
Thanks.
Regards,
Ibase
Jon
Much appreciated if anyone can provide some links or pointers.
Thanks.
Regards,
Ibase
Jon
url=/technet/prodtechnQuote:>-----Original Message-----
>Exchange 2000 installs OWA by default. Inside your
network, try
>http://servername/exchange
>and see what you get.
>To make it available to users on the Internet, you need
to open up port 80
>to the server. It's actually best to force it to use SSL
and open port 443
>instead for added security. Have your ISP or whomever
hosts your domain's
>DNS create an A record that points to your public IP (or
you may be able to
>use the record specified for your MX record).
>See
>http://www.microsoft.com/technet/treeview/default.asp?
>This link may work better:
> http://makeashorterlink.com/?A14021832
>> Hi,
>> Much appreciated if anyone can provide some links or
pointers.
>> Thanks.
>> Regards,
>> Ibase
>> Jon
>.
Quote:> Hi,
> Much appreciated if anyone can provide some links or pointers.
> Thanks.
> Regards,
> Ibase
> Jon
http://servername/exchange
and see what you get.
To make it available to users on the Internet, you need to open up port 80
to the server. It's actually best to force it to use SSL and open port 443
instead for added security. Have your ISP or whomever hosts your domain's
DNS create an A record that points to your public IP (or you may be able to
use the record specified for your MX record).
See
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/pr...
ol/exchange/exchange2000/deploy/confeat/e2kowa.asp
for more info (note URL wrap) -
This link may work better:
http://makeashorterlink.com/?A14021832
Quote:> Hi,
> Much appreciated if anyone can provide some links or pointers.
> Thanks.
> Regards,
> Ibase
> Jon
> >-----Original Message-----
> >Exchange 2000 installs OWA by default. Inside your
> network, try
> >http://servername/exchange
> >and see what you get.
> >To make it available to users on the Internet, you need
> to open up port 80
> >to the server. It's actually best to force it to use SSL
> and open port 443
> >instead for added security. Have your ISP or whomever
> hosts your domain's
> >DNS create an A record that points to your public IP (or
> you may be able to
> >use the record specified for your MX record).
> >See
> >http://www.microsoft.com/technet/treeview/default.asp?
> url=/technet/prodtechn
> >ol/exchange/exchange2000/deploy/confeat/e2kowa.asp
> >for more info (note URL wrap) -
> >This link may work better:
> > http://makeashorterlink.com/?A14021832
> >> Hi,
> >> Much appreciated if anyone can provide some links or
> pointers.
> >> Thanks.
> >> Regards,
> >> Ibase
> >> Jon
> >.
> > Is there any way to set up default preferences for OWA?
> > For example, can I set up so that when I come into an OWA
> > calender, that it comes up as a 7 day view as opposed to a
> > 1 day view. Or in the journal, can I change which fields
> > gets shown.
> > >-----Original Message-----
> > >Exchange 2000 installs OWA by default. Inside your
> > network, try
> > >http://servername/exchange
> > >and see what you get.
> > >To make it available to users on the Internet, you need
> > to open up port 80
> > >to the server. It's actually best to force it to use SSL
> > and open port 443
> > >instead for added security. Have your ISP or whomever
> > hosts your domain's
> > >DNS create an A record that points to your public IP (or
> > you may be able to
> > >use the record specified for your MX record).
> > >See
> > >http://www.microsoft.com/technet/treeview/default.asp?
> > url=/technet/prodtechn
> > >ol/exchange/exchange2000/deploy/confeat/e2kowa.asp
> > >for more info (note URL wrap) -
> > >This link may work better:
> > > http://makeashorterlink.com/?A14021832
> > >> Hi,
> > >> Much appreciated if anyone can provide some links or
> > pointers.
> > >> Thanks.
> > >> Regards,
> > >> Ibase
> > >> Jon
> > >.
http://www.whalecommunications.com/whitepapers/
Whether you use our product or someone else's, you should be aware of
the security issues present when deploying OWA.
Joseph Steinberg ---------------------------------------------------------------------------
> http://servername/exchange > and see what you get. > To make it available to users on the Internet, you need to open up port 80 > See > http://www.microsoft.com/technet/treeview/default.asp?url=/technet/pr... > This link may work better: > http://makeashorterlink.com/?A14021832
> > Much appreciated if anyone can provide some links or pointers. > > Thanks. > > Regards,
---------------------------------------------------------------------------
_.._
(_.-.\ Joseph Steinberg
.-, ` Director of Technical Services
.--./ / _.-""-. Whale Communications
'-. (__..-" \
',.__. ,__.-'/ (201) 947-9177 x1511
'--/_.'----'` http://www.whalecommunications.com
> to the server. It's actually best to force it to use SSL and open port 443
> instead for added security. Have your ISP or whomever hosts your domain's
> DNS create an A record that points to your public IP (or you may be able to
> use the record specified for your MX record).
> ol/exchange/exchange2000/deploy/confeat/e2kowa.asp
> for more info (note URL wrap) -
> > Hi,
> > Ibase
> > Jon
1. How to install and configure OWA
Jon,
Im assuming that you are referring to OWA in E2k. If this is the case, OWA
is enabled by default.
Check your IIS server for the /exchange path - it should be enabled already.
Regards
Paul.
3. Installing, configuring, and deploying OWA
4. RPC SERVER TOO BUSY and SERVICES.EXE problem
5. How do i install/configure OWA -
6. Exchange 2000 - Information Store
7. installed exchange Client on power mac I configured it with TCPip
8. Using Seagate Backup with Exchange
9. Installing/configuring ArcserveIT for Exchange Server
10. Installing/Configuring NT Backup on Exchange Server...
11. installed exchange Client on power mac I configured it with TCPip