Initial connect of Outlook client to Exchange server 2007sp1 with Outlook anywhere takes a long time (1,5 minute) auth=ntlm
Hi,
I have a weird problem. When I start my Outlook on a remote site. Outlook connects to my server using Outlook anywhere (rpc over https). The initial connect time is very long (1,5minute).
After this, when Outlook shows connected, everything works very fast.
The authentication is NTLM. On my old server, with Windows 2003 x64, I did NOT have this problem. On my new Windows 2008 x64 server I cannot find the problem.
I have tried disabling ipv6. Did not make any difference.
Anyone can help me out?
Thanks,
Raymond
I have a weird problem. When I start my Outlook on a remote site. Outlook connects to my server using Outlook anywhere (rpc over https). The initial connect time is very long (1,5minute).
After this, when Outlook shows connected, everything works very fast.
The authentication is NTLM. On my old server, with Windows 2003 x64, I did NOT have this problem. On my new Windows 2008 x64 server I cannot find the problem.
I have tried disabling ipv6. Did not make any difference.
Anyone can help me out?
Thanks,
Raymond
ASKER
Thanks, I will try this tomorrow. I'm at the server location now. My ost is not so big, it is 100Mb now.
Raymond
Raymond
Try disabling NTLM and Changing to Basic. Also you should verify what Authentication Method you are using server side.
You didnt mention which Version of Outlook you were using - if you are using 2007 all you need to do is match the version running server side - if you are running 2k3 - make sure you use basic as NTLM might work - but more often than not requires basic.
http://msexchangeteam.com/archive/2007/11/08/447484.aspx
THis will help you check your authentication methods within Exchange http://technet.microsoft.com/en-us/library/bb124149.aspx
You didnt mention which Version of Outlook you were using - if you are using 2007 all you need to do is match the version running server side - if you are running 2k3 - make sure you use basic as NTLM might work - but more often than not requires basic.
http://msexchangeteam.com/archive/2007/11/08/447484.aspx
THis will help you check your authentication methods within Exchange http://technet.microsoft.com/en-us/library/bb124149.aspx
You can also do some additional troubleshooting by locating the Exchange Icon within the System Tray and holding down your Ctrl Key and Right Clicking on it - then select "Connection Status" this will show you the RPC Process and the Negotiation and what Directory Server you are using.
ASKER
@tenaj: My ost is rebuild, but connecting still takes a long time.
@redsoxunixgeek: I will try both and get back to you. Thanks! BTW I use Outlook 2007.
@redsoxunixgeek: I will try both and get back to you. Thanks! BTW I use Outlook 2007.
ASKER
@redsonunixgeek:
Connection status shows connected with https to my server for all items (5).
I will try to switch to basic, but I need some time for that. I'll get back to you for that. Thanks,
Raymond
Connection status shows connected with https to my server for all items (5).
I will try to switch to basic, but I need some time for that. I'll get back to you for that. Thanks,
Raymond
ASKER
I changed server and client to basic authentication now. However, it still takes a long time before Outlook 2007 askes for a password. When I finally can enter the password, Outlook shows connected within seconds.
I still have no clue why it takes so long to ask for a password. Status is trying to connect.
I can use the webmail interface without problems.
Raymond
I still have no clue why it takes so long to ask for a password. Status is trying to connect.
I can use the webmail interface without problems.
Raymond
Have you reviewed the logs on the server?
ASKER
Hi,
Sorry for the late reply. I have gone through the logs. When I logon I can see nothing special in the logs. I'm gessing I have to live with the delay, or go back to Windows server 2003 x64.
Raymond
Sorry for the late reply. I have gone through the logs. When I logon I can see nothing special in the logs. I'm gessing I have to live with the delay, or go back to Windows server 2003 x64.
Raymond
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Tried this also. No luck. I'm going away for a week, so I close this. Thanks for your help tenaj!
c:\Documents and Settings\<profilename>\Loc
This will force the machine to recreate the OST file which may be corrupt. Also, how big is your OST file? Every time you start Outlook it checks to make sure that you have a good OST file and if it's huge you might see an improvement if you archived some of your data.
-t