CDS  Freshman Member

So - nearly one year later - how is the plan going?

Same issue here on my USG210. After upgrading from 4.33 to 4.35 fallback to default config with labling the previous config as "bad". I neither have time nor do I feel like re-configuring everything from scratch, so for now I'm bach at 4.33 .Any ideas on how to identify what is the issue in my conig?

Does anyone else have the problem that after upgrating 4.33 --> 4.35 the config is considered "bad" by the USG - and the default config loaded?This happens consistently for me ...Any idea how to find out what is "bad" and why?

Well,appearently my running 4.33 config is considered "bad" by 4.35 - of course without any indication why.What a great Job Zyxel! :s

Well, the problem is not how to create the traces, but more how physically create both at the same time - while the PC with Secuextender is in a physically different location than the USG (otherwise I wouldn't need a VPN connection:...) But anyway on update: I updated to V4.33 yesterday. I still can not get SSL VPN to…

... upgraded from V4.32 without any issues awell...

Did you try clearing the Browser cache?

Me aswell. I struggle to now create the requested logs from Secuextender and USG at the same time .....

AH THANKS!Changing the local policy did it.Strange how this error is shown in log log ..

If this is the only reason, why does the log stat in line 23 " Tunnel [SCHAUDELNET_Fedderwardersiel] Phase 2 proposal mismatch" . THIS is the VPN1 in my original description and the connection which is NOT supposed to be used for L2TP connections. These both VPN's intentionally are using different Local policies.

The Log: L2TP_Gate is the correct gateway, but the corresponding connection is L2TP_Connection. No. Date/Time Source Destination Message 1 2019-01-10 19:27:38 MobileClient_IP:3169 Server_IP:500 The cookie pair is : 0x9b7d21976a5a4f83 / 0x0000000000000000 2 2019-01-10 19:27:38 MobileClient_IP:3169 Server_IP:500 Recv Main…

No. I mean the exact Problem which is described in the beginning of this thread. The connection from the Secuextender fails with the error "Can't get authentication token".

Well, the new Thread seems to cover a different issue. I have the "Can't get authentication token" problem an my USG210 running on 4.32(AAPI.0)ITS-WK48-r86397 . It there anything newer which fixes this?

Hi! Please describe in more detail: You are connected though a SSL-VPN connection, and try to access the config page? If so, did you grant Admin Service to your SSL-VPN Subnet? (Configuration->System->WWW->Admin Service Control)