Comments

• Hi @MitatOnge I checked and the Anydesk connection is working now. Thank you for your help. Ralph

  in Problem Connection to Any-Desk-Server by using DPI-SSL Comment by Ralph February 2022
• Hi @Enzino78 Thank you for your suggestion. I will test it with us. Ralph

  in Problem Connection to Any-Desk-Server by using DPI-SSL Comment by Ralph January 2022
• Hi @Enzino78 I tested it with your suggestion. Unfortunately without success. ☹️

  in Problem Connection to Any-Desk-Server by using DPI-SSL Comment by Ralph January 2022
• Hi @BWC & @MitatOnge Thanks for your answer. I looked at the packages. There are a whole range of IPs that are being tried. You could then exclude them all. But that's not a good permanent solution for me. I am currently in contact with Anydesk support. Let's see what comes from there. In App Control I found anydesk…

  in Problem Connection to Any-Desk-Server by using DPI-SSL Comment by Ralph January 2022
• @BWC I monitor my traffic and found some dropped packets. Often Drop Code 737 and some 727 and 166. in:X0*(interface), out:--, DROPPED, Drop Code: 737(Packet dropped - cache add cleanup drop the pkt), Module Id: 25(network), (Ref.Id: _2293_dbdifBeeDmfbovq

  in Problem Connection to Any-Desk-Server by using DPI-SSL Comment by Ralph January 2022
• @BWC The AnyNet Relay is exclused. Also the .anydesk.com and the IP 239.255.102.18 as the default value connection (According Anydesk). In the Connection Failures there are no blocked connections that I could assign to Anydesk.

  in Problem Connection to Any-Desk-Server by using DPI-SSL Comment by Ralph January 2022