New server install, users keep getting popup for the username/password in outlook, this problem is becoming the vaine of my life. SBS 2k8 SP2 - Exchange 2007 Sp2 (Exchange SP2 just installed to try and get round this problem), Rollup 4 installed. All windows updates installed. The server is all default settings, the clients added to the domain normally, things were all fine then outlook started saying needs password. Some getting the popup box. I thought I resolved it by changing IIS, default site OWA to accept but its come back. I've read many threads but all have different solutions so I've decided to open my own so apoligies in advance. The outlooks aren't set to ask for autherisation/username password either. They were just added normally through the outlook wizard to exchange. There's a mixture of outlooks, but mostly Outlook 2003 & Outlook 2007. 1 has Outlook 2010.

Key points. 1. Is this happening with all versions of Outlook? Including Outlook 2003. 2. Did you install SP2 with the wrapper for SBS 2008? If not then that might have caused problems. SP3 doesn't need the wrapper - any reason you didn't go straight to SP3? 3. Was the server configured using the wizards? It isn't clear what you changed in IIS - but changes to IIS should not be required, IF the server was setup correctly. The most common reason for this is that the autodiscover URL resolves somewhere else and the prompt isn't coming from your server but elsewhere. Running the Fix My Network wizard in the SBS management console will often fix a lot of issues. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

Hi Simon. 1. Is this happening with all versions of Outlook? Including Outlook 2003. I've narrowed it down to Outlook 2007. 2. Did you install SP2 with the wrapper for SBS 2008? If not then that might have caused problems. SP3 doesn't need the wrapper - any reason you didn't go straight to SP3? By wrapper, if you mean the Exchange installation tool, yes I did. I downloaded and extracted the SP2, then installed it with the tool. The problem I had was there before and after. I haven't installed SP3 just yet as I didn't have time. 3. Was the server configured using the wizards? Yes. It isn't clear what you changed in IIS - but changes to IIS should not be required, IF the server was setup correctly. I changed the following from this thread http://social.technet.microsoft.com/Forums/en-US/exchangesvrclients/thread/b9572e9d-34df-4d1c-82fb-a9fb8e1c2283, its solved it twice. 1st time I just did OWA and it dissapeared. The next time it came back I installed Exchange SP2 and did the following.... IIS Mgr on SBS 2008 / - / SBS Web Applications / - SSL Settings / Client certificates - Stop / Start web server after changing settings: Autodiscover: Ignore EWS: Ignore OAB: Accept *) owa: Accept *) Rpc: Accept *) RpcWithCert: Accept *) *) All these have to be Accept to get rid of login box The most common reason for this is that the autodiscover URL resolves somewhere else and the prompt isn't coming from your server but elsewhere. Running the Fix My Network wizard in the SBS management console will often fix a lot of issues. I'll try this if/when it comes back. I have seen it for 24hrs now since EWS, OAB and RPC was set to accept. Thanks!

Outlook doesn't use client certificates at all in a default configuration, so setting the client configuration settings was problem a waste of time. It may well have done is forced an update of the IIS Metabase, so it wasn't the actual change that fixed the issue, but something done as a consequence of the issue. The fact that you have pinned it down to Outlook 2007 is good, because that does point the finger at web services. The repeating authentication prompt can mean a number of things, such as the wrong authentication type being used. Simon.Simon Butler, Exchange MVP Blog | Exchange Resources

ok, I'll sit on this for the time being, 48hrs now and its not come back.

Hi, I would like to confirm how is thing going on. Is everything working fine now? If there is any progress or problem, please feel free to post it here. Regards, Novak Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Still running fine still :)