RE: OWA stopped working
- From: v-terliu@xxxxxxxxxxxxxxxxxxxx (Terence Liu [MSFT])
- Date: Mon, 04 Jun 2007 08:00:08 GMT
Hello Jens,
Thank you very much for kind update.
I'm glad to hear that things are working correctly for you now.
I'd like to make a summary for this post:
Issue:
=============
Can not log on OWA and get error message about wrong credentials
Resolutions:
=============
1. Please open IIS console on SBS
2. Extend to Web Sites->Default Web Site
3. Right click the Exchange virtual directory, select Properties
4. Click Directory Security tab, Click Edit button under Authentication and
access control
5. Ensure you only tick the Basic authentication (password is sent in clear
text)
Please do not hesitate to post in this great newsgroup if you need any
assistance in the future. I look forward to working with you again.
Thank you and have a nice day,
Best regards,
Terence Liu(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: OWA stopped working
| thread-index: AcekTb5TT7iAkffBRRG1ChChUKv02w==
| X-WBNR-Posting-Host: 207.46.19.168
| From: =?Utf-8?B?SmVucyBXaWxsYWRzZW4=?=
<JensWilladsen@xxxxxxxxxxxxxxxxxxxxxxxxx>
| References: <FFE34891-3363-4206-AE37-872532823CCC@xxxxxxxxxxxxx>
<$3nxOpBpHHA.1144@xxxxxxxxxxxxxxxxxxxxxx>
| Subject: RE: OWA stopped working
| Date: Fri, 1 Jun 2007 06:07:01 -0700
| Lines: 207
| Message-ID: <2F948AF1-BF54-43E2-AFD5-457F20BB95AD@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.2826
| Newsgroups: microsoft.public.windows.server.sbs
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:40904
| NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| X-Tomcat-NG: microsoft.public.windows.server.sbs
|
| Thank you for your prompt response.
|
| The virtual server was set to integrated Windows auth. It is proberbly me
| who has set it that way. when i was trying to implement a PKI
infrastructure.
| But the time ran out and i had to bail the project. some settings the got
| forgotten :(
|
| But thanks
|
| MVH Jens
|
| "Terence Liu [MSFT]" wrote:
|
| > Hello Jens,
| >
| > Thank you for posting here.
| >
| > Please note the newsgroups are staffed weekdays by Microsoft Support
| > professionals. Our goal is to provide a one business day response to
posts.
| >
| > For time critical issues (not business down), we encourage you to
contact
| > CSS directly for more immediate assistance:
| >
| > International Support (non-US/Canada):
| > http://support.microsoft.com/common/international.aspx
| >
| > US and Canada:
| > http://support.microsoft.com/default.aspx?scid=fh;EN-US;OfferProPhone
| >
| > According to your description, I understand that you can not log on OWA
and
| > get error message about wrong credentials. If I have misunderstood the
| > problem, please don't hesitate to let me know.
| >
| > Based on my research, this issue is mostly caused by the wrong CA
assign to
| > OWA web site or the incorrect authentication method assign to OWA web
site.
| > I suggest we try the following steps to see if we can resolve this
issue:
| >
| > Suggestion 1: Run CEICW to reassign the self-sign CA to OWA web site.
| >
| > Go through the follow KB and Rerun CEICW again carefully.
| >
| > How to configure Internet access in Windows Small Business Server 2003
| > http://support.microsoft.com/kb/825763/en-us
| >
| > Detailed steps for your reference:
| >
| > a. On the SBS 2003 Server open the Server Management console. Go to
| > Standard Management\To Do List.
| >
| > b. Click the "Connect to the Internet" link.
| >
| > c. When navigating to the Firewall page, select "Enable firewall" and
click
| > Next (I suppose you have 2 network adapters in SBS 2003).
| >
| > d. On the "Services Configuration" page, select all the items and then
| > click Next.
| >
| > e. On the "Web Services Configuration" page, make sure "Allow access to
the
| > entire Web site from the Internet" is selected. If you select "Allow
access
| > to only the following Web site services from the Internet", make sure
all
| > item in the list are selected. Click Next.
| >
| > f. On the "Web Server Certificate" page, choose to create a new Web
server
| > certificate and then type the public FQDN (your new DNS name) that you
will
| > use to access OWA and RWW (for example, if your public FQDN that you
use to
| > access the sites is www.xyz.com, you should type www.xyz.com as the new
| > certificate name).
| >
| > g. Go through the remaining steps.
| >
| > Then try to access OWA from internal and external.
| >
| > Suggestion 2: Check the authentication method assign to OWA web site:
| >
| > 1. Please open IIS console on SBS
| >
| > 2. Extend to Web Sites->Default Web Site
| >
| > 3. Right click the Exchange virtual directory, select Properties
| >
| > 4. Click Directory Security tab, Click Edit button under Authentication
and
| > access control
| >
| > 5. Ensure you only tick the Basic authentication (password is sent in
clear
| > text)
| >
| > If we can not resolve the issue after we perform the above steps,
please
| > kindly help me collect some information for further investigation:
| >
| > 1. Please capture screenshots on the error messages and send the
pictures
| > to me at v-terliu@xxxxxxxxxxxxx
| >
| > 2. Try to access the OWA via https://localhost/exchange/ on SBS, is it
work?
| >
| > 3. Try to access the OWA via https://SBSServerName/exchange on internal
| > clients, is it work?
| >
| > 4. Collect the IIS log.
| >
| > a. Open IIS snap-in.
| > b. Right click Default Web Site and click Properties.
| > c. Uncheck the "Enable Logging" box and click Apply.
| > d. Go to C:\WINDOWS\system32\LogFiles\W3SVC1 folder and move all files
to a
| > backup location.
| > e. Check "Enable Logging" box and click OK.
| > f. Run IISReset command.
| > g. Reproduce the problem and send the log file in
| > C:\WINDOWS\system32\LogFiles\W3SVC1 folder to me for research.
| >
| > 5. Gather IIS Metabase:
| >
| > 1) Download the IIS Resource Kit tools from the following page:
| >
http://www.microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-
| > B628-ADE629C89499&displaylang=en
| >
| > 2) Install it, run MBExplorer (Metabase Explorer)
| >
| > 3) Right click the "LM" node and choose "Export to file".
| >
| > 4) Specify a file name, specify the password and finish the export.
| >
| > 5) Send the file and the password to v-terliu@xxxxxxxxxxxxxx
| >
| > Hope these steps will give you some help.
| >
| > Thanks and have a nice day!
| >
| > Best regards,
| >
| > Terence Liu(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: OWA stopped working
| > | thread-index: AcejX2sTirYdn3LNTdGuaXv3uRR4gw==
| > | X-WBNR-Posting-Host: 207.46.19.197
| > | From: =?Utf-8?B?SmVucyBXaWxsYWRzZW4=?=
| > <JensWilladsen@xxxxxxxxxxxxxxxxxxxxxxxxx>
| > | Subject: OWA stopped working
| > | Date: Thu, 31 May 2007 01:41:01 -0700
| > | Lines: 16
| > | Message-ID: <FFE34891-3363-4206-AE37-872532823CCC@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.2826
| > | Newsgroups: microsoft.public.windows.server.sbs
| > | Path: TK2MSFTNGHUB02.phx.gbl
| > | Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.sbs:40553
| > | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| > | X-Tomcat-NG: microsoft.public.windows.server.sbs
| > |
| > | Hi
| > |
| > | My OWA has stopped working, even when you login on RWW if you click
on
| > read
| > | "my company mail". The OWA states that it cannot login becaause of
wrong
| > | credentials, but the credentials where good enough for login to RWW.
| > | Nobody in the domain can acces OWA with their normal credentials.
| > |
| > | What could cause this ??
| > |
| > | I have had some problems with an Certificate upgrade, but I cant see
how
| > | this could affect OWA's login
| > |
| > | Can anybody shed some light on this strange problem. We use OWA
regularly
| > so
| > | i have to solve this quickly
| > |
| > | Regards Jens
| > |
| >
| >
|
.
- References:
- RE: OWA stopped working
- From: Terence Liu [MSFT]
- RE: OWA stopped working
- From: Jens Willadsen
- RE: OWA stopped working
- Prev by Date: RE: Default SMTP Virtual Server - Best authentication methods?
- Next by Date: RE: OWA stopped working
- Previous by thread: RE: OWA stopped working
- Next by thread: RE: OWA stopped working
- Index(es):