Hi All,
A customer is thinking of having me build him a file server. He has 3 windows 10 workstation that all need to see that same YUGE drawing files. Plus backup would be nice.
So since I am allergic to Windows servers (the make me say "bad" words), I thought of a FC29 Samba server.
Then it occurred to me, why not put the shoe on the other foot. If there is an NFS client for Windows, why not use NFS? Any benefit of using NFS over CIFS on this scenario?
You thoughts?
-T
On 12/7/18 6:37 PM, ToddAndMargo via users wrote:
So since I am allergic to Windows servers (the make me say "bad" words), I thought of a FC29 Samba server.
Then it occurred to me, why not put the shoe on the other foot. If there is an NFS client for Windows, why not use NFS? Any benefit of using NFS over CIFS on this scenario?
It looks like it's possible. You need to turn on the "Services for NFS". I have no idea how well it works, but there is a bit of configuration involved.
On 12/8/18 10:37 AM, ToddAndMargo via users wrote:
Hi All,
A customer is thinking of having me build him a file server. He has 3 windows 10 workstation that all need to see that same YUGE drawing files. Plus backup would be nice.
So since I am allergic to Windows servers (the make me say "bad" words), I thought of a FC29 Samba server.
Then it occurred to me, why not put the shoe on the other foot. If there is an NFS client for Windows, why not use NFS? Any benefit of using NFS over CIFS on this scenario?
You thoughts?
Well, so as not to have to make changes to the client's workstations I would use the protocol that is supported by default by windows. So, I would use CIFS.
That is why, even though I only use it for testing, my NAS is configured to offer both NFS and CIFS services.
On 08Dec2018 10:57, Ed Greshko ed.greshko@greshko.com wrote:
On 12/8/18 10:37 AM, ToddAndMargo via users wrote:
A customer is thinking of having me build him a file server. He has 3 windows 10 workstation that all need to see that same YUGE drawing files. Plus backup would be nice.
So since I am allergic to Windows servers (the make me say "bad" words), I thought of a FC29 Samba server.
Then it occurred to me, why not put the shoe on the other foot. If there is an NFS client for Windows, why not use NFS? Any benefit of using NFS over CIFS on this scenario?
You thoughts?
Well, so as not to have to make changes to the client's workstations I would use the protocol that is supported by default by windows. So, I would use CIFS.
That is why, even though I only use it for testing, my NAS is configured to offer both NFS and CIFS services.
Also, you may find that some Windows locking protocols don't work over NFS. And Windows ACLs are different to UNIX ACLs. If they're running Windows native software I'd imagine that NFS _may_ cause trouble.
But by all means _offer_ both. You may find one is faster than the other.
Cheers, Cameron Simpson cs@cskk.id.au
ToddAndMargo via users wrote:
Then it occurred to me, why not put the shoe on the other foot. If there is an NFS client for Windows, why not use NFS? Any benefit of using NFS over CIFS on this scenario?
Samba does cifs much better than windows supports nfs in my experience.
Short answer: stick with samba/cifs
-- Rex
On 12/7/18 6:37 PM, ToddAndMargo via users wrote:
Hi All,
A customer is thinking of having me build him a file server. He has 3 windows 10 workstation that all need to see that same YUGE drawing files. Plus backup would be nice.
So since I am allergic to Windows servers (the make me say "bad" words), I thought of a FC29 Samba server.
Then it occurred to me, why not put the shoe on the other foot. If there is an NFS client for Windows, why not use NFS? Any benefit of using NFS over CIFS on this scenario?
You thoughts?
-T
Thank you for all the help! I will stick with CIFS
-
Cameron Simpson -
Ed Greshko -
Rex Dieter -
Samuel Sieb -
ToddAndMargo