Free Microsoft Outlook Resources & Whitepapers

Specific Users unable to login to OWA

We have several users who access OWA from home with no problems. I have just tried to get 2 additional users to start using OWA but they are unable to login. When they go to the OWA URL they get the login dialog box, enter their username and password but then are constantly asked for the username/password until they eventually get a "
HTTP/1.0 401 Unauthorized" message.
Other users can login with no problems. The only difference I can see between the users is that the users who cannot login were originally setup with a firstname.lastname username which we changed to a firstnamelastname username as we had problems and removing the dot seemed to solve those. Otherwise I cannot see any differences.

Any ideas would be great?


Post your answer or comment

comments powered by Disqus
My server crashed and was forced to restore all mailboxes using Backupexec ver 11D.  I selected the option to have BU Exec create the user account during the restor process.  The users that were created by Backupexec are unable to login to OWA they recive a message that states "You could not be logged on to Outlook Web Access. Make sure your domainuser name and password are correct."  However any other user created before or after can access OWA just fine.  comparing the users side by side the settings are identical.  Have tried making user domain admin, member of remote web workplace. to no avail.  Any one with any ideas, short of recreating the users and once agian restoring the mailboxes, would be greatly appericated.

Hi

I have a problem whereby all users in all remote branches are unable to login to outlook. Outlook says exchange is unavailable. Branch offices connect via a VPN and there is no firewall between them, all ports are open.

All users in my head office (same location as exchange) are unaffected.

From the remote PCs, I can telnet to the exchange server on ports 443 and 25 and from exchange I can telnet back to the PCs on port 135 as well as the ports outlook uses at random, something like 46000-60000.

I can ping the exchange server from the PCs.

I can telnet to both the DCs on LDAP 3389.

I can open the autodiscover webpage and successfully get message 600.

From both the DCs, I can telnet and ping the remote PCs and also to exchange.

I have noticed in the Connection Status tool of outlook, that Outlook says connecting to both the global catalog and the exchange server. If I use the DS Access registry key to force outlook to use my global catalog that holds the FSMO roles, it at least establishes a connection to that but exchange remains on status as connecting.

The autodiscovery tool works also and is successful after I make the logonserver the main global catalog server.

I have tried restarting all the servers (2 DCs and 1 exchange 2007 server) in all different sequences and still no luck.

I have verified the certs are correct on exchange. I have also verified the autodiscovery service to be working successfully via powershell. No clear error messages appear in the exchange evert logs to explain the issue.

OWA is fine also, both internall and externally as well as from the affected PCs.

The last thing is if I try to recreate a mail profile and press the 'Check Name' button, it hangs and eventually times out. If I put the DC name in the exchange server field, it resolves correctly.

Has anyone encountered anything like this before?

Thanks in advance

Hi all,
 
Greetings and have happy thanksgiving weekend!!
 
I have the wierd isssue in my Exchange organization.
 
Users who are having the mailboxes at a particular server(say SelSxul-Mailbox store)are not able to login to the OWA.I'm able to open the server in ESM am able to connect to the mailboxes.Since all the users are working remotely am not able to check with the default site intranet -https://..../exchange.
 
What could be the problem...
 
Thanks for ur time in this....
 
 
 
 
 
 

i am facing weird OWA behavior. I have 2 back-end-servers and users on 1 of them can log into OWA but users on the 2nd are not. The users unable to login are not working from internally or externally. What i had to do in the past was open IIS admin and delete OWA hierarchy, under Default Web Site. I deleted;
Exadmin
Exchange
ExchWeb
OMA
Public
after i deleted those i had to restart system attendant service and the hierarchy was re-created and OWA worked fine. This has happened twice on the same server within the past sweveral months. Does anyone have any ideas why this would occur?

I need some guidance please!

I have two CAS servers and one 2003 Front end server. OWA redirects to the front end server for the thousands of users we have before I move the mailboxes over to 2010. I have run into an issue where 30 or so users have to login twice. This happens every time for the users no matter where they are. I use form-based authentication.

