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

Could not associate packet to any connection

In the firewall I see many denied as the one I attach, this is an example but I have many more.

For what is this? At first it is not affecting the communications but I see many that the requests arrive well and then the errors that I attach appear

Type of rule is 0, looking at the documentation it is a rule that generates sophos, but even so I don't understand why that error comes out.

Anyone else has happened?

This thread was automatically locked due to age.

Top Replies

rfcat_vk over 2 years ago +1 suggested

Hi, they appear to be the XG rejecting RDP attempts to connect to it, the XG does not use RDP. Basically you do not have a rule to handle the traffic. Could not associate packet is when a connection…

0 rfcat_vk over 2 years ago

Hi,

they appear to be the XG rejecting RDP attempts to connect to it, the XG does not use RDP.

Basically you do not have a rule to handle the traffic. Could not associate packet is when a connection has ended, but one end is still sending close connection packets.They can be ignored.

Ian

XG115W - v20 GA - Home

XG on VM 8 - v20 GA

If a post solves your question please use the 'Verify Answer' button.
Cancel
Vote Up +1 Vote Down

Cancel

0 Christian Garcia2 over 2 years ago in reply to rfcat_vk

I also have many denied like the one attached, this is normal same as above error?

I am having problems precisely with the IP 192.16.1.150 which is a nas and it seems strange to me so many denied ...

I also have many denied like the one attached, this is normal same as above error?

I am having problems precisely with the IP 192.16.1.150 which is a nas and it seems strange to me so many denied ...

I have created an Any -> Any -> Any rule for nas and that does not block anything to test and those blocks keep coming out




Thank you very much for the help. :-)

0 rfcat_vk over 2 years ago in reply to Christian Garcia2

Hi,

you are probably seeing a lot of timeout errors on the connection, are you able to increase the time to live for packets on the NAS?

Ian

XG115W - v20 GA - Home

XG on VM 8 - v20 GA

If a post solves your question please use the 'Verify Answer' button.
Cancel
Vote Up 0 Vote Down

Cancel
0 BeEf over 2 years ago in reply to Christian Garcia2

I'd suspect a problem with NATing.

Can you send a (physical and logical) network layout and the firewall and nat rules for 192.168.1.150 to 172.21.1.4?
Cancel
Vote Up 0 Vote Down

Cancel

0 Christian Garcia2 over 2 years ago in reply to BeEf

Good Morning.

I have managed to solve the problem of access to the nas by extending the time of "Tcp Conn. Establishment Idle Timeout" in the XG, I see that the drops of rule 0 of the XG continue to appear but there is no longer so much latency and the nas can be accessed correctly .

Thank you!!