SiMPLE | Forum

bud

maestro

Reputation: +1842

Location: shangri la

Registered: 2012-07-07

Posts: 3,960

Website

slow nfs share in windows

Anybody have any advise how to speed up windows slow nfs handling?

Trench

Member

Reputation: +130

Registered: 2014-05-05

Posts: 221

Re: slow nfs share in windows

I don't do NFS access from Windows... what is the nature of how NFS access is being performed?  e.g. Just a desktop application doing its own thing over winsock (like Filezilla), or something that integrates with Windows file system APIs by installing a network provider and network redirector that supports NFS?

For the latter, slowness in multiple-redirector environments can come from Windows trying to prove that the UNC to an NFS server you provided is not a Microsoft DFS root and/or is not for one of the other installed network redirectors or providers.  Enabling the Microsoft "DisableDFS" policy can help the first part, and configuring the Windows Network Provider Order to push your NFS network provider higher in the order can mitigate the second part.

Arkos

Sedmin

Reputation: +2783

Registered: 2014-06-06

Posts: 7,048

Re: slow nfs share in windows

..

https://docs.microsoft.com/en-us/window … ile-server

...

Perhaps this helps you?

https://github.com/winnfsd/winnfsd/issues/59

...

Or this

http://blog.malayter.com/2012/05/fixing … tween.html

...

Last edited by Arkos (2018-11-14 15:57:03)

bud

maestro

Reputation: +1842

Location: shangri la

Registered: 2012-07-07

Posts: 3,960

Website

Re: slow nfs share in windows

Thanks for the suggestions, gonna check it out.
The thing is that windows remote desktop use the nfs protocol if i understand it right, and its just so painfully slow (1Mb speed max), both in negotiating the connection and in the transmission itself. I found that one way of getting around the slow transmission speed, is to open up multiple "channels" a bit like the torrent protocol, but standard software doesnt have the means to use this. I would have to build some collect/cache thingy to use inbetween. Much to complex.

Arkos

Sedmin

Reputation: +2783

Registered: 2014-06-06

Posts: 7,048

Re: slow nfs share in windows

...

Like this?

MaxConcurrentConnectionsPerIp

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Rpcxdr\Parameters\MaxConcurrentConnectionsPerIp

The default value of the MaxConcurrentConnectionsPerIp parameter is 16. You can increase this value up to a maximum of 8192 to increase the number of connections per IP address.

Btw. All those tweaks for NFS from Microsoft are for below protocol 4.1

> No registry tuning is required for NFS v4.1 protocol.

...

Could it be, that HaneWinNFS handles this the same way? A License is 19.- for privat use, 29.- for commercial.

...

I guess, if you go through Microsofts NFS Performance Tipps, you can get the same result as with HaneWinNFS.

HanewinNfs has a 30 day Trial time. (Shareware)

https://www.hanewin.net/nfs-e.htm

(Multithreaded implemenation with a configurable number of UDP server threads and one thread per TCP connection.)

...

Last edited by Arkos (2018-11-14 23:04:26)

Trench

Member

Reputation: +130

Registered: 2014-05-05

Posts: 221

Re: slow nfs share in windows

The thing is that windows remote desktop use the nfs protocol if i understand it right...

Hmm, that is not something I would have suspected, or have ever heard referenced, nor see supported in Microsoft documentation regarding the RDP protocol.  Drive redirection, which has been there since the XP version of RDP, happens over the RDP protocol itself to my knowledge.  Any pointers to where you saw the suggestion that NFS is being employed as part of RDP drive redirection?

