SSL VPN connected but IP address not assigned to TAP-device
So, I have a strange one:
Two years ago I deployed an USG40W which worked flawlessly. To access this client remotely I have been using SecuExtender without a problem. But now the VPN stopped working - well kind off.
SecuExtender connects without a problem but the IP address from the SSL VPN pool is not assigned to the TAP network device. The route gets added but with no IP address.
Strangely enough: The VPN works from my laptop with the very same settings. Only difference is that on my laptop I'm running Windows 10 Ver. 1803 and on my desktop Ver. 1809. The rest is the very same - including the SecuExtender version.
To make matters even more complicated: on my desktop (which has problems to establish the connection) I can connect to another USG40 just fine. The difference there is that on the working USG I have firmware 4.25 and on the non working USG I have firmware 4.32.
You guys have any idea?
We fix some SSL VPN related issues in the latest firmware.
I sent the firmware to you via private message.
Please upgrade to this version to check if SSL VPN is working fine.
Hi EmilyThank you for your feedback. I did get your message.Unfortunately I had no time to update the firmware yet as this is a productive system and I have to schedule the downtime with my client.I will update this thread once I have further informations.I'd still like to ask: why is the vpn working with an older firmware?0
Hi EmilyI was able to install the new firmware that you sent me.Sadly this did not fix my problem. I still don't get an IP address for the TAP network device. Further ideas?Steve0
I want to analyze the SSL VPN connection from my PC to your device, so please private message the details of remote session.(The USG's Wan IP and username/password)
I do have the exact same issue. We use the USG20 on the latest firmware (checked today) and secuextender is working without any problems on 3 win10 machines. then i have two other clients, also win10, the connection works flawlessly, the routes are set but the TAP Interface gets no IPs and says "no network connectivity", both on ipv4 and ipv6 i get no IP.
I tested locally without any issue. The firmware is 3.30(BDQ.9).
Can you private message your configuration to me.
HelloNo actually not. I could not get this to work - even with the firmware from Emily.But I setup a new Windows 10 virtual machine with version 1809 and this machine is connecting flawlessly and even getting an IP. So I guess something with my OS is fu**ed up. But I won't reinstall - I'll use the VM for now.0
Does the Assign IP pool not conflict with your LAN?
Try a range 192.168.139.1-192.168.139.14 and in global settings for network extension local IP to 192.168.139.1
- 8.1K All Categories
- 1.6K Nebula
- 60 Nebula Ideas
- 54 Nebula Status and Incidents
- 4.4K Security
- 224 Security Ideas
- 963 Switch
- 45 Switch Ideas
- 868 WirelessLAN
- 20 WLAN Ideas
- 5.2K Consumer Product
- 139 Service & License
- 268 News and Release
- 95 Success Stories
- 53 Security Advisories
- 12 Education Center
- 573 FAQ
- 273 Nebula FAQ
- 132 Security FAQ
- 73 Switch FAQ
- 72 WirelessLAN FAQ
- 7 Consumer Product FAQ
- 34 Nebula Monthly Express
- 71 About Community
- 44 Security Highlight