Sascha_Walther  Freshman Member

Problem solved, thx to the perfekt service from the Zyxel Support. There was an missing policy routing entry to route the backtraffic into to tunnel instead of to the internet from a later rule. thx a lot for your support, all.

Zywall should replay, I'll have a look.

Hi, I do note use Windows. I think it is not a problem of the smb service it self because I uses traceroute and ping to try to reach the NAS. Also because I can't reach the webinterface and so on.

Hello, thx for answering, here are the screens... I'm not sure what is the output information about that? regards Sascha

Good morning, and thank you for replaying to my Problem. I think i did like you mentioned with the tutorial. i was very hard to find the right settings but now I yust need to power on the fritzbox and get an connection. I can see the connection in the webinterface. Then it is also possible to access the zywall with the…

hm, ui die 2200er ist schon ne andere Größenordnung. Danke für Deinen Tipp! Grüße Sascha

Works with this configuration.

Hello, some problem here :( -also Zywall110 with AVM Fritzbox. zywall using fixed ip and Fritzbox dynamic one. Phase1 is ok but no connection will be established?? Any Ideas? thx Sascha

Hi @@Zyxel_Stanley I understand and this is exactly my problem. Why changed this? Or other question why is this not an option to choose how to work? Now it is not possible to use mutli-session apps like ftp etc. over more then one connection. :( Thanks for answering Sascha

Hello, thank you for answering. In Firmware V4.30 (AAAA.0) it works like I wanted to and like it does since serveral years. As you see I do failover and Load Balancing. LB primary with cable and dsl and if both not available it moves to passiv (mobil) connection. The Problem is that in the new firmware since V4.31 (AAAA.0)…

Helo, sorry I opend second Thread, but I explained there more detailed the problem... https://businessforum.zyxel.com/discussion/2310/zywall-110-trunk-load-sharing Maybe have a look to understand my problem which already exists in 4.33