Thanks, That's a good line of enquiry Riley.
I'm not sure how to take that further unfortunately.
ILLiad is OCLC's Document Delivery platform written in .NET that runs in
the context of IIS, in this case IIS 7.5
The issue hasn't gone very far with OCLC or the vendor behind ILLiad.
They seem to be stumped and I fear it's a 'not of our doing' symptom
(which includes my company).
I have limited experience with IIS and Windows, and virtually none with
LDAP.
If anyone knows of another forum or list, that would be helpful too.
On 3/28/14 11:18 AM, "Riley Childs" <[log in to unmask]> wrote:
>Does illiad run on top of something (IIS, Tomcat etc)
>>Yes, I think so. But narrowing that down has been the challenge and it's
>>extremely difficult to put the blame squarely in one corner.
>>So, my question has been what exactly is the connectivity issue. Is it
>>W2008, Illiad or LDAP?
>>
>>Since it works on port 389 I'd like to rule out ILLiad but I'm struck by
>>how a refresh on the browser allows the authentication.
>>The windows server and LDAP are managed by different groups, and are
>>different stacks, windows 2008 server vs Novell on linux.
>>Since LDAP is binding I assume the problem is with the Windows
>>configuration or certificate, or store.
>>
>>To answer your last questions.
>>The servers are in the same data center, and an ldapadmin test from the
>>windows server is successful.
>>This is a new Windows server with the latest version of ILLiad. We bumped
>>up servers from W2003 to W2008
>>There's not much revealing in the logs, folks from Atlas System and OCLC
>>have looked at them.
>>
>>Thanks
>>
=====================================================================
Please note that this e-mail and any files transmitted from
Memorial Sloan-Kettering Cancer Center may be privileged, confidential,
and protected from disclosure under applicable law. If the reader of
this message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any reading, dissemination, distribution,
copying, or other use of this communication or any of its attachments
is strictly prohibited. If you have received this communication in
error, please notify the sender immediately by replying to this message
and deleting this message, any attachments, and all copies and backups
from your computer.