What Happens:
When a user logs into the new OWA interface they are redirected to legacy owa but fail and sent to the old OWA form saying “You could not be logged on to OWA. Make sure your domainuser name and password are correct, and then try again.”
I have checked over users attributes to make sure they are correct. It seems to be random users on different database servers. These users are in one domain and no pattern to the OU. I have tried two different 2003 front end servers. Event log says Unknown user name or bad password. Event ID 529. No other errors happen or shown in iis logs. I have had them login regularly like the other users, use UPN, and none of this works.

My next step is to delete a user’s account and recreate/reattach mailbox.

Any thoughts or opinions?

Thanks,
Rob

i have several exchange servers and for users on exchange server1, they are unable to access OWA all of a sudden. I am unable to browse the Exchange folder in IIS! i am not prompted for a user name password as i should be. I get a message "this program cannot display the webpage". any thoughts? this is critical to my company
thanks

Greetings all,

I have completed the installation on Exchange 2013 without any errors but I am unable to login to ECP, when I browse to https://servername/ecp login page comes up fine but when I try to enter domain/username & password I am getting "Your mailbox can't be accessed using the address, please contact helpdesk"
I am using the domain account I have install the Exchange server with and same mailbox is also a admin account on Exchange 2007.
If I try any other mailbox account, still receive the same message. If I type the password or account wrong on purpose for (testing) I get 'User name and password entered is incorrect/'

This is setup on my test bed and the test bed network also running a Exchange 2007.
Exchange 2007 Ent. installed on Windows 2003 R2
Exchange 2013 Ent. installed on Windows 2008 R2
There are 2 DC's and both of them Windows 2008 R2

Also, when I log in to Exchange 2007 MC, I get the following message from the EMC panel:

Warning:
Object domain/Users/DiscoverySearchMailbox {D919BA05-46A6-415f-80AD-7E09334BB852} has been corrupted and it is in an inconsistent state. The following validation errors have accourred:

Warning:
The value of property 'RecipientTypeDetails', 536870912, is not defined in the Enum type 'RecipientTypeDetails'.

I am not sure if this is related to the first issue but I though I would add this too.

Any help would be great.
Thanks!

Hi

I have a problem whereby all users in all remote branches are unable to login to outlook. Outlook says exchange is unavailable. Branch offices connect via a VPN and there is no firewall between them, all ports are open.

All users in my head office (same location as exchange) are unaffected.

From the remote PCs, I can telnet to the exchange server on ports 443 and 25 and from exchange I can telnet back to the PCs on port 135 as well as the ports outlook uses at random, something like 46000-60000.

I can ping the exchange server from the PCs.

I can telnet to both the DCs on LDAP 3389.

I can open the autodiscover webpage and successfully get message 600.

From both the DCs, I can telnet and ping the remote PCs and also to exchange.

I have noticed in the Connection Status tool of outlook, that Outlook says connecting to both the global catalog and the exchange server. If I use the DS Access registry key to force outlook to use my global catalog that holds the FSMO roles, it at least establishes a connection to that but exchange remains on status as connecting.

The autodiscovery tool works also and is successful after I make the logonserver the main global catalog server.

I have tried restarting all the servers (2 DCs and 1 exchange 2007 server) in all different sequences and still no luck.

I have verified the certs are correct on exchange. I have also verified the autodiscovery service to be working successfully via powershell. No clear error messages appear in the exchange evert logs to explain the issue.

Has anyone encountered anything like this before?

Thanks in advance

We have Exchange 2003 SP 2 on Server 2003 with and SMTP connector to our Smart Host Barracuda Spam filter. We filter incoming and outgoing messages.

I am starting to have more and more users report that they are unable to send to addresses externally but other users are able to. These addresses are not the same in any way. When I create a new Outlook profile (2007) for the user the issue is resolved. The message is kicked back almost instantly, not able to catch them in the queues.

