Solved

SonicWALL SSL-VPN 4000 - Active directory integration

Posted on 2013-12-24
6
855 Views
Last Modified: 2014-04-02
I recently started my current job, and last week the primary domain controller died.  Little did we know that it was not replicating correctly.  In the end,  I had to seize the roles on the secondary, and out backup softwares {AD backups} do not backup GPO objects, so they are all lost.

Our SSL-VPN device was authenticating users just fine through an active directory connection, but since the recovery,  It keeps saying users are "not a member of the permitted AD group(s).   The work around is to remove the security groups that are allowed, which lets everyone use it.. I want to secure this back up.  Here is a copy of the log.  {newest entry on top}

2013-12-24 13:29:29 Warning Authentication 10.1.1.254 192.168.1.6 jthompson User login failed

2013-12-24 13:29:29 Debug Authentication 10.1.1.254 192.168.1.6 jthompson Login failed - Not a member of permitted AD group(s)  


2013-12-24 13:29:29 Debug Authentication 10.1.1.254 192.168.1.6 jthompson Matched 0/2 groups (0.00%)

2013-12-24 13:29:29 Debug Authentication 10.1.1.254 192.168.1.6 jthompson No match for AD group: ssl-vpn-auth

2013-12-24 13:29:29 Debug Authentication 10.1.1.254 192.168.1.6 jthompson No match for AD group: SSL-NetExtender-HQ

2013-12-24 13:29:29 Debug Authentication 10.1.1.254 192.168.1.6 jthompson Considering SSL-VPN group: VPN

2013-12-24 13:29:29 Debug Authentication 10.1.1.254 192.168.1.6 jthompson Found existing SSL-VPN group: amervend

2013-12-24 13:29:29 Debug Authentication 10.1.1.254 192.168.1.6 jthompson Error in binding to LDAP server: Local error (82)

2013-12-24 13:29:29 Debug Authentication 10.1.1.254 192.168.1.6 jthompson Kerberos login successful

2013-12-24 13:29:29 Debug Authentication 10.1.1.254 192.168.1.6 jthompson Attempting AD/Kerberos login (principal: 'jthompson@AMERVEND.AFVUSA.COM', realm: 'amervend.afvusa.com')
 
2013-12-24 13:29:29 Debug Authentication 10.1.1.254 192.168.1.6 jthompson Login attempt: domain: 'VPN'


Also,  if I go to Users --> Local Groups --> configure group --> AD Groups tab --> configure and enter a domain name and password,  it get the same error as above.
"Error in binding to LDAP server: Local error (82)"
0
Comment
Question by:Madlife6
  • 3
  • 3
6 Comments
 
LVL 11

Expert Comment

by:Miftaul
ID: 39737939
SSL VPN uses a simple AD account to validate the AD users if you integrated AD logon for VPN users. The AD account doesnt need any administrative privileges. Here "jthompson" is the AD account that was configured when integrating with AD.

To reconfigure it, you need to go to "Users -> Settings -> select "LDAP+Local" on "Authentication method for login" and click Configure"

As all configurations were already there, under the Login username in Setting tab, enter users full name as the Login username. And the password for the user. This must match the AD.

Go to Test tab, and enter the details and do a test, Dont enter fullname here, rather the login name. that should work now.
0
 

Author Comment

by:Madlife6
ID: 39737994
Maybe I should have Clarified,  this is the SonicWALL SSL-VPN Appliance.  there is No users-> Settings option.  If I go into portal -> domain,  the authentication is set as "Active Directory"

The error log looks to authenticate the users just fine,  but can't determine the group


I compared it without SonicWALL Firewall settings, which does LDAP + Local Authentication for the content filter bypass.  This authenticates users in the group without issue.
0
 
LVL 11

Expert Comment

by:Miftaul
ID: 39738071
Could you follow This Link and check page 142.
0
Simple, centralized multimedia control

Watch and learn to see how ATEN provided an easy and effective way for three jointly-owned pubs to control the 60 televisions located across their three venues utilizing the ATEN Control System, Modular Matrix Switch and HDBaseT extenders.

 

Accepted Solution

by:
Madlife6 earned 0 total points
ID: 39824162
Sorry for the delay.  I was out sick and then sent to a remote site for a week and a half.   I got this up and working.  It appears to be an issue with our PDC.  I rebuilt a 2nd domain controller,  got all the Active directory parts sync'ing good with the PDC, and when i pointed the SSL-VPN 4000 to this,  it worked just fine.

We have plans in the upcoming months to migrate everything to 2008, and in the process, get rid of the troublesome server.
0
 
LVL 11

Expert Comment

by:Miftaul
ID: 39824193
Good that the issue is fixed. Well done.
0
 

Author Closing Comment

by:Madlife6
ID: 39971694
Because the problem was an anomololy inside our PDC that no one would have figured out on their own.  All of their suggestions and help combined did lead me to determine this though.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

In-place Upgrading Dirsync to Azure AD Connect
This article explains the steps required to use the default Photos screensaver to display branding/corporate images
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

685 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question