Mount samba shares with utf8 encoding using cifs

[dmizer]

Thanks! Sorry but I didn't want to stress.

I'm using the NetworkSpace 2 from LaCie: Here is a description. There exists a windows program to change password and settings, but I don't have an Windows OS anymore. In the link above is an instruction to hack the NAS, but I'm a little afraid that I gone loose my data's if I do it.

Actually, I suggest that you post this question to the LaCie community forums here: http://www.nas-central.org/community-portal I think they will be better equipped to handle your problem.

[john_spiral]

FYI:

Hi,

I've noticed that you need to give the full path on a credential file under Ubuntu 10.10 (updated). I previously had the below line in a script, previously on 8.04:

sudo mount -t cifs //192.168.1.74/c$ ~/windowsmachine/ -o credentials=.pass,iocharset=utf8,noexec,ro

Under 10.10 this now needs to be changed to:

sudo mount -t cifs //192.168.1.74/c$ ~/windowsmachine/ -o credentials=~/.pass,iocharset=utf8,noexec,ro

as my .pass file is in my /home/username/ directory.

If you don't it will give an evil message like:

error -1 (Unknown error 4294967295) opening credential file .pass

hope this helps someone.

[dmizer]

sudo mount -t cifs //192.168.1.74/c$ ~/windowsmachine/ -o credentials=.pass,iocharset=utf8,noexec,ro

Frankly, I'm surprised this worked for you at all. You should always use the full path to the credentials file, and ~/.pass is not a full path.

Since mount works with the root account (sudo) and not the user account, my howto instructs you to put the credentials file in a root home instead of the user home.

So for example, if you switched to a root prompt with sudo -i and then ran your new command it would also not find your credentials file because from a root prompt ~/.pass is /root/.pass

I highly recommend that you either place the credentials file in the root home (as explained in this tutorial) so it's more secure, or that you revise your mount command to include the real full path of /home/user/.pass instead of using a tilde.

[john_spiral]

...I highly recommend that you either place the credentials file in the root home (as explained in this tutorial) so it's more secure..

Thanks for the heads up on more robust security.

On a slightly different subject. Is it still necessary (Ubuntu 10.10) to specify the IP address of the primary WINS server in the /etc/samba/smb.conf file for an Ubuntu WINS client in a subnetted network?

Also with the below name resolve order in smb.conf:

name resolve order = wins bcast host lmhosts

I previously did this under 8.04 to resolve Windows host names on different subnets, by their short names. Without the above config it didn't work.

[dmizer]

Thanks for the heads up on more robust security.

On a slightly different subject. Is it still necessary (Ubuntu 10.10) to specify the IP address of the primary WINS server in the /etc/samba/smb.conf file for an Ubuntu WINS client in a subnetted network?

Also with the below name resolve order in smb.conf:

name resolve order = wins bcast host lmhosts

I previously did this under 8.04 to resolve Windows host names on different subnets, by their short names. Without the above config it didn't work.

No problem.

As to WINS, if you don't have a good local DNS server for name resolution, you'll have to rely on WINS for your name resolution. If that's the case, then you may have to place the IP address of the WINS server in the client's smb.conf. It's not always necessary, but it's certainly good practice.

[iliekpie]

Great guide but I'm having a bit of an issue with getting the mount to be permanent.

Using: Windows 7 64bit, Ubuntu 10.10 64-bit, NAS is a Dns-323

After following the guide I don't get any error messages ever but nothing appears in /media/share

If I use the code posted by narky in one of the first few posts:

sudo mount -t smbfs -o username=*****,password=***** //192.168.0.2/music /mnt/music
Except with my ip //192.168.1.104/Vol1 /media/share

It works when I try it that way but it goes away after a reboot.

If I try with cifs manually it doesn't seem to work.

The only thing I thought to try was changing cifs to smbfs in /etc/fstab but I have no idea if that even makes sense to try. It doesn't seem to work though.

How can I get it to be permanent?

[tipiglen]

Dmizer,
Thanks for all your effort on this.

I have a share which mounts perfectly well on bootup, but have the shutdown delay problem with "CIFS VFS: no response" errors and a full minute of waiting followed by a forced disk check on reboot.

I have tried a lot of the "fixes", scripts, moving umountnfs to K10, etc, but with no joy.

Please help. Running Mint 9 (ubuntu based).

Thanks in advance
http://tipiglen.co.uk/loveandpeace3.gif
ed

[tipiglen]

Dmizer,

And empathetic thoughts for all folk in Japan and those who know and care for them.

http://tipiglen.co.uk/loveandpeace3.gif

[tipiglen]

This fix works for me!
http://ubuntuforums.org/showthread.php?t=1347340&page=3

What a community of interest!

xxxxxxx
ed

[dmizer]

Great guide but I'm having a bit of an issue with getting the mount to be permanent.

Using: Windows 7 64bit, Ubuntu 10.10 64-bit, NAS is a Dns-323

After following the guide I don't get any error messages ever but nothing appears in /media/share

If I use the code posted by narky in one of the first few posts:

sudo mount -t smbfs -o username=*****,password=***** //192.168.0.2/music /mnt/music
Except with my ip //192.168.1.104/Vol1 /media/share

It works when I try it that way but it goes away after a reboot.

If I try with cifs manually it doesn't seem to work.

The only thing I thought to try was changing cifs to smbfs in /etc/fstab but I have no idea if that even makes sense to try. It doesn't seem to work though.

How can I get it to be permanent?

SMBFS is not included in Ubuntu unless you compile it from source. There is literally no reason why smbfs should work where cifs wouldn't unless there has been a change in syntax.

Please post your actual /etc/fstab line.

This fix works for me!
http://ubuntuforums.org/showthread.php?t=1347340&page=3

What a community of interest!

xxxxxxx
ed

Thanks for finding that. I've included that link in the troubleshooting section.