We are also seeing Retry and Failure errors for some users trying to send Outlook Appoitments and Appointment updates to a variety of external addresses. Once again, this is a problem with an address for one user but not for another. Unsure if these issues are related. These messages I do see in the SMTP Connector queue.

Not sure if these problems would be related.

Any suggestions would be appriciated.

Hi

I have a problem whereby all users in all remote branches are unable to login to outlook. Outlook says exchange is unavailable. Branch offices connect via a VPN and there is no firewall between them, all ports are open.

All users in my head office (same location as exchange) are unaffected.

From the remote PCs, I can telnet to the exchange server on ports 443 and 25 and from exchange I can telnet back to the PCs on port 135 as well as the ports outlook uses at random, something like 46000-60000.

I can ping the exchange server from the PCs.

I can telnet to both the DCs on LDAP 3389.

I can open the autodiscover webpage and successfully get message 600.

From both the DCs, I can telnet and ping the remote PCs and also to exchange.

I have noticed in the Connection Status tool of outlook, that Outlook says connecting to both the global catalog and the exchange server. If I use the DS Access registry key to force outlook to use my global catalog that holds the FSMO roles, it at least establishes a connection to that but exchange remains on status as connecting.

The autodiscovery tool works also and is successful after I make the logonserver the main global catalog server.

I have tried restarting all the servers (2 DCs and 1 exchange 2007 server) in all different sequences and still no luck.

I have verified the certs are correct on exchange. I have also verified the autodiscovery service to be working successfully via powershell. No clear error messages appear in the exchange evert logs to explain the issue.

Has anyone encountered anything like this before?

Thanks in advance

On Exchange 2007, I've created a self signed cert.

Internal Exchange Server name : ex07.microsoft.local
External Server : ex07.microsoft.xxx.com.sg

New-ExchangeCertificate -FriendlyName "SelfSigned Cert" -SubjectName "cn=ex07.microsoft.xxx.com.sg" -DomainName ex07,ex07.microsoft.xxx.com.sg -PrivateKeyExportable $True

I've Enabled the new certificate for IMAP,POP3,IIS and SMTP

I've exported this cert and installed on my External PC via MMC - Cert.
However, from the External, my outlook client is unable to login via https over rpc.

OWA is fine from External.
I'm also able to login when I did https://internalFQDN/rpc internally.

Any advice ?

Hi all,

May I know more about Exchange 2007 SP1. The situation is

----
A new Exchange Server 2007 SP1 is installed and enable Outlook Anywhere. All
of my Windows XP SP2 with Outlook 2003 SP2 client unable to login from
outside using RPC over HTTPS. I'm not sure the server configuration is
correct or not.

Server Configuration
- Windows Server 2003: DC
- Windows Server 2008: Additional DC with Exchange Server 2007 SP1

Client Configuration
- Windows Vista or Windows 7 with Outlook 2007: Working fine. They can
check e-mail properly from home or office
- Windows XP SP2/SP3 with Outlook 2003 SP2: Unable to login. A login dialog
box is continuous to appear.

Others related to the Exchange Server is working properly such as OWA, Push
Mail, etc

--
KF Thomas SHIU
General Network Computing Limited

When I connect to exchange using the OWA I am unable to login unless I
specifically place my domain name before the user name i.e mydomainuser If
you do not place the domain then the owa will assume the domain incorrectly.
i.e 202.24.67.5user Not sure what is causing this. The Exchange server =
2003

Please help.

I'm unable to log into OWA from the internet error 403.6 pops up, owa loads perfectly from inside the domain, I can even set specific ip addresses from computers outside our domain they and they worked perfectly, I just simply need to reset our OWA to allow any ip address to be able to login by using username and password ( I followed http://support.microsoft.com/default.aspx?scid=kb;en-us;883380, but it did not fix my problem) I know that the problem is possibly in "IP addresses and domain name restrictions" and "authentication and access control" for "Default Web Site" in IIS 6.0.  We're running ms exchange server 2003.  If someone could tell me what are the proper ip settings allow any ip to connect to our OWA that would be great.

