winnfsd / vagrant-winnfsd

Manage and adds support for NFS for Vagrant on Windows.

Other

567 stars 62 forks source link

Add a note to the readme about opening firewall ports #94

Open yurimorini opened 8 years ago

yurimorini commented 8 years ago

Windows10 block winnfsd by default and the system silently with no errors (the process is started, but no communication is done). This can be not straightforward, so why do not add a sort of reminder in the README after installation note?

Remember to add appropriate firewall rules to your system ensuring winfssd is not blocked. 
Add a rule targeting the winnfsd binary to accept either outbound and inbound connection. 
Binary is located at:

%USERPROFILE%\.vagrant.d\gems\gems\vagrant-winnfsd-{yourversion}\bin

Do you eventually accept a pull request about this ?

Asked also here: #70

marcharding commented 8 years ago

This should be done by the plugin on the first run, see https://github.com/winnfsd/vagrant-winnfsd/blob/master/lib/vagrant-winnfsd/plugin.rb#L62. Maybe it is an UAC problem (not sure).

Nevertheless: An additional info in the README does not hurt. I'll add that with the next release.

yurimorini commented 8 years ago

Thanks, I'm quite sure no UAC popup was shown. Maybe it's my git bash configuration.

leem32 commented 6 years ago

Just had the same problem. Eset Smart Security Firewall was causing nfs to connection timeout. Adding an exception fixed the issue and now I'm fully synced with CentOS guest from my Windows 7 host. The default sync wasn't working for me from guest -> host. It only worked from host -> guest. Using latest vagrant/virtual box. With winnfsd sync is now bi-directional :)