AD users not able to connect to SSL_VPN, Local users connect correctly. Auth Method set correctly.

Thysmith
Thysmith Posts: 16  Freshman Member
First Anniversary 10 Comments Friend Collector
edited April 2021 in Security
Hi all, I have checked through the form but nothing has seemed to explain what is going wrong. Here is the log to start:
[ 2018/11/19 12:45:12 ][SecuExtender Agent][DETAIL]&nbsp; Build Datetime: Dec 22 2016/15:25:36<br>[ 2018/11/19 12:45:12 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;SecuExtender.log: C:\Users\%Username%\SecuExtender.log<br>[ 2018/11/19 12:45:12 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;osvi.dwPlatformId = 2, osvi.dwMajorVersion = 6, osvi.dwMinorVersion = 2<br>[ 2018/11/19 12:45:12 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;interface guid: {F90AB50A-709D-44E6-A0AE-229DEA5DAC8F}, idx: 2<br>[ 2018/11/19 12:45:12 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;tBuf : (\DEVICE\TCPIP_{F90AB50A-709D-44E6-A0AE-229DEA5DAC8F})<br>[ 2018/11/19 12:45:12 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;network name got, idx: 18<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Checking service (first) ...<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; SecuExtender Helper is running<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Try to connect to SecuExtender Helper<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; SecuExtender Helper is connected<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][INFO]&nbsp; &nbsp; [ThyTech] try to login ***.***.***.***:443<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][INFO]&nbsp; &nbsp; Connect to ********:443<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][INFO]&nbsp; &nbsp; Local address is *********<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;Connect success.<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Handshake LoopCounter: 0<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; 1271 bytes of handshake data received<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; InitializeSecurityContext returns 0x90312<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Send 126 bytes of handshake data<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Handshake LoopCounter: 1<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; 258 bytes of handshake data received<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; InitializeSecurityContext returns 0x0<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; SSL Handshake is successful<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; STREAM_SIZE: Header: 13	Trailer: 16, MaxMessage: 16384<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Protocol: TLS1.2<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Cipher: AES256<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Cipher strength: 256<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Hash: SHA384<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Hash strength: 0<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Key exchange: 0xae06<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][DETAIL]&nbsp; Key exchange strength: 256<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][INFO]&nbsp; &nbsp; Server subject: CN=usg40_*******<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][INFO]&nbsp; &nbsp; Server issuer: CN=usg40_********<br>[ 2018/11/19 12:45:39 ][SecuExtender Agent][ERROR]&nbsp; &nbsp;**** Error 0x800b0109 authenticating server credentials! (0x0)<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; SSL session is created<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;SSL Connection is going to be closed<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][INFO]&nbsp; &nbsp; user login device success<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][INFO]&nbsp; &nbsp; Creating secure tunnel to ***.***.***.***:443<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][INFO]&nbsp; &nbsp; Connect to ********:443<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][INFO]&nbsp; &nbsp; Local address is ********<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;Connect success.<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; Handshake LoopCounter: 0<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; 1271 bytes of handshake data received<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; InitializeSecurityContext returns 0x90312<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; Send 126 bytes of handshake data<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; Handshake LoopCounter: 1<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; 258 bytes of handshake data received<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; InitializeSecurityContext returns 0x0<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; SSL Handshake is successful<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; STREAM_SIZE: Header: 13	Trailer: 16, MaxMessage: 16384<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; Secure session is created<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; Secure session negotiation begin<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; stage 1...done<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; stage 2...done<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][WARN]&nbsp; &nbsp; The device is going to close the connection.<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][ERROR]&nbsp; &nbsp;stage 3...failed (0x0)<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][ERROR]&nbsp; &nbsp;Failed to create security tunnel (0x0)<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;SSL Connection is going to be closed<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][INFO]&nbsp; &nbsp; Connect to ********:443<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][INFO]&nbsp; &nbsp; Local address is ********<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;Connect success.<br>[ 2018/11/19 12:45:40 ][SecuExtender Agent][DETAIL]&nbsp; Handshake LoopCounter: 0<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][DETAIL]&nbsp; 1271 bytes of handshake data received<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][DETAIL]&nbsp; InitializeSecurityContext returns 0x90312<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][DETAIL]&nbsp; Send 126 bytes of handshake data<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][DETAIL]&nbsp; Handshake LoopCounter: 1<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][DETAIL]&nbsp; 258 bytes of handshake data received<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][DETAIL]&nbsp; InitializeSecurityContext returns 0x0<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][DETAIL]&nbsp; SSL Handshake is successful<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][DETAIL]&nbsp; STREAM_SIZE: Header: 13	Trailer: 16, MaxMessage: 16384<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][INFO]&nbsp; &nbsp; logout message has sent<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][DEBUG]&nbsp; &nbsp;SSL Connection is going to be closed<br>[ 2018/11/19 12:45:41 ][SecuExtender Agent][DETAIL]&nbsp; Connection ends.