Thanks

We have several users who do not regularly connect to the corp LAN, so they used to change their PW when it expires through OWA 2003.

Now that we upgraded to 2007, users are unable to login to OWA to change their password once it expires...

Has this feature been removed, or is there something else I need to enable?

If the user account has not expired, they can successfully change the password, it only effects Expired accounts...

Hello,

I have one user who is not able to access their mailbox using OWA. A few weeks ago the user was able to access it. When the user enters the username/password it just comes back with the login box until it displays HTTP/1.1 401 unauthorized message. The only thing that has changed since is that I have moved the mailbox from one Mailbox Store to a new Mailbox Store. Other users that moved are able to access OWA. HTTP is enabled for the user and when they login to AD they have no problem with mail.  
Your help is greatly appreciated.

Thanks

Hi,

Our problem is this.

We have an Exchange organisation & single AD with approx 1,500 users.
OWA is accessible internally for all users. Most of the time our users
operate with Outlook 2003, but the OWA version is useful if they have to
login quickly / temporarily to another PC. We would like to keep this
capability.

This was fine until recently when we introduced a new interet facing OWA
server. We would like to restrict access to this server to a specific user
group.

Is there a simple way to allow users access to one OWA server internally
but deny them access to the external server?

We are running Exchange 2003 SP1 on Win2k3.

Many thanks for your help.

Any ideas will be greatly appreciated.
Best regards
Matt

Hi,

Have an interesting one here. The system was working perfectly and then all of a sudden, the users are unable to logon to OWA? Yet the administrator can logon without a problem. Any idea what could be happening?

Thanks in anticipation.

I can log into OWA ok on any PC within the company but nobody else can. It asks for my password etc and in I go. When I try it for another user it asks for the password, takes it, adds a bit of the graphics then asks fir the password again and so on. Adding bits fo the OWA screen then asking for the password. I tried telling it to remember the password but that did not help.

Please help, am I just terminally dumb?!

I have a strange issue. All user except admin group cannot login to OWA. iving the error " The user name or password that you entered is not valid. Try entering it again." If I add the user to admin group, after some time, I cabn able to login. Strange issue. Outlook is working fine for all users.

Regds
Pradeep

hello frndz
I have Exchange 2007 organization and I have a problem MY exchange users are unable to change there passwords through OWA It give the following errors:

The password supplied does not meet the minimum security requirements. Please contact technical support for your organization if you need help.

Please Help

Hello,
I recently added a new SMTP address to three different users. The domain
is the same just different prefix. After that they are still able to
recieve mail and send mail via mail client (outlook). But when they try to
login to OWA they get page can not be displayed. If I delete the newly
created email address they can get right on. Any ideas?
--
Jon Boyle


Hello,

Some users are not able to connect to Exchange server 2010 via Outlook 2007 client but can login via OWA. Other users who can connect to server via Outlook 2007 client are in the same database as ones that are unable to connect. Weird like ____.

Please help.

Thanks

Kris


We are running SBS-2003 and all existing users do not have any problem with using Outlook 2003 or OWA via IE to access their email. This week I set up 2 new users and the exact same thing happens with both of them. When I setup Outlook it finds the users name and authenticates it, but when I try to open up Outlook on their PC's I get this error: "Unable to open your default e-mail folders. You must connect to your Microsoft Exchange Server computer with the current profile before you can synchrozine your folders with your offline folder file." 

I have deleted and recreated their profiles on the PC and even tried to create it on a PC they do not use the same results.

When they try to use OWA, I get this error:  "HTTP 1.1/ 503 Service is no longer available" , yet if I can log onto OWA without any issue on the same PC.  Any help would be greatly appreciated!

DJ


Not finding an answer? Try a Google search.