RE: shorten the URL using ISA
- From: v-edtian@xxxxxxxxxxxxxxxxxxxx (Edward Tian)
- Date: Tue, 25 Oct 2005 07:46:49 GMT
Dear Steve:
Thanks for your update.
Yes, since SBS is a highly integrated server, the https://owa.domain.com
has already been used by the default web site. However, you may register
another Host record at your ISP's DNS Server. For example, you can use
https://owa.domain.com for your OWA site and https://www.domain.com for
your default web site.
Note: In this way, we should register both https://owa.domain.com and
https://www.domain.com at the ISP's DNS Server so that these two URLs can
be resolved to the external IP address of your SBS Server.
Please feel free to post back if you have any other questions. I hope to
see you again in the newsgroup.
Have a good day!
Best Regards
Edward Tian(MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
======================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.
Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.
For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Any input or comments in this thread are highly appreciated.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Thread-Topic: shorten the URL using ISA
| thread-index: AcXYny8W1jntT/zkRWmCpyteGxdQJg==
| X-WBNR-Posting-Host: 220.234.174.46
| From: "=?Utf-8?B?U3RldmU=?=" <steve_smith19@xxxxxxxxxxx>
| References: <E3B5A093-ADD5-4CB2-A305-C1822349FFEB@xxxxxxxxxxxxx>
<NoHhkug1FHA.1172@xxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: shorten the URL using ISA
| Date: Mon, 24 Oct 2005 06:31:05 -0700
| Lines: 141
| Message-ID: <B9F216E5-9824-4C7E-A1C1-3EEBBD6E20F1@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.windows.server.sbs
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:164011
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Thanks Edward and Jim.
|
| It seems that I could only publish the OWA site other than the default
web
| site. Anyway, thanks for your help, I have learned a lot.
|
| Steve
|
| "Edward Tian" wrote:
|
| > Dear Steve:
| > Thank you for posting here.
| >
| > From the description, I understand that you want to enable the internet
| > users to access the OWA using https://owa.domain.com and currently the
OWA
| > site can be visited at https://owa.domain.com/exchange. If I have
| > misunderstood your concern, please do let me know.
| >
| > Based on my experience, the objective is achievable. We can perform
this
| > path redirection by using a path redirection on the Path tab in the Web
| > Publishing Rule.
| >
| > Double click the OWA publishing rule, go to the Path tab, Add a new
path as
| > following:
| > External Path: /
| > Internal Path: /Exchange\
| >
| > In the case of OWA publishing, the external path is /* (which
represents
| > all folders and directories on the site) and the internal path is
| > /Exchange\. Notice that you must use a backslash at the end of the path
| > because the OWA Web Publishing Rule Wizard already entered the
/Exchange/
| > path.
| >
| > These path redirections do the following:
| >
| > When the user enters https://owa.domain.com/exchange in the browser to
| > connect to the OWA site, the connection is directed to the /Exchange
folder
| > on the OWA Web site.
| > When the user enters https://owa.domain.com/exchweb, the connection is
| > redirected to the /Exchweb folder on the OWA Web site
| > When the user enters https://owa.domain.com/public, the connection is
| > redirected to the /Public folder on the OWA Web site.
| > When the user enters https://owa.domain.com, the connection is redirect
to
| > the /Exchange folder on the OWA Web site.
| > The reason why this works is because the OWA Web site is kind enough to
| > help users who don't understand the difference between UNC paths and
URLs.
| > The OWA Web site will accept the backslash as a valid request and
convert
| > it on the fly to a forward slash. This allows you to use the Internal
Path
| > statement /Exchange\ and /exchange/* in the Path tab, where it would
| > otherwise not be possible to do this if you had to enter forward
slashes
| > for both entries because the ISA firewall will not allow you to enter
| > multiple path mappings that use the same path prefix.
| >
| > Just to make this clear, the reason why we must enter /Exchange\ in
order
| > to get the redirect is that we already have a redirect for /Exchange/*,
| > which is associated with connections users make when they enter
| > https://owa.domain.com/exchange. We can't enter the same path twice, so
we
| > need to trick the ISA firewall's Web Publishing Rule by using
/Exchange\
| > instead, which is associated connections made to
https://owa.domain.com/.
| >
| > I would like to kindly remind you that this solution is somewhat not
| > feasible in SBS environment. As you know, SBS is a highly integrated
| > server. The OWA is published by the ISA Server together with many other
| > components such as RWW and companyweb. By default, the default web site
can
| > be reached at https://owa.domain.com (If this is your FQDN) which will
case
| > confliction with the OWA site. So, if you do want to achieve this
| > objective, the default web site could NOT be published.
| >
| > Hope the above information helps. Please feel free to let me know if
there
| > is anything I can do for you.
| >
| > Have a nice weekend! :)
| >
| > Best Regards
| > Edward Tian(MSFT)
| > Microsoft CSS Online Newsgroup Support
| >
| > Get Secure! - www.microsoft.com/security
| > ======================================================
| > This newsgroup only focuses on SBS technical issues. If you have issues
| > regarding other Microsoft products, you'd better post in the
corresponding
| > newsgroups so that they can be resolved in an efficient and timely
manner.
| > You can locate the newsgroup here:
| > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx
| >
| > When opening a new thread via the web interface, we recommend you check
the
| > "Notify me of replies" box to receive e-mail notifications when there
are
| > any updates in your thread. When responding to posts via your
newsreader,
| > please "Reply to Group" so that others may learn and benefit from your
| > issue.
| >
| > Microsoft engineers can only focus on one issue per thread. Although we
| > provide other information for your reference, we recommend you post
| > different incidents in different threads to keep the thread clean. In
doing
| > so, it will ensure your issues are resolved in a timely manner.
| >
| > For urgent issues, you may want to contact Microsoft CSS directly.
Please
| > check http://support.microsoft.com for regional support phone numbers.
| >
| > Any input or comments in this thread are highly appreciated.
| > ======================================================
| > This posting is provided "AS IS" with no warranties, and confers no
rights.
| >
| > --------------------
| > | Thread-Topic: shorten the URL using ISA
| > | thread-index: AcXV01xsahYIKFcVRveFbVGuOz1Tfw==
| > | X-WBNR-Posting-Host: 220.234.174.46
| > | From: "=?Utf-8?B?U3RldmU=?=" <steve_smith19@xxxxxxxxxxx>
| > | Subject: shorten the URL using ISA
| > | Date: Thu, 20 Oct 2005 17:07:01 -0700
| > | Lines: 11
| > | Message-ID: <E3B5A093-ADD5-4CB2-A305-C1822349FFEB@xxxxxxxxxxxxx>
| > | MIME-Version: 1.0
| > | Content-Type: text/plain;
| > | charset="Utf-8"
| > | Content-Transfer-Encoding: 7bit
| > | X-Newsreader: Microsoft CDO for Windows 2000
| > | Content-Class: urn:content-classes:message
| > | Importance: normal
| > | Priority: normal
| > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| > | Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
| > | Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:163184
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | Sorry for the typo in the previous post. So create again.
| > | We are using SBS 2003/ISA
| > |
| > | OWA works fine from external network using
| > https://owa.domain.com/exchange,
| > | Is it possible to shorten this url to https://owa.domain.com where it
| > | transfers this to the full url ?
| > |
| > | I think this will be more convenient! Thanks very much for your help.
| > |
| > | Steve
| > |
| > |
| >
| >
|
.
- Prev by Date: Re: Help and Support Center hangs on second search
- Next by Date: Re: ISA 2004 fails to install with SBS 2003 Premium CD
- Previous by thread: RE: SBS2003/ISA2004 question
- Next by thread: RE: Event 257 - PlugPlayManager warning
- Index(es):
Relevant Pages
|
Loading
