We help IT Professionals succeed at work.

OWA and IE now requiring DOMAIN\Username

Running Exchange 2003 sp2 on Server 2003 R2 sp2.  
Since approx. June 6th 2010 users logging in to OWA have to use DOMAIN\username where previously only had to use username.  As said this was working up to the weekend, also it only happens using IE 7 &8, firefox works just fine.  Mobile access etc still OK.
All the setting on IIS and Exchange are good, I set it up a few years ago with the default domain and has been working since.
Has anyone else seen this issue over the last week?
Comment
Watch Question

BusbarSolutions Architect

Commented:
do you use form based authentication or windows auth!

Author

Commented:
We do not use forms base authentication, (ESM-Protocols-HTTP-Exchange Virtual Server)
We do use Integrated Windows Authentication  (ESM-Protocols-HTTP-Exchange Virtual Server-Exchange-Authentication)

Commented:
Things like that don't often just change on their own, did anyone make any changes to your setup before it stopped working?

Author

Commented:
No, nobody made any changes. The only thing that would have changed would be a update to either the exchange server or a IE patch on the clients.  
BusbarSolutions Architect

Commented:
windows authentication always uses domain\username
looks like you have been using basic auth, if so go to the IIS and configure it for basic Auth and configure the default domain \

Author

Commented:
The default domain in IIS Directory Security is our Domain name.
What happens now is that when you try to log in to OWA using IE the login box pops up again with URL\username already filled in.  This started happening last week, though it doens't do this when you use FireFox.  No changes has be be made to our Exchange server, apart from Windows Updates.
Everything was working perfectly up to last week, and if you don't us IE it still is.
BusbarSolutions Architect

Commented:
looks like it is related to IE!

Author

Commented:
So you'd think... but I have some test VMs that haven't been updated recently and it still happens.  It's an annoyance but not a huge issue, apart from 'users' who seem to think this is the end of the world.

I was mainly interested in seeming if anyone else had seen this issue arise in the last week or so.

I'm confident Exchange/IIS etc are set up OK as I configured them not to need the DOMAIN\Username combo.  
BusbarSolutions Architect

Commented:
lol I know what you are talking about.
well never seen this looks like there is an update deployed that broke the auth config.
No solution found