I have SMB 2.0 enabled on the NAS.įrom the command line I've been trying to mount CIFS. The NAS is running Freebsd 9.1.0.1 - Sandstorm (revision 775). But, now I can't mount any of the drives. I wanted to test using the mount command before finally getting the automount to work. With some time now to try to get Plex DNLA going again now, I decided to pick up from where I left off. Then removed Plex and removed mount commands.
So I ended up using the mount command in a script to mount the external NAS drives. Should it be Media\ Share or Media Share or "Media Share"? I'm using BASH. "//192.168.102.22/Media Share/Movies" The spaces always mess me up. I may have gotten it wrong but there is a space between the two words "Media" and "Share" ie. Note I think you have an error in your command: //192.168.102.22/Media\ Share/Moviesshould be: //192.168.102.22/Media/Share/Movies I haven't enabled NFS on the NAS as I hear it was slower than SMB, AFP or CIFS. I run TimeMachine backups to the server and for that I've been using CIFS on the Macs. They have no problem connecting to the NAS using SMB, CIFS or AFP. I enabled Windows Networking so I could connect using a bunch of Macs.
#Plex vs serviio Pc
I have only 1 windows PC and that is from work. I can't find that setting in Windows Networking. I was trying to get the basic mount command to work before I started on the automount as it looks like it would be more challenging to debug as a first step. I also had to add the domain - in my case the workgroup.
#Plex vs serviio update
Some time ago I had to update the command on my Pi to: //.uk/videos /mnt/server_videos cifs tomount,noauto,rw,iocharset=utf8,username=nick,password=my_password,uid=osmc,gid=osmc,file_mode=0770,dir_mode=0770,domain=home,vers=3.0 0 0Note the addition of the domain and vers parameters.Vers is the smb protocol and you may now find smb1 is being rejected for security reasons, but please make sure you have disabled "Windows 10 Domain Logons" in the Windows Networking Webconfig as it is no longer needed but will stop you using protocols above SMB1.
#Plex vs serviio password
I should have tried to reset the password a few iterations earlier. Now I'll try the thanks for your patience on this. Put back the original password and all is OK. Apparently the change didn't work because when I removed the password (ie. I reset the password when I started this challenge because I couldn't remember the original password. When I turned the nas log to debug, it said FAILED with error NT_STATUS_WRONG_PASSWORD Together with sec=ntmlv2 I get mount error(13): Permission denied So I think I've made some progress. I've tried all the vers options and only vers=2.0 seems to do anything better. I have tried all sorts of different combinations of options but no luck so far.
#Plex vs serviio full
Nick Howitt wrote:If you have a space in your file path, try quoting the full path: mount.cifs '//192.168.102.22/Media Share/Movies' /mnt/nas_movies -o user=useror try everything: mount.cifs '//192.168.102.22/Media Share/Movies' /mnt/nas_movies -o user=user,domain=cos,vers=3.0Another reference I bumped into said to change the " " to "\040" It can be added back at the command line if necessary. I suggest you remove it at which point it will disappear from the webconfig. You have it enabled so you have to force SMB1 in the mount.cifs command but we can see virtually no good reason to have "Force SMB1 Protocol" enabled any more, but were too scared to remove it when we renamed it in case there was an edge case which was important. "Windows Domain Logons" was renamed to "Force SMB1 Protocol".
0 kommentar(er)
