RE: OWA Access, You can not be logged in..,........
- From: v-natliu@xxxxxxxxxxxxxxxxxxxx ("Nathan Liu [MSFT]")
- Date: Mon, 05 Sep 2005 06:47:02 GMT
Hello Rob,
Thank you for posting in the SBS newsgroup.
I am sorry for the delayed response due to weekend. Please understand that
the newsgroups are staffed weekdays by Microsoft Support professionals to
answer your systems and applications questions. Your understanding is
greatly appreciated!
According to your description, I understand that you received the error
message "you could not be logged on to outlook web access, ensure that you
username and password are correct", when you try to logon the OWA. If I
have misunderstood your concern, please don't hesitate to let me know.
To narrow down this issue, please perform the below steps:
1. By default, after running CEICW, the component will set the Default
Domain property on the corresponding IIS sub-directories (under
Authentication -> Access Control) as following:
/Exchange/: \
/Microsoft-Server-ActiveSync/: SBS domain name
/OMA/: SBS domain name
However, Exchange 2003 SP1 replaces the OWA logon screen (Program
Files\Exchsrvr\bin\auth\usa\logon.asp) and it caused OWA now to ask for
domain\username instead of simply just the username. To fix this problem
before SBS SP1 comes out, you can edit the SP1 logon.asp or (which is
recommended) just add the domain name in the Exchange virtual directory,
Directory Security, Authentication and access control, Default Domain.
The same goes to the OWA and Server-ActiveSync sub-sites, we can just set
the "SBS domain name" back. This is considering the fact that some PPC or
mobile phone cannot use the reverse backslash character when inputting
credential.
2. When you log on to Microsoft Outlook Web Access (OWA) or Microsoft
Outlook Mobile Access (OMA), If you type "<NetBIOS name of the
domain>\<user alias>" in the User Name field, can you log on to OWA?
3. If you try Basic OWA access, does it work?
4. On the SBS server, open Server Management, click Users, on the right
pane, and double-click a problematic user. On the Exchange Features tab,
under Protocols, is Outlook Web Access enabled?
On the Account tab, click Log On To..., is it set to "The following
computers"? If so, change to "All computers" and check if the user can log
on to OWA.
5. If you disable Forms Based Authentication, does OWA works internally? To
disable Exchange Forms Based Authentication:
A. Open Exchange System Manager.
B. Expand Server, <server name>, Protocols, HTTP
C. Right-click Exchange Virtual Server, Properties. Settings tab.
D. Uncheck Enable Forms Based Authentication. Click OK.
E. Go to a command prompt, type "iisreset" and press ENTER.
I am appreciated your time and cooperation. If anything is unclear, please
feel free to let me know. I am looking forward to hearing from you.
Best regards,
Nathan 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 Access, You can not be logged in..,........
>thread-index: AcWwsiSlii7unSjHQrmGSaNOhgICKw==
>X-WBNR-Posting-Host: 71.29.118.84
>From: =?Utf-8?B?Um9i?= <Rob@xxxxxxxxxxxxxxxxxxxxxxxxx>
>Subject: OWA Access, You can not be logged in..,........
>Date: Sat, 3 Sep 2005 11:06:01 -0700
>Lines: 24
>Message-ID: <406DBB1A-4FD5-43D5-8442-6DFC815C561C@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:150463
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>SBS 2003, when trying to logon to OWA it gives the error "you could not be
>logged on to outlook web access, ensure that you username and password are
>correct"
>
>
>I have installed that patch for the logon name format change. Sp1 was
>install a while back. Everything was fine till I unchecked "anonymous
>authentication" on the default web site, it worked, but unfortunately I
added
>all the sites below it in the default web site directory. Realizing the
>mistake, I renabled anonymous auth. and thats when OWA started with the
>error. Looking at the settings over and over again many many times does
not
>show anything obvious. Remote web desktop still works, internally and
>externally, OWA does not. It is not a port issue. The normal Outlook
client
>works fine.
>
>I have been through the "connect to internet" applet in the "to do" list
>several times, reinstalled the patch twice.
>
>How do i reset the IIS back to defaults? Or is there a easy simple fix for
>this?
>
>This is due to a client that would like to password protect the website.
He
>wants a entry login on his sbs server before seeing the remote web
workplace.
>I am glad I have not attempted this on his box.....
>
.
- Follow-Ups:
- References:
- Prev by Date: Re: Routing question
- Next by Date: RE: Updates 891193 and / or 884032 Fatal Error
- Previous by thread: OWA Access, You can not be logged in..,........
- Next by thread: RE: OWA Access, You can not be logged in..,........
- Index(es):
Relevant Pages
|
Loading
