after ssl connect with secuextender, client cannot see lan1

gianluca
gianluca Posts: 3
edited April 2021 in Security
hello,
i have setup a vpn connection to my USG40.
the connection bring's up, but i cannot see the device on lan1.
the tap adapter remain on 169.254.xx.xx and not take the ip addres of SSL_VPN address range.
can you help me?
thank you
gianluca

Accepted Solution

  • gianluca
    gianluca Posts: 3
    Answer ✓
    hi Asgatlat,
    with the new firmware, the vpn is fully functionally.
    and with the old firmware, the version 4.0.2.0 give the access to the lan
    thank you for the idea, and thank to Emily for the firmware
    gianluca
«134

All Replies

  • Zyxel_Emily
    Zyxel_Emily Posts: 911  Zyxel Employee
    edited October 2018

    Hi @gianluca,

     

    Here are some tips for troubleshooting.

     

    1. Check if the SecuExtender is the latest version 4.0.3.0.

    ftp://ftp2.zyxel.com/SecuExtender/software/SecuExtender_SecuExtender_Windows%204.0.3.0.zip  

     

    2. TAP driver was signed with SHA2.

    Make sure Microsoft update KB3033929 is installed.

    http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB3033929  

    On Windows, go to Control Panel > Device Manager > Network adapters > TAP-Windows Adapter V9 for Zyxel SecuExtender > Properties > General.

    In device status, check if you get TAP driver error (Code52).


    3. Check if SSL VPN is correctly configured.

    The "Assign IP Pool" cannot overlap with IP addresses on the local networks (LAN and DMZ), the SSL user's network, or the networks you specify in the SSL VPN Network List.




  • Thnk you for response, but i have double checked the setting's, and are correct. this error (no ip to tap adapter), remain in both windows 7 and windows 10. the tap adapter is fully functionally and the KBKB3033929 is installed
    this is my configuration:

    i think i have made the correct setting's, the VPN can connect, but tyhe tap adapter remain on 169.254.xx.xx even if the software say 192.168.50.2.
    secuextender version: 4.0.3.0
    zyxel USG40 firmware version: V4.32(AALA.0)
    thank you
    gianluca



  • Asgatlat
    Asgatlat Posts: 74  Ally Member
    hi gianluca,
    i got the same problem since the 4.0.3.0.
    as i said in my previous post : 
    https://businessforum.zyxel.com/discussion/1760/secuextender-4-0-3-0-windows-not-working-vpn-connection-still-ok#latest
    the setup i described in my post is not working on every laptop...

    i think the 4.0.3.0 is blocked by usg, you can transmit data but can't recieved data
  • Zyxel_Emily
    Zyxel_Emily Posts: 911  Zyxel Employee

    Hi @gianluca,

     

    I also got the same issue as yours "TAP-Windows adapter remains on 169.254.xx.xx" when using the firmware 4.32(AALA.0) on USG40.

    After USG40 is upgraded to the latest firmware, TAP-Windows adapter gets the correct IP.

    I will send the firmware to you for verification in private message.


  • Asgatlat
    Asgatlat Posts: 74  Ally Member
    hi Emily,
    i just tried your Firmware (for my Zywall 110), it is working, the TAP adapter got IP adress and i can access to my Lan with SecuExtender 4.0.3.0 
    thank you for the fix
  • After USG40 is upgraded to the latest firmware, TAP-Windows adapter gets the correct IP.
    Hi Emily, I have the same problem with USG20, my firmware is: 4.32(ABAQ.0)

    SecureExtender 4.0.3.0, all configurations as messages above, TAP adapter remains on 169.254.x.x

    What firmware should I use?

    thank you



  • Zyxel_Emily
    Zyxel_Emily Posts: 911  Zyxel Employee

    The firmware is sent to you via private message.
  • Hello:

    i have the same problem. Please, can you send me the latest version of firmware?
    Thank you!
  • Hello, I have an USG60 with FW 
    V4.32(AAKY.0) 

    Same Problem, get noch IP Adress from the SSL 
    Range (Secuextender 3.0.4)

    do you have an Solution? Thank you

Security Highlight