Protocol Control blocking incorrect ports
I just spent days figuring out why our outside staff could not access our Filemaker server. Filemaker uses port 5003 and has been doing so for well over a decade or more.
I finally located in our Untangle reports that Protocol Control was wrongly associating port 5003 and port 53 with the predefined Soulseek and Xunlei P2P Protocols. I have all P2P protocols set to block. Why Xunlei should be associated with DNS port 53 is beyond me.
Please see attached Untangle report page.
|