asked on LDAP/Authentication isseu
Hello Experts,
For some time now (few weeks) we have had a systemic issue with one of our applications that uses LDAP to authenticate.
We use a program called Presenter, that uses the LDAP protocol to authenticate users from Active Directory. When the users open internet explorer and go to the site it display an error message.
ERROR MESSAGE
An unexpected error occurred.
Could not open LDAP://CN=Desktop Users, OU=_DistributionGroups,DC=
When the user gets this error message they do not get directed to the login page or anything just a white IE page with this message. The interesting thing is that if they continually "refresh" "F5" the page if this error message appears after say about 5-10 times of "refreshes" they will get to the login page.
I have found this MS KB Artical which describes symptoms we are having but I do not what to apply this fix until I have done some more troubleshooting.
If any one has any ideas as where to start any suggestions would be greatlty appreciated.
I have attached the exact screenshot of what a user will encounter when trying to access this site (internal site).
LDAP-error-meesage.JPG
For some time now (few weeks) we have had a systemic issue with one of our applications that uses LDAP to authenticate.
We use a program called Presenter, that uses the LDAP protocol to authenticate users from Active Directory. When the users open internet explorer and go to the site it display an error message.
ERROR MESSAGE
An unexpected error occurred.
Could not open LDAP://CN=Desktop Users, OU=_DistributionGroups,DC=
When the user gets this error message they do not get directed to the login page or anything just a white IE page with this message. The interesting thing is that if they continually "refresh" "F5" the page if this error message appears after say about 5-10 times of "refreshes" they will get to the login page.
I have found this MS KB Artical which describes symptoms we are having but I do not what to apply this fix until I have done some more troubleshooting.
If any one has any ideas as where to start any suggestions would be greatlty appreciated.
I have attached the exact screenshot of what a user will encounter when trying to access this site (internal site).
LDAP-error-meesage.JPG
DatabasesActive DirectoryWindows Server 2003
Last Comment
Will Szymkowski
Did you try different browser ?
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks for the responses...
@ Roads - We have tried different broswers and this does not make a difference.
@ noci - This is the link that the users have been using for quite awhile now. It has always worked before. I do not administer the "Presenter" server. I have asked the development team and they have said that no changes have been made.
Where could we start to diagose this issue? Is there any tools out there that could be helpful?
@ Roads - We have tried different broswers and this does not make a difference.
@ noci - This is the link that the users have been using for quite awhile now. It has always worked before. I do not administer the "Presenter" server. I have asked the development team and they have said that no changes have been made.
Where could we start to diagose this issue? Is there any tools out there that could be helpful?
ASKER
When we use the syntax you have stated before (ldap://ldapserver[:port]/
LDAP-search-dialog-box.JPG
LDAP-search-dialog-box.JPG
Besides syntax, if the backend LDAP / AD server is to slow with a respons it will also be taken as a refusal.
That would at least explain the F5 behaviour.
So try to find out if there are any differences in performance between the presenter server and the ldap server.
That would at least explain the F5 behaviour.
So try to find out if there are any differences in performance between the presenter server and the ldap server.
the ldap port is 389 (default). not 24500.... and default can be omitted.
and ldapserver is the actual ldapserver not a webserver server.
and ldapserver is the actual ldapserver not a webserver server.
ASKER
24500 is the port that they have always used. Nothing has change (that I know of). Here is the KB artical that explains our symptoms. Take a look and let me know what you think. I have not tried this yet...
http://support.microsoft.com/kb/908370
http://support.microsoft.com/kb/908370
Well that article also mentions LDAP access problems, where the underlying cause is lsot packets in the teaming and or lower driver(s).
They suggest a particular installation order in the Resolution section. That seems at least a viable start to at least exclude that the problem is in that area.
They suggest a particular installation order in the Resolution section. That seems at least a viable start to at least exclude that the problem is in that area.
ASKER
We have used a work-a-round solution for this as the following KB artical has not solved this issue.
Thanks for the suggestions.
Thanks for the suggestions.
ASKER
Thanks for your help.