Hi
I have a Raspberry Pi computer. I wish to use it as a streaming music player, taking music stored on my Nas4Free box. I am trying out the RaspyFi distribution, which is intended as a music player - it has no video or photo playback options. It can be controlled from a (tablet PC) web browser, or a local keypad and LCD text display.
My problem is that I cannot get it to connect to the Nas4Free box. It uses SMB/CIFS to chatter on the wired network. The log on the Nas4Free box suggests that all is well, but RaspyFi comes up with a cryptically unhelpful error message - I have had a browse around looking for further information about the error message (cifs_mount failed w/return code = -6) and have not found anything useful.
I don't know if this is related..... I can mount a share from windows 7 by using the share name ('Nas4Free'), but I can't using the IP address of the Nas4Free box (It pings and ftp's correctly, so I do have the correct ip address). Raspyfi only can connect by ip address.
Any help or suggestions would be appreciated.
Thanks
Peter
This is the old XigmaNAS forum in read only mode,
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
it will taken offline by the end of march 2021!
I like to aks Users and Admins to rewrite/take over important post from here into the new fresh main forum!
Its not possible for us to export from here and import it to the main forum!
[Solved] Has anyone got RaspyFi working with Nas4Free?
-
pmiller056
- NewUser
- Posts: 6
- Joined: 26 Apr 2013 23:11
- Status: Offline
[Solved] Has anyone got RaspyFi working with Nas4Free?
Last edited by pmiller056 on 17 Nov 2013 21:13, edited 1 time in total.
-
pmiller056
- NewUser
- Posts: 6
- Joined: 26 Apr 2013 23:11
- Status: Offline
Re: Has anyone got RaspyFi working with Nas4Free?
Hi
I finally managed to fix this for myself. I wasn't as clear as I should have been describing what happened under Windows - Windows could see and use correctly the files when browsing local network-connected devices. Windows would fail when trying to mount and assign a drive letter to the shared files. Using a Windows XP computer, which provides more information useful for fault finding in place of a Windows 7 computer (which tidily hides everything useful for fault finding) was helpful.
It turns out that I was confusing 'Path to share' with 'sharename'. I'll elaborate....
My Nas4free box is assigned IP address 192.168.0.nn. It has one mounted filesystem at /mnt/3tbdisks. I wish to share on the network the directory /public from the root of the 3tb filesystem. CIFS/SMB is set up to share /mnt/3tbdisks/public as Nfsfiles. When configuring the Raspyfi player I was asked to configure the path to the network files, so I set it up for //192.168.0.nn/mnt/3tbdisks/public which failed. When I changed the path to the network files to //192.168.0.nn/Nfsfiles it all started to work correctly.
In retrospect, a simple mistake. I hope someone else learns something useful from this.
Regards
Peter
I finally managed to fix this for myself. I wasn't as clear as I should have been describing what happened under Windows - Windows could see and use correctly the files when browsing local network-connected devices. Windows would fail when trying to mount and assign a drive letter to the shared files. Using a Windows XP computer, which provides more information useful for fault finding in place of a Windows 7 computer (which tidily hides everything useful for fault finding) was helpful.
It turns out that I was confusing 'Path to share' with 'sharename'. I'll elaborate....
My Nas4free box is assigned IP address 192.168.0.nn. It has one mounted filesystem at /mnt/3tbdisks. I wish to share on the network the directory /public from the root of the 3tb filesystem. CIFS/SMB is set up to share /mnt/3tbdisks/public as Nfsfiles. When configuring the Raspyfi player I was asked to configure the path to the network files, so I set it up for //192.168.0.nn/mnt/3tbdisks/public which failed. When I changed the path to the network files to //192.168.0.nn/Nfsfiles it all started to work correctly.
In retrospect, a simple mistake. I hope someone else learns something useful from this.
Regards
Peter