Replies

Thank you. I’ll have a look at that resource kit.

I’ve just found this: http://support.microsoft.com/?kbid=245830

However, changing the user name to the cn=username,cn=domain format worked, but only if the “Log on using secure authentication” was ticked. So no improvement, just a slightly more complicated username string.

Thank you. I’ll have a look at that resource kit.

I’ve just found this: http://support.microsoft.com/?kbid=245830

However, changing the user name to the cn=username,cn=domain format worked, but only if the “Log on using secure authentication” was ticked. So no improvement, just a slightly more complicated username string.

Edited by unkamunka to make the MSKB link “live”

I think it may make sense to split this query in two. I’ve found this article:

Microsoft Knowledge Base Article 326690

But don’t seem to have the tools it is suggesting I alter my settings with. I’ll start a new post in one of the server forums to answer this part of the query.

Therefore – Anyone any ideas for the search order in Outlook?

Edited by unkamunka to make the MSKB link “live”

I think it may make sense to split this query in two. I’ve found this article:

Microsoft Knowledge Base Article 326690

But don’t seem to have the tools it is suggesting I alter my settings with. I’ll start a new post in one of the server forums to answer this part of the query.

Therefore – Anyone any ideas for the search order in Outlook?

Ummmm. Well….. I’m still at the same point. I know how to set up Outlook 2000 (company standard) and Outlook Express to connect to AD via LDAP. However, as other Outlook set ups (XP and 2000 in Corporate mode) don’t offer the “Secure Password Authentication” option, I’d like to know how I can change the authentication method at the server so as not to require this option at the client end – perhaps I should have put that more clearly.

Also my main head ache is the search order.

I appreciare the help so far.

Ummmm. Well….. I’m still at the same point. I know how to set up Outlook 2000 (company standard) and Outlook Express to connect to AD via LDAP. However, as other Outlook set ups (XP and 2000 in Corporate mode) don’t offer the “Secure Password Authentication” option, I’d like to know how I can change the authentication method at the server so as not to require this option at the client end – perhaps I should have put that more clearly.

Also my main head ache is the search order.

I appreciare the help so far.

In Outlook XP in Change (same path as yours) there is a tick box for “This server requires me to log on”. If I got to the More Setting, there is a tick box to use SSL. The latter does not seem to do the same as Secure Password Authentication. If you look at Outlook Express (XP SP2 version for example) you’ll see that this has both a “Secure Password Authentication” (General Tab) and “SSL” (Advanced tab) option. The two are not the same. Having played with using Outlook Express to connect to AD/LDAP I can assure you the two are different.

However, this is going off subject a little. Can anyone help me with changing the search order, so that systems check LDAP before contacts? Any suggestions on how I go about altering the LDAP access rights?

In Outlook XP in Change (same path as yours) there is a tick box for “This server requires me to log on”. If I got to the More Setting, there is a tick box to use SSL. The latter does not seem to do the same as Secure Password Authentication. If you look at Outlook Express (XP SP2 version for example) you’ll see that this has both a “Secure Password Authentication” (General Tab) and “SSL” (Advanced tab) option. The two are not the same. Having played with using Outlook Express to connect to AD/LDAP I can assure you the two are different.

However, this is going off subject a little. Can anyone help me with changing the search order, so that systems check LDAP before contacts? Any suggestions on how I go about altering the LDAP access rights?

I only have one user running Office XP and they are at SP2. I’ll apply SP3 and see if that helps them.

However, everyone else is on Office 2000.

I only have one user running Office XP and they are at SP2. I’ll apply SP3 and see if that helps them.

However, everyone else is on Office 2000.

Yes. You can set up an LDAP connection, but it won’t connect. Outlook XP doesn’t seem to have the “Use Secure Password Authentication” option that my Win 2003 server seems ot require. I hit the same problem with the Outlook 2000 Corporate setup (which gives you “services” in the tool menu rather than “accounts”). If you go into Sevices in Outlook 2000 and set up an LDAP connection, again there is no “Use Secure Password Authentication” option and I fail to connect. Switch to Internet only and set up the connection via “Accounts” in the tools menu, put a tick in “Use Secure Password Authentication” and it works a treat.

Yes. You can set up an LDAP connection, but it won’t connect. Outlook XP doesn’t seem to have the “Use Secure Password Authentication” option that my Win 2003 server seems ot require. I hit the same problem with the Outlook 2000 Corporate setup (which gives you “services” in the tool menu rather than “accounts”). If you go into Sevices in Outlook 2000 and set up an LDAP connection, again there is no “Use Secure Password Authentication” option and I fail to connect. Switch to Internet only and set up the connection via “Accounts” in the tools menu, put a tick in “Use Secure Password Authentication” and it works a treat.

You can get this problem if your e-mail address domain is not hosted by the ISP. If exchange is set up to use you domain.local address or another provider is hosting your company domain (e.g. mycompany.com), bellsouth.net will see you e-mail address as foreign and assume you are relaying. I’d suggest:

1. Check that Exchange is set up correctly with you external domain name (not a .local address)
2. If another company is hosting your domain name, you should be able to route outgoing SMTP traffic to their mailservers rather than bellsouth’s.
3. Another option would be to transfer the domain to bellsouth (however you will also need to transfer any web pages which could a problem).
4. Last option, set Exchange to send e-mail directly (don’t relay through the ISP).

You can get this problem if your e-mail address domain is not hosted by the ISP. If exchange is set up to use you domain.local address or another provider is hosting your company domain (e.g. mycompany.com), bellsouth.net will see you e-mail address as foreign and assume you are relaying. I’d suggest:

1. Check that Exchange is set up correctly with you external domain name (not a .local address)
2. If another company is hosting your domain name, you should be able to route outgoing SMTP traffic to their mailservers rather than bellsouth’s.
3. Another option would be to transfer the domain to bellsouth (however you will also need to transfer any web pages which could a problem).
4. Last option, set Exchange to send e-mail directly (don’t relay through the ISP).

In the hope of not appearing too naive, what happens if you use the record macro option to capture some code when the button is pressed. I don’t know how well this works with a third party application, but it might be worth looking at the code Excel generates to see if that has any pointers in it.