Highlighted
Absent Member.
Absent Member.
544 views

Contextless login stopped working via encrypted LDAP


Hi all: Yesterday I created a new workstation image which I intend to roll out to all my users. In my testing of this new image I have discovered that the Novell Client (Novell Client 2 SP3 for Windows 7 (IR6)) will not do contextless logins via encrypted LDAP as it has in the past (worked for many years). If I move to unencrypted LDAP then contextless login works fine. At first I thought it was a certificate issue so I copied the certificate I know works to my test machine, but I still get the same results.


I am really stuck and could use some help. Thanks, Chris.
Labels (1)
0 Likes
3 Replies
Highlighted
Absent Member.
Absent Member.

Re: Contextless login stopped working via encrypted LDAP


PS: Sorry I forgot this little piece. The error I receive when I try to use encrypted LDAP is: "LDAP Contextless Login: No LDAP server specified." This is BS as I know I have working LDAP servers if I merely turn off encryption and goes to port 389. Chris.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Contextless login stopped working via encrypted LDAP

Is it safe to assume you have no traffic on the eDirectory server when
this tries to work and instead errors? Have you tried watching a LAN
trace to see if the client is even trying to make a connection to any
server when this happens (to see how accurate the error message is)?

I assume when you are changing from encrypted to unencrypted (or vie
versa) that you are explicitly changing the port as well, but if not
please confirm.

If you are following a particular section of documentation including a
link to that may help us reproduce the issue.
--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Highlighted
Absent Member.
Absent Member.

Re: Contextless login stopped working via encrypted LDAP


Thanks for the reply. When I change from encrypted to unencrypted the post gets automatically changed from 636 to 389. I have not run a LAN race when attempting encrypted LDAP, but I know it returns data when unencrypted as the context will change for users in different OUs. I am also sure the servers are listening on 636 as other workstations function fine using encryption.


I think wireshark is my next stop. Chris.


>>> ab<ab@no-mx.forums.novell.com> 5/15/2014 11:43 AM >>>



Is it safe to assume you have no traffic on the eDirectory server when
this tries to work and instead errors? Have you tried watching a LAN
trace to see if the client is even trying to make a connection to any
server when this happens (to see how accurate the error message is)?

I assume when you are changing from encrypted to unencrypted (or vie
versa) that you are explicitly changing the port as well, but if not
please confirm.

If you are following a particular section of documentation including a
link to that may help us reproduce the issue.
--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.