Thread Info
  • State Suggested Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 29 subscribers
  • Views 12807 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

SSL VPN Client dont connect with AD users

Idir AIT YAHIA

Hello All

 

I have configured SSL VPN remote access, i can remotely donwnload and install client with user configuration

But it is impossible for users added from AD to connect to the VPN.

I tried with a user created locally on firewall, it connects correctly to the VPN.

Knowing that I have correctly configured SSL VPN Client authentification method, someone has an idea of the source of the problem ?

 

Regards



This thread was automatically locked due to age.
Parents
  • 0

    Hi Idir, 

    If the user is new to AD then you may need to authenticate via captive portal or by using a client. This way the user will be registered onto the XG device. This is only used fo the users who are new to AD and never been authenticated on XG. 

  • 0 in reply to Aditya Patel

    Hi Patel,

    Thank's for your reply, the user are already logged on firewall, It is also listed in the user list. the user created on firewall belongs to the default group open user, and users imported from AD belong to the AD group.

    May be that the problem occurs when negotiating the login between the firewall and the domain controller, Since the first user does not exist on the domain, so the password is checked locally.

     

    regards

Reply
  • 0 in reply to Aditya Patel

    Hi Patel,

    Thank's for your reply, the user are already logged on firewall, It is also listed in the user list. the user created on firewall belongs to the default group open user, and users imported from AD belong to the AD group.

    May be that the problem occurs when negotiating the login between the firewall and the domain controller, Since the first user does not exist on the domain, so the password is checked locally.

     

    regards

Children