this post was submitted on 04 Jun 2024
32 points (100.0% liked)

Selfhosted

40313 readers
185 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

I am running a NAS that needs to connect to a server (the NAS isn't powerful enough). I also need to connect my NAS to a Windows, Mac, and Linux device (Linux being the most important, then Mac, then Windows). Out of SMB, FTP, and NFS, which one would be the best, quickest, and most secure for my situation? My NAS supports multiple sharing protocols, but I don't want to deal with mixed up permissions and conflicts later on.

you are viewing a single comment's thread
view the rest of the comments
[–] Shadow@lemmy.ca 7 points 5 months ago (1 children)

SMB.

The windows nfs implementation sucks, but everything talks SMB.

[–] just_another_person@lemmy.world 5 points 5 months ago

It's going to be SMB just because you want things to work, and user perms synced to the host. It's the same Samba implementation anyway.