There is a network provider involved, but at least on my Windows 10 machines, the "Microsoft Remote Desktop Session Host Server Network Provider" is already at the top of the network provider order by default.  If it's not already at the top on your machine, no harm in pushing that to the top of the order just to make sure it doesn't have any substantial effect.  (This would be on the machine you're Remote Desktop'ing into; not on the machine you're running the MSTSC.EXE client on.)

But I don't expect that's the issue; at best it could only improve the initial connection time, but won't/can't have any effect on the sustained transfer rate.

Remote Desktop drive redirection multiplexes through the RDP connection itself, and "is just slow" in my experience.  The opportunity to speed it up is to NOT use RDP drive redirection, and instead make your RDP client machine and RDP host machine access the files in question through a network-accessible share that both computers can access.  Not because their connection bandwidth to that share will be any greater or different than the bandwidth they already had access to; but because they won't be using the RDP protocol to redirect the file system access.

In other words, put the files on a CIFS share of the RDP host machine, and access/push files to that share over CIFS/SMB rather than over RDP.  RDP file system redirection and printer redirection is made for convenience and not performance, in my opinion and experience.  Not that that's helpful information.

Arkos

Sedmin

Reputation: +2783

Registered: 2014-06-06

Posts: 7,048

Re: slow nfs share in windows

...

Yes, Windows Remote Desktop useses RDP

https://docs.microsoft.com/en-us/window … hosts#apps

...

Possible fix?

http://www.johndstech.com/2017/microsof … em-solved/

...

Last edited by Arkos (2018-11-15 01:26:30)

iCQ

Spammer

Reputation: +544

Location: Netherlands

Registered: 2017-07-31

Posts: 1,967

Re: slow nfs share in windows

Long time ago i used NFS and RDP. That time all i did to boost was allow it to make/use more connections/ports with the MaxConcurrentConnections value and such (also make sure the firewall/routers lets it happen).

Now i like the NX protocol a lot more. Of course vnc been there too...

https://en.wikipedia.org/wiki/NX_technology
https://www.nomachine.com
https://www.nomachine.com/download

NoMachine and other applications lets you secure (SSH) connect to desktops, devices and files. Beware on older Android devices you have to enable "install from unknown sources" and get the official Android APK from the NoMachine website.

SFTP is not going to help you either i think, samba, active directories... i dunno what u doing. Im sorry, i cant help much here. Have you thought about setting up a VPN at that box?

Last edited by iCQ (2018-11-15 06:56:13)

nämeless

Semi-corrupt admin

Reputation: +2600

Location: Nizhny Novgorod, Russia

Registered: 2012-09-30

Posts: 9,767

Re: slow nfs share in windows

Anybody have any advise how to speed up windows slow nfs handling?

Try this.

https://yadi.sk/d/Yd0946GQiPKXp

bud

maestro

Reputation: +1842

Location: shangri la

Registered: 2012-07-07

Posts: 3,960

Website

Re: slow nfs share in windows

...

Yes, Windows Remote Desktop useses RDP

https://docs.microsoft.com/en-us/window … hosts#apps

...

Possible fix?

http://www.johndstech.com/2017/microsof … em-solved/

...

Testing!!

bud

maestro

Reputation: +1842

Location: shangri la

Registered: 2012-07-07

Posts: 3,960

Website

Re: slow nfs share in windows

Anybody have any advise how to speed up windows slow nfs handling?

Try this.

https://yadi.sk/d/Yd0946GQiPKXp

Will do!

bud

maestro

Reputation: +1842

Location: shangri la

Registered: 2012-07-07

Posts: 3,960

Website

Re: slow nfs share in windows

In other words, put the files on a CIFS share of the RDP host machine, and access/push files to that share over CIFS/SMB rather than over RDP.  RDP file system redirection and printer redirection is made for convenience and not performance, in my opinion and experience.  Not that that's helpful information.

Well yes it is good advice, the problem in my case also is when i try to stitch together different boxes over internet, some running Linux and some windows

Trench

Member

Reputation: +130

Registered: 2014-05-05

Posts: 221

Re: slow nfs share in windows

Sure, understandable.  My main concern/response was to the statement "The thing is that windows remote desktop use the nfs protocol if i understand it right".  Since to my knowledge the answer is "No, RDP does not use NFS to perform file system redirection", and therefore doing specifically NFS-related speed-up things with the expectation it would improve RDP file system redirection seemed misguided.

If CIFS/SMB isn't an option (not that Linux is unable to connect to CIFS/SMB shares), the analog to what I was suggesting is that you would change the Windows machine acting as the Remote Desktop host to connect to the shared files host directly on it's own.  Instead of mapping to the shared files host on your Remote Desktop client machine, and then expecting Remote Desktop file system redirection to pass-through that file system access to the Remote Desktop host machine.  (Since I presume that's the meaning of the screen shot you posted of Remote Desktop Connection's drive redirection.)

That specifically CIFS/SMB would be used instead wasn't important; the important part was not "doubly-redirecting" by sending the shared file system access through the extra layer of RDP file system redirection.  It's damn convenient to do it that way, but not fast.

Arkos

Sedmin

Reputation: +2783

Registered: 2014-06-06

Posts: 7,048

Re: slow nfs share in windows

...

The main thought/use of those shares was sharing wide, not fast.

I guess you can speed up each share, not depending on the OS, becasue i don't think, (in your case), xxx people must/will have access at the same time.

...

bud

maestro

Reputation: +1842

Location: shangri la

Registered: 2012-07-07

Posts: 3,960

Website

Re: slow nfs share in windows

Tried the links Arkos posted and the remote desktop actually feels alot faster now, 25% of networkspeed in lan, but it was just a quicktest with an old machine, so it can propably work even better with some ssd-drives. So overall much better

I dont know why i mixed it up with nfs with RDP, propably a brain fart or something.

I think if i want to use windows CIFS/SMB with linux´s Samba share, im gonna need a vpn tunnel so they can be within the same network range, and then it getting a bit much pieces as i already have other vpn networks for other uses.

Last edited by bud (2018-11-17 00:23:44)