This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Remote desktop/access suddenly stopped working after system update

Hey guys - I am totally baffled - my UTM 9 box has been working beautifully without any issues and suddenly I lost the ability to use remote access/desktop via my dynamic DNS service after the latest 9.407-3 update.

I checked my NAT rules and nothing has changed but firewall log is throwing out the following errors when I try to use remote desktop:

2016:10:03-12:17:44 homestation ulogd[4782]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60003" outitf="eth0" srcmac="00:25:90:f4:54:61" srcip="204.79.197.200" dstip="192.168.1.101" proto="6" length="40" tos="0x00" prec="0x00" ttl="64" srcport="443" dstport="64961" tcpflags="RST"

 

This message comes up when I try to access my Plex Server remotely:

2016:10:03-12:24:44 homestation ulogd[4797]: id="2001" severity="info" sys="SecureNet" sub="packetfilter" name="Packet dropped" action="drop" fwrule="60001" initf="eth0" srcmac="02:ff:70:00:07:0b" dstmac="00:25:90:f4:54:61" srcip="192.168.1.118" dstip="192.168.1.199" proto="17" length="30" tos="0x00" prec="0x00" ttl="64" srcport="23235" dstport="5351"



This thread was automatically locked due to age.
Parents
  • Jay, normally, the "RST" packets can be ignored.  This looks like the UTM's connection tracker just thought the conversation that 192.168.1.101 was having with 204.79.197.200 was already concluded.

    What do the .118 and .119 IPs represent in the second log line?

    Cheers - Bob

Reply
  • Jay, normally, the "RST" packets can be ignored.  This looks like the UTM's connection tracker just thought the conversation that 192.168.1.101 was having with 204.79.197.200 was already concluded.

    What do the .118 and .119 IPs represent in the second log line?

    Cheers - Bob

Children