RE: Publishing OWA in ISA 2000
- From: v-edtian@xxxxxxxxxxxxxxxxxxxx (Edward Tian)
- Date: Thu, 29 Sep 2005 09:29:35 GMT
Hi:
Thanks for posting here.
>From the description, I understand that you have web published OWA for your
internal Exchange in Bridging mode. When the external users try accessing
the OWA, they received an error 500 and the page cannot be displayed. If I
have misunderstood your concern, please do let me know.
First could you please tell me if you are using the SBS Server? In SBS
environment, by default the Exchange Server is located in the SBS Server
itself after we complete the whole installation of SBS. In this way, the
CEICW Wizard will automatically publish the OWA/RWW and other components to
the internet.
If your OS is Windows Server 2000/2003 based, I suggest you post this kind
of question to the microsoft.public.isa newsgroup next time. The reason why
we recommend posting appropriately is you will get the most qualified pool
of respondents, and other partners who read the newsgroups regularly can
either share their knowledge or learn from your interaction with us. Thanks
for your understanding!
Here, I would still like to provide you the following suggestions:
Based on my experience, this problem occurs if the fully qualified domain
name (FQDN), the NetBIOS name, or the IP address that ISA Server uses to
connect to the internal Web server that is running Microsoft Internet
Information Services (IIS) does not match the common name of the Web server
certificate that is mapped to the Web site.
Please check the common name of the Web server certificate and change the
Web Publishing Rule on ISA Server to match this name as follows:
1. Open ISA Server MMC
2. Go to Publishing
3. Go toWeb Publishing
4. Right-click the Web publishing rule that you want, and then click
Properties.
5. Click the Action tab.
6. Make sure that the Send original Host Header to the published server
instead of the original one check box is not selected. Note If the Send
original Host Header to the published server instead of the original one
check box is selected, you have to take care the Host Header the external
Client connects to the Published Site matches the CN of the Webserver
Certificate.
7. Under Redirect the request to this internal Webserver, type the correct
common name of the Web server certificate. Note Make sure that the internal
network can correctly resolve the common name of the Web server certificate.
Please feel free to let me know if you have any questions or concerns.
I look forward to your reply. Thank you.
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: Publishing OWA in ISA 2000
| thread-index: AcXEMDQpFnRRUlcqRu+sSIu1F+Hw+w==
| X-WBNR-Posting-Host: 220.234.172.107
| From: =?Utf-8?B?bm9zcGFt?= <nospam@xxxxxxxxxxxxxxxxxxxxxxxxx>
| Subject: Publishing OWA in ISA 2000
| Date: Wed, 28 Sep 2005 06:26:16 -0700
| Lines: 12
| Message-ID: <7F844CEC-E7F7-4660-8CAE-952B1BBE9D2B@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:157117
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Hi:
| I have an exchange in the internal network and SSL enable.
| I have export the private key to ISA. I have also create a web publish
rule
| to publish the OWA in bridging mode.
| When external users access the OWA, it give this error relating to
| certificate and some machines prompt that "the page cannot be display"
|
| 500 Internal Server Error - The target principal name is incorrect.
|
| Internet Security and Acceleration Server
|
| Any help is appreciated.
|
.
- Prev by Date: RE: Strange Exchange problem...
- Next by Date: RE: Connectivity issues
- Previous by thread: RE: Strange Exchange problem...
- Next by thread: RE: Publishing OWA in ISA 2000
- Index(es):
Relevant Pages
|
Loading
