You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I use this firewall (TinyWall) on Windows 7 that only allows specific .exe files to communicate over the network. Despite allowing megacmd.exe to bypass the firewall, it still has connection issues when the firewall is on.
My question is this: What specifically needs to be allowed to communicate through the firewall? It's not megacmd.exe apparently.
Thanks for any input.
The text was updated successfully, but these errors were encountered:
Basically the .exe file was located in a symlink directory I created. My firewall apparently didn't like symlinks, and when I directed it to the real directory instead it worked fine.
So I use this firewall (TinyWall) on Windows 7 that only allows specific .exe files to communicate over the network. Despite allowing megacmd.exe to bypass the firewall, it still has connection issues when the firewall is on.
My question is this: What specifically needs to be allowed to communicate through the firewall? It's not megacmd.exe apparently.
Thanks for any input.
The text was updated successfully, but these errors were encountered: