Exchange Client Access Server causes authentication prompt
I am using Exchannge Server 2007. The client access server is local on the domain. When outlook users are configured the users gets an authentication prompt whenever they open outlook. I need some help on resolving this issue.
July 19th, 2009 4:32am

HI,I cannot understand your question correctly. Can you describe your question and with AD topology and exchange topology?RegardsChinthaka
Free Windows Admin Tool Kit Click here and download it now
July 19th, 2009 4:48am

Dear Jermaine,Please try below option to resolve the outlook username and password prompt. Open IIS on your Exchange server. Expand "your computer name" then expand "Web Sites" then expand "Default Web Site. From here you should see the "Autodiscover". Right click on "Autodiscover" and select "Properties", from here select the "Directory Security Tab" and then click the "Authentication and access control Edit button". A popup page for "Authentication Methods" will be visible. be sure to select the "Integrated Windows authentication" check box.In case still the same issue please let me know.Cheers,Subhash Tiwari |MCA|MCSE|MCSA|MCDBA|MCTS | Blog-> http://subhashtiwari.spaces.live.com
July 19th, 2009 1:11pm

Thanks My AD is Windows Server 2003 and Exchange Server 2007. Mail box Server is in some other country the CAS server is local. I can ping all the servers by name. Users authenticate some times. I even get 'Exchange Server unreachable'.I will try Subhash solution and give an update later.
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2009 5:13pm

Hi, might be your Clients use remote Global catalog server to authenticate users instead of using local Global catalog server. So please refer below TechNet KB article how to point specific GC server for Outlook ResourceHow to configure Outlook to a specific global catalog server or to the closest global catalog serverregards Chinthaka
July 20th, 2009 5:26pm

Hi "Integrated Windows authentication" check box is selected. whenever i try to connect i get the user name and password prompt. when i click cancel i will see at the bottom left hand corner 'need password'.regardles of this i can still send and receive mail
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2009 8:51pm

Do you think ASP.Net service has anything to do with it? The ASP.net version is left blank. Should i go in and select the version '2.0.50727'? "Dont want to make a change that i cannot reverse"
July 20th, 2009 8:58pm

Hi,Did the client connect Exchange server via Outlook Anywhere?Please check whether the Integrated Windows authentication and Basic authentication have been checked on the Autodiscover virtual directory under IIS.If not, please check them. Moreover, ensure "Integrated Windows Authentication" is checked on the EWS virtual directory, then restart IIS and check this issue.ThanksAllen
Free Windows Admin Tool Kit Click here and download it now
July 21st, 2009 12:26pm

Thanks No the clients are not using outlook anywhere to logon to eXchange its disabled. Should i enable it? I have multiple CAS Servers and some are not local. Can I specify what CAS server/s I only want the clients to authenticate against?psBoth Integrated Windows authentication and Basic authentication have been checked on the Autodiscover virtual directory under IIS.
July 23rd, 2009 2:29am

Hi,To get Autodiscover working, Outlook must access CAS. After that, the Free/Busy information, OAB and OOF will be configured smoothly.When Outlook connecting CAS, it will send the LDAP query to get all available Autodiscover URL from the AD and sort them based on the client's AD site. After connecting Autodiscover service successful, it will obtain the AS, OAB or OOF URL based on the proximity and current availability.Thus, it's impossible to specify certain CAS to do the authentication for the client.Currently, I would like to confirm whether all the users had this issue or just the part of users in the local.Additionally, I suggest we check whether the event 9696 was received in event log on the Exchange serverThanksAllen
Free Windows Admin Tool Kit Click here and download it now
July 24th, 2009 9:21am

Thanks guys;The problem is solved. The resolution was actually the two networks were actually on seperate vlans and when we truncked the two vlans and changed the ip settings whalla.... everything just started working. Thanks again your comments really helped me to resolve this problem.
July 25th, 2009 12:48am

Hi,Glad to hear that is resolved by yourself. Thanks for your sharing.Allen
Free Windows Admin Tool Kit Click here and download it now
July 25th, 2009 8:15am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics