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

Use of TCP #31

Open
GoogleCodeExporter opened this issue Jul 13, 2015 · 1 comment
Open

Use of TCP #31

GoogleCodeExporter opened this issue Jul 13, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Hello,

NFSv3 and NFSv2 classes (as INFS interface implementations) create the 
connection based on UDP transport protocol. Could it be possible to enable TCP 
as well (and also as setting in the GUI program)? If I change the protocol 
value in source, should it work correctly? Or is there any problem with that?

Thanks,
Jan

Original issue reported on code.google.com by jan.pi...@gmail.com on 8 Nov 2012 at 2:55

@GoogleCodeExporter
Copy link
Author

In my experience this is related to performance. I had been using Services For 
Unix 3.5 for many years, in different environments. Usually, if I let SFU be in 
default UDP mode, the client computer freezes from time to time - usually when 
opening explorer or the mounted drive. For this reason I change it to TCP the 
first thing after installation. I just tried NekoDrive, and observed the same 
behaviour: random freezes upon opening explorer or file-open dialogue, 
sometimes lasts 10 minutes. I ascribe this to lack of TCP support, although I 
could not reason why UDP would more likely to cause freezes. All testings are 
always done in LAN, with no latency problems.

Original comment by zhangwe...@realss.com on 18 Aug 2014 at 4:25

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

No branches or pull requests

1 participant