Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Version Issue #81

Open
RyzaJr opened this issue Aug 4, 2015 · 1 comment
Open

Windows Version Issue #81

RyzaJr opened this issue Aug 4, 2015 · 1 comment

Comments

@RyzaJr
Copy link

RyzaJr commented Aug 4, 2015

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.

@RyzaJr
Copy link
Author

RyzaJr commented Aug 5, 2015

Actually, I solved this issue.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
@RyzaJr and others