after ssl connect with secuextender, client cannot see lan1
Accepted Solution
-
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 lanthank you for the idea, and thank to Emily for the firmwaregianluca1
All Replies
-
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.
See how you've made an impact in Zyxel Community this year!
https://bit.ly/Your2024Moments_Community1 -
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 installedthis 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.0zyxel USG40 firmware version: V4.32(AALA.0)thank yougianluca
0 -
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 data1 -
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.
See how you've made an impact in Zyxel Community this year!
https://bit.ly/Your2024Moments_Community0 -
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 fix0 -
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 lanthank you for the idea, and thank to Emily for the firmwaregianluca1
-
Hi Emily, I have the same problem with USG20, my firmware is: 4.32(ABAQ.0)After USG40 is upgraded to the latest firmware, TAP-Windows adapter gets the correct IP.
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
0 -
See how you've made an impact in Zyxel Community this year!
https://bit.ly/Your2024Moments_Community1 -
Hello:i have the same problem. Please, can you send me the latest version of firmware?Thank you!
0 -
Hello, I have an USG60 with FW
Range (Secuextender 3.0.4)V4.32(AAKY.0)
Same Problem, get noch IP Adress from the SSL
do you have an Solution? Thank you0
Categories
- All Categories
- 415 Beta Program
- 2.4K Nebula
- 148 Nebula Ideas
- 96 Nebula Status and Incidents
- 5.7K Security
- 262 USG FLEX H Series
- 271 Security Ideas
- 1.4K Switch
- 74 Switch Ideas
- 1.1K Wireless
- 40 Wireless Ideas
- 6.4K Consumer Product
- 249 Service & License
- 387 News and Release
- 84 Security Advisories
- 29 Education Center
- 10 [Campaign] Zyxel Network Detective
- 3.5K FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 85 About Community
- 73 Security Highlight