This just occurs with AD Users which validate properly within the GUI. Local users connect normally without issue. 

Auth Method is setup with Local and Group AD

Router Log just shows this 
<table><tbody><tr><td><div>1</div></td><td><div>2018-11-20 11:51:25</div></td><td><div>notice</div></td><td><div>User</div></td><td><div>User ******(MAC=-) from http/https has logged out Device</div></td><td><br></td><td></td><td><br></td></tr><tr><td><div>2</div></td><td><div>2018-11-20 11:51:25</div></td><td><div>notice</div></td><td><div>SSL VPN</div></td><td><div>User ******* from http/https is connecting SSL tunnel.</div></td><td></td><td></td><td><br></td></tr><tr><td><div>3</div></td><td><div>2018-11-20 11:51:25</div></td><td><div>notice</div></td><td><div>User</div></td><td><div>User ******(MAC=-) from http/https has logged in Device</div></td></tr></tbody></table>
This is a USG 40 running 4.32. Something similar is also occurring on a USG 20 - VPN

Server is 2012 R2 in both cases. 

All Replies

  • Zyxel_Emily
    Zyxel_Emily Posts: 1,278  Zyxel Employee
    First Anniversary 10 Comments Friend Collector First Answer

    Hi @Thysmith,

     

    AD user is able to establish SSL VPN to USG40.


    Make sure ad-users is in selected user in SSL VPN policy.


    If you’re using the default Authentication Method rule, make sure “group ad” is on the list.


    If you create another rule(ex: new_auth) in Authentication Method with “group ad”, remember to select the new created rule (ex: new_auth) in CONFIGURATION > System > WWW > Service Control > Authentication.


    The latest firmware is sent to you in the private message. 
    If AD user is still unable to build SSL VPN, please feel free to let me know and send the remote access information to me via private message.
  • Thysmith
    Thysmith Posts: 16  Freshman Member
    First Anniversary 10 Comments Friend Collector
    Hi Emily, Appears the Firmware update you sent me resolved the issue! Thank you so much!
  • Zyxel_Emily
    Zyxel_Emily Posts: 1,278  Zyxel Employee
    First Anniversary 10 Comments Friend Collector First Answer

    Good to hear the issue is resolved.   =)
  • I'm also having a similar issue, running firmware V4.32(ABAQ.0) on USG20-VPN
    Is there a newer firmware?\

  • Zyxel_Emily
    Zyxel_Emily Posts: 1,278  Zyxel Employee
    First Anniversary 10 Comments Friend Collector First Answer

    The firmware is sent to you via private message.
  • Thysmith
    Thysmith Posts: 16  Freshman Member
    First Anniversary 10 Comments Friend Collector
    Hi Emily, Some of my users are still having quite a bit issues connecting. The new firmware you provided did have good results but it is still hit and miss, any other suggestions?
  • Zyxel_Charlie
    Zyxel_Charlie Posts: 1,034  Zyxel Employee
    First Anniversary Friend Collector First Answer First Comment
    @Thysmith
    Regarding to your description, some of users faced the issue, others did not.
    You may check issue account on device.
    Go to AAA server, and press test.

    If the account is in the AD group, the result will show as below

    Or you need to make sure the account already added in your own AD server.
    Charlie
  • Thysmith
    Thysmith Posts: 16  Freshman Member
    First Anniversary 10 Comments Friend Collector
    Haha, that is definitely not the issue.

    What I am seeing is this:

    I am actually now trying it with a Local User Account (Nick and a Domain account NickW)

    They both show as logged in on this page of the router. 

    BUT

    Aint Nobody home. 

    I get this but nothing else in the logs 


    (hope you can see that)
  • Thysmith
    Thysmith Posts: 16  Freshman Member
    First Anniversary 10 Comments Friend Collector
    edited January 2019
    It Appears that 4.33 dropped today and I noticed SE 4.0.3.0. So far things worked right after reboot, but I will test further and report back. 

Security Highlight