the problem here (in my pc) it's not something new... here, i get firewalled each time core get busy for a long time, since when core is frozen for too long nl seems to move both tcp and udp ports to set port +1, those ports are not opened in my router=firewalled.
here core geet often busy for several reasons, the ones i recon are:
1. there are too many shared files and, at some point during a long session, something breaks and core get busy.
2. neoshare is on, sometyhing goes wrong and core get busy.
3. neokad process is trying to use an insane resources, taskmanger shows Neokad. exe CPU 30, everything get unstable and busy, and after a long time this stance leads to mulekad filewalled.
can you see anyone of these behaviours?
close NL, check taskmanager for all neoloader related processes to be faded and restart always fix this. btw i always try to kill both mulekad and neokad processes before restarting, in order to fix without restart, but it is not so effective (it couldn't work).