I have a 2008 small business server with exchange server 2007 and all the clients are XP with outlook 2007. I have the same problem but the solution did not work for me. If anyone has any other suggestions, I would really appreciate it. Is this right? What do others have?ĭoes this perhaps have to do with IIS7 on Server 2008? I realize this is cutting-edge stuff, so I expect some bumps along the way, but this is just a pain.
I checked my authentication settings for the OAB directory in IIS again, and it is set to Basic (with default domain as my internal domain name) and Windows Authentication. This is extremely frustrating, and I fail to see what is causing these authentication issues. If you leave Outlook closed for an extended period of time, the connection is establised correctly and everything downloads fine with no password prompts. If, however, they close outlook and reopen it, it works fine with no password prompt.Īlso, every few hours, Outlook still prompts for a password to download the OAB.
If they enter their password, it just reprompts and never connects. It seems that if anyone leaves Outlook open overnight, when they return in the morning, it is prompting them for their password to connect to Exchange (over TCP/IP MAPI). Okay, I thought I had this issue resolved, but apparently not. This is really frustrating and I am new to Exchange 07. If anyone knows of anything I should look at, please let me know. Other times, though, even after typing the username and password correctly several times, it still will not connect to the server. The strangest thing is, sometimes, users can just click cancel and the connection gets established. They are all now using a LAN connection to connect directly using MAPI. I have tried forcing the clients to use Kerberos or NTLM instead of negotiating the security, and I ensured that they were not using Outlook Anywhere (which some were). I have checked all the Internal URL and External URL settings everywhere I can find, and according to Get-OutlookProvider, the server is the internal name. This seems strange, but it may have to do with my usage of SSL certificates, as the valid, signed cert is has the outside address as its CN. The strange thing is, the logon box's title indicates it is attempting to connect to our outside FQDN instead of the internal one. Everything was working well for the first few days, but this morning, Outlook began prompting users to enter their credentials. I recently put in a brand new domain at my workplace using Server 2008 Standard and Exchange 2007 Standard.
0 kommentar(er)
