OWA Login Problem 1

[UkMister]

Hi,
I have a rather interesting OWA login problem. Most users have no problem in logging on to the OWA server. However, one or two of them are prompted for their login credentials, they supply them (they are correct) and the page starts to load. The page then gets 'stuck' and prompts for the login credentials again. This loop continues.
The page looks like it is going to load with the frames appearing, but it never quite gets there. I can't find anything that would cause this as when I try dialling in, it works, as it does for most users. I'm completely stuck and don't know where to begin.

Can someone help???

ukmister

 

[robbyb]

Only a guess, but could it be that something in the mailbox is preventing the page from loading up correclty? It maybe then times out and wants to authenticate again?

You could try backing up the mailbox (perhaps to PST, if not to tape), and then maybe deleing and recreating the mailbox. Test it whilst empty. Test again when you have restored the mailbox.

?

 

[Zelandakh]

Another thought is java support on the client - if its not installed it doesn't login.

 

[maguca]

Hi there,

Had this problem once, but only when accessing OWA from LAN... the client machine wasn't registering it's DNS suffix - check this in IP properties/DNS tab. This was causing authentication queries for every object on the page.

mc

 

[lengoo]

I have had this problem and currently I have this problem. Try stopping and starting the webservices and then reassigning the permissions for the exchange folder.

 

[jasonhand]

It's a permissions issue. Make sure that the permissions are set correctly for the inetpub folder according to Microsoft specs. I had this problem and had a Microsoft engineer walk me through what the permissions should be on the Inetpub folder and subfolders and it solved the problems. Sorry I don't have the exact settings, but Microsoft may have a technet bulletin on the permissions necessary to make OWA function correctly.

-Jason
-Jason
Romans 12:1-2

 

[zoeythecat]

I once had a problem with certain usernames accessing OWA. I would get, &quot;Could not access Inbox&quot;. Not sure if this applies here but what I found out in my case was the Exchange Display name was not unique (had a long display name) for some usernames. So what I had to do to login to these mailboxes was on the first screen for the login name enter the ==>mailbox@xxxxx.org< for the username. You will then be prompted to enter the username and password. Enter these as you normally would.

 

[UkMister]

I'm going through all these suggestions. I set up an empty account but the user still couldn't access his account.
I'm not sure that it is a permissions problem either. When I try to access their account using a dial up connection from home I get in!!
The only difference is that my user uses a broadband connection and I use standard 56k dial up connection.
Also, I can't check any settings on their machine because it is their own home computer - could it be something to do with settings on their machine?
I did have problems a few months ago that needed me to reinstall OWA but it seems to be working for almost everyone.
Is there a microstoft paper that explains exactly what settings should be used when setting it up??

Again, thanks for your help

ukmister

 

[robbyb]

Are you still using the default port 80 for OWA? If not, then your user may have a firewall that is blocking the new port?

Ask your user if he is using any software firewalls like ZoneAlarm. He may have too restrictive a setting that isn't allowing authentication to happen.

He/she may have an ADSL router. This may have too restrictive a setup.

Send 'em down to an Internet Cafe, that's what I say!

 

[zoeythecat]

One thing to consider may be to have the user bring in their workstation so you can troubleshoot it at work. That may be the easiest scenario. If you can get this workstation onto your network and login via OWA then it may be something to do with their settings. Maybe you can run some updates on their system and make sure they are at the latest Internet Explorer.

 

[maxfaj]

give this a try, on the smtp properties of the exchange server, go to aunthentication and remove the domain name ie.. exchange.ny.gov click apply, then go back and enter exchange without ny.gov &quot;maybe&quot; just maybe this might help.

 

[UkMister]

Hi again,

I've been speaking to the supplier of my users broadband package. I have been informed that cache that my users box is pointing at has a problem. I was advised to point the box at a different cache location (I'm still not too sure how broadband works). Apparently it is quite easy to do. It will have to be if a user is to configure it!!

When the results are in, I'll let everyone know.

Again, thanks for your help in this

ukmister

 

[tencevaines]

You know, you might be onto something there.

OWA 2000 definately doesn't like proxy servers, so if the user you are having trouble with has a proxy configured in their IE (could be what the Broadband is calling a cache), then remove it and try again.

The only other ways to solve this issue (if it is indeed a proxy type issue and you require proxy for internet access), is one of two things, setup HTTPS on the OWA server. HTTPS encrypts the data, and proxy won't touch encrypted data therefore allowing all data to tansfer through. The other method is VPN, setup a quick ras server on your win2K box, and setup a vpn tunnel to connect this user to your OWA.

Hope this helps Bro!

 

[brightds]

It is definetly a proxy/global policy issue. We have had and resolved this issue using MS new proxy server.
If you are still having this problem - feel free to e-mail me and I will provide additional info.
Thanks
Don

 

[UkMister]

Hi,

We eventually found the problem to this.
I'm not too sure of the technical details or how broadband works in the UK but here goes. NTL are the broadband providers for a couple of users here. Apparently, NTL have been having problems with one of their 'caches' at the Nottingham site. This means that anyone that has their broadband box set up to look at this site will have problems accessing OWA.
Our user rang NTL and was talked through the procedure for changing where the broadband box was pointing.
This done, our user can now access OWA.

Hope this helps