Sunday, June 26, 2011

UTM: Troubleshooting LDAP over TLS integration with SonicWall

Article Applies To:
Affected SonicWALL Security Appliance Platforms:

Gen5: NSA E7500, NSA E6500, NSA E5500, NSA 5000, NSA 4500, NSA 3500, NSA 2400, NSA 240
Gen4: PRO series: PRO 5060, PRO 4100, PRO 4060,PRO 3060, PRO 2040, PRO 1260
TZ series: TZ 210, TZ 210 Wireless, TZ 190, TZ 190 W, TZ 180, TZ 180 W, TZ 170, TZ 170 W, TZ 170 SP, TZ 170 SP Wireless.
Affected Firmware versions: All Gen5 and Gen4 firmware versions (SonicOS Enhanced)
Affected Services: LDAP

Problem Definition:

The following error messages are addressed in this article.

- Problem contacting LDAP server
- Credentials not valid at LDAP server. or Credentials not valid at LDAP server - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece
- LDAP Authentication failed.
- BAD LDAP server certificate TLS error unknown CA

More error messages and solutions related to LDAP integration can be found at the below link: http://support.microsoft.com/kb/823659


Problem contacting LDAP server



Cause of the error:

This error may appear if the DNS settings are not configured properly and the sonicwall is unable to access the LDAP server. We need to make sure that the DNS name resolution works correctly on the SonicWALL.

Possible Solution:

1. In the sonicwall, specify the IP Address of the local DNS server as the DNS server 1.
Go to Network > DNS, click on 'Specify DNS manually' and specify the IP Address of the local DNS server as the DNS server 1 and the public DNS as DNS server 2.
Click Apply on the top of the web page.

Note: Your local DNS server should also forward the DNS requests to the internet DNS servers. Check the forwarders settings in your local DNS server.



2. Try to ping the domain name of your LDAP server.

Go to System > Diagnostics > Ping > enter the domain name, click on 'Go' button. If the response is ‘domainname is alive’ then it is confirmed that the DNS name resolution is working on the SonicWALL.

If there is no reply from the domain name, then ensure the physical connectivity /IP address / Subnet mask of the LDAP server is correct. Try to ping the IP address of the LDAP server.



If you can ping the LDAP server, but are unable to connect to the LDAP server thru the LDAP configuration page then go to User Settings > Select ‘LDAP + Local Users’ and click on the ‘Configure’ button.



Verify the parameters on the Settings tab.


- IP Address of the LDAP server
- Port number
- Login User Name / Password
- Use TLS (SSL) is enabled.



We need to verify the configuration on the LDAP server side.



Check the following security settings on the “Domain Controller Security Settings” in the Active Directory:


Domain Member: Digitally encrypt secure channel data (when possible): Enabled
Domain Member: Digitally sign secure channel data (when possible): Enabled
Network Security: LDAP client signing requirement: Negotiate signing
Domain Controller: LDAP Server signing requirement: None

After making the above changes (if any), update the group policy by running ‘gpupdate / force’ command




‘Credentials not valid at LDAP server.’ Or ‘Credentials not valid at LDAP server - 80090308: LdapErr: DSID-0C090334, comment: AcceptSecurityContext error, data 525, vece’



Cause of the error:

This error means that the LDAP process is failing on the initial bind.

Possible Solution:

1. Check the login credentials on the settings tab:

The Login user name must be the full name, and not the alias (i.e. - 'Mustufa Kamaal Afghan' and not 'mkafghan').





2. Make sure that the user object for the Login user name is in the container/OU specified as User tree for login to server on the directory tab:

In this example, the Login user name ‘Jane Doe’ is a user object in the AD tree ‘ad.local/Users’.

Also, make sure there are no special characters in the password for the Login user name (especially a ! at the end).


LDAP Authentication failed



Cause of the error:

This issue may appear if the proper user name is not supplied for authentication

Possible Solution:

Make sure that you supply the user logon name that is configured in the Active Directory (LDAP server).






BAD LDAP server certificate TLS error unknown CA



Cause of the error:

If the sonicwall device tries to establish an LDAPS (LDAP over TLS) connection with the LDAP server and it is not configured with a valid server certificate, then this error appears.

Possible Solution:

To resolve this issue, please make sure that:

- Correct port number is selected, for LDAPS (LDAP over TLS) port number 636 is used.
- You have imported a valid user certificate and selected the same in ‘Local certificate for TLS’
- Or if you do not have a valid certificate imported, then to avoid this error, simply uncheck the option ‘Require valid certificate from server’. The sonicwall device will still communicate with the LDAPS.






You can verify that the LDAPS server is running on the Active Directory by running the ‘netstat –anp tcp’ command on the LDAP server. If the command return port number 636 TCP 'LISTINING' then it indicates that LDAPS (TLS) is running.



Conclusion:

The solutions provided here should help resolve the most common issues related to the LDAP/TLS integration with SonicWALL.

Reference:  Fuzegna.com, 2008. UTM: Troubleshooting LDAP over TLS integration with SonicWall. https://www.fuzeqna.com/sonicwallkb/consumer/kbdetail.asp?kbid=5097&ratelink=false&msg=Thank%20you%20for%20your%20input.

No comments:

Post a Comment