RE: Exchange 2003 - OWA client connection problem
From: Alan Sun [MSFT] (v-asun_at_online.microsoft.com)
Date: 07/15/04
- Next message: SteveHodd: "RE: Exchange 2003 - OWA client connection problem"
- Previous message: Matthew Tisdel: "RE: connects to old server"
- In reply to: SteveHodd: "Exchange 2003 - OWA client connection problem"
- Next in thread: SteveHodd: "RE: Exchange 2003 - OWA client connection problem"
- Reply: SteveHodd: "RE: Exchange 2003 - OWA client connection problem"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 15 Jul 2004 04:29:39 GMT
Hi Steve,
Thanks for your post.
According to the information in your post, I suggest you first verify the
following setting in IIS:
1. Start the Microsoft Management Console (MMC) IIS snap-in.
2. Right-click Default Web Site, click Properties on the shortcut menu, and
then click the Home Directory tab.
3. Under "When connecting to this resource, the content should come from",
click "A redirection to a URL".
4. In the Redirect to box, type "/exchange" (without the quotation marks).
5. Under "The client will be sent to", click "A directory below this one".
6. Stop and start the Default Web Site.
More info here:
319878 XWEB: How to Make Outlook Web Access the Default Web Site
http://support.microsoft.com/?id=319878
Second, I suggest you use the basic authentication. To do so:
1. Click Start, point to Programs, point to Administrative Tools, and then
click Internet Services Manager.
2. If necessary, click to expand the local computer object, and then click
to expand Web Sites.
3. Right-click Default Web Site, and then click Properties.
4. On the Directory Security tab, under Anonymous access and authentication
control, click Edit.
5. In Authentication Methods, under Authenticated access, click to select
Basic authentication. In Default domain, type your organization's domain
name.
6. Click to clear all other authentication methods.
If the issue persists, please collect the following information:
1. Please test the issue on different client with multiple user accounts.
Does the issue appear on all the situations?
2. Try to access OWA from the Exchange 2003 server directly by pass all the
proxy and firewall.
3. Try to use the URL " http:// Please inform me of the results at your convenience. Have a nice day!
Thanks & Regards
Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
access the OWA.
Alan Sun
Microsoft Online Partner Support
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
|Thread-Topic: Exchange 2003 - OWA client connection problem
|thread-index: AcRpq/pj1blF4yFzTD+VtASDEbmoiw==
|X-WBNR-Posting-Host: 195.25.48.253
|From: =?Utf-8?B?U3RldmVIb2Rk?= <steveHodd@hotmail.com>
|Subject: Exchange 2003 - OWA client connection problem
|Date: Wed, 14 Jul 2004 07:08:03 -0700
|Lines: 37
|Message-ID: <020511BA-E31B-4A85-B0E7-55461DBE00DC@microsoft.com>
|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.exchange.connectivity
|NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 127.0.0.1
|Path: cpmsftngxa06.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
|Xref: cpmsftngxa06.phx.gbl
microsoft.public.exchange.connectivity:96857
|X-Tomcat-NG: microsoft.public.exchange.connectivity
|
|Hi,
|
|I have installed the first Exchange 2003 Server into an existing
Exchange 5.5 organisation.
|I am having problems using Outlook Web Access.
|
|We have 6 Exchange sites, within my local site I have the following
servers.
|Exchange 5.5 Server: NT_BDC1 10.53.7.5
|Exchange 2003 Server: W3-EXCHANGE 10.53.7.202
|
|When I first tried to use OWA by connecting to:
http://w3-exchange/exchange
|I was automatically redirected to: http://nt_bdc1/exchange
|So I have un-installed OWA from the Exchange 5.5 server (NT_BDC1).
|
|Now if I run IE6 on the W3-EXCHANGE server and connect to:
http://w3-exchange/exchange
|I can connect and OWA works correctly.
|
|However if I run IE6 on any other Client PC, I get these results:
| http://w3-exchange Site Under Construction (this I would expect)
| http://w3-exchange/exchange This page can not be displayed
| http://10.53.7.202/exchange OWA connects very slowly and is slow to
use.
|
|- IE6 is configured to use a Proxy Server (but bypass for local
addresses)
|- I've also tried without the Proxy being set.
|- nslookup correctly resolves W3-EXCHANGE to 10.53.7.202
|- The network connection between clients and server is 100mb.
|- You can connect from client to server using Outlook as the client
with no problems.
|- I have installed Exchange Server 2003 SP1, this has made no
difference.
|- I have tried connecting from several different clients.
|- Access to http://w3-exchange/public works correctly on the client
|
|
|Why does IE resolve http://w3-exchange/public but not
http://w3-exchange/exchange ?
|Why is the OWA connection so slow ?
|
|Any help would be appreciated.
|
|Steve Hodd
|
Relevant Pages
... SBS 2003, Exchange 2003, all fully updated. ... OWA came back alive again this moring for no obvious reason. ... request failure can be found in the application event log of the web server. ... one of my web application under Default Web Site by accident. ...
(microsoft.public.exchange.setup)
... There is an article about this on Microsoft web site: ... * I am in OWA, because I asked IIS to match the certificate with my AD ... Exchange system MMC, ... ... I saw that by default, when you create a new web server, ...
(microsoft.public.exchange.connectivity)
... There is an article about this on Microsoft web site: ... * I am in OWA, because I asked IIS to match the certificate with my AD ... Exchange system MMC, ... ... I saw that by default, when you create a new web server, ...
(microsoft.public.exchange2000.connectivity)
... There is an article about this on Microsoft web site: ... * I am in OWA, because I asked IIS to match the certificate with my AD ... Exchange system MMC, ... ... I saw that by default, when you create a new web server, ...
(microsoft.public.exchange2000.protocols)
... There is an article about this on Microsoft web site: ... * I am in OWA, because I asked IIS to match the certificate with my AD ... Exchange system MMC, ... ... I saw that by default, when you create a new web server, ...
(microsoft.public.exchange.misc)