I have the same issue now. I upgraded from a RB750gr3 on v7.8 (which I ran for almost a month), zero issues on that one.
I upgraded - now I have a RB5009 on v7.8. Every 65 sec, the RDP connection would disconnect. Happened from two systems on my network - One Win 10, one Win 11 (at least windows has problems - I do not RDP out form Mac or iOS so can’t attest to that). I broke out wireshark which showed TCP RST on both sides.
FWIW, the remote side is a combination of Win 2012 R2 server, Win 2016, Win 2019.
At first I was skeptical extending udp-timeout from the default 10s to 20s would fix it, but it has. - I assumed the command prefixed with
/ip/firewall/
was for hte IPv4 stack. But somehow, this command is for both IPv4 AND IPv6 stack?
This is the new updated setting (see udp-timeout) that makes my RDP connections stable:
/ip firewall connection tracking
set enabled=auto generic-timeout=10m icmp-timeout=10s loose-tcp-tracking=yes tcp-close-timeout=10s \
tcp-close-wait-timeout=10s tcp-established-timeout=1d tcp-fin-wait-timeout=10s tcp-last-ack-timeout=10s \
tcp-max-retrans-timeout=5m tcp-syn-received-timeout=5s tcp-syn-sent-timeout=5s tcp-time-wait-timeout=10s \
tcp-unacked-timeout=5m udp-stream-timeout=3m udp-timeout=20s
Can someone clarify if the settings updated with
/ip/firewall/connection/tracking
are applying to both the ip4 AND ip6 stacks on the Mikrotik?
This is quite clearly a bug, if it works on Rb750gr3 and not on Rb5009.
EDIT: Just experienced the very same fault on a RB750gr3 running 7.8.