Mount samba shares with utf8 encoding using cifs

[dmizer]

Sorry folks, I've been tied up at work. I'll try to reply to everyone here. If I've missed someone please let me know.

Thank you.

reets@ubuntu:~$ smbtree user=reets
Password:
reets@ubuntu:~$

Try this command instead:

smbclient -L DLINK-80CEDB

Output of smbtree

john@john-desktop:~$ smbtree
Password:
MSHOME
\\OFFICE OFFICE

Text from /etc/samba/smb.conf – not the entire file, just the part that seemed relevant.

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = MSHOME

Two things I need to see here.

1) Please post the output of:

smbclient -L OFFICE

2) Your smb.conf does not give your Ubuntu computer a netbios name. Please add an option after "workgroup = MSHOME" (highlighted above in red) which can be used to identify your computer on the network like so:

netbios name = Ubuntu_computer_name

replace "Ubuntu_computer_name" with whatever you'd like your ubuntu computer to be known as on your network (usually whatever comes after the @ symbol in your cli prompt.

Then, restart your samba server with the following command:

sudo /etc/init.d/samba restart

Dmizer, this has been a great HOWTO. I have a NAS device (an HDD enclosure) connected to my router (Netgear Rangemax Wireless Router). I followed your howto but got stumped on the netbios part. Although this computer is a dual boot with XP, the NAS doesn't have anything to do with the two OSes I have. I am able to access the NAS from XP and was able to access the NAS from Hardy without any trouble. As soon as I upgraded to Intrepid I lost my connection to the NAS.

My best suggestion to you is to mount this device with FTP instead of SMB. I only looked briefly at the specs for your device, but my success rate with NAS devices in this thread has been limited. If you have problems with FTP as well, let me know and I'll try to dig deeper.

@dmizer:
Finally I could solve my problem with Imomega StoreCenter Pro.
I switched to ntp (cifs still has problems with 8.10).
The problem with ntp is that you have to specify on NAS settings a valid range of IP (or even * for all) that have access to it otherwise it will not mout.
Thanks.

I am so glad you got that working! As I mentioned above, NAS devices just don't seem to cooperate well with CIFS.

Same as above, the fact that I can mount the department folders but not my own lead me to believe AD does not have anything to do with it.

In other words, I'm still clueless

The whole network doesn't have to be AD. The department folders may be on a simple samba server for easy access, and your personal folder restricted by AD for security reasons. Also, an AD server can handle permissions differently according to the needs of the shares. In other words, open shares can be given access outside of AD logins while your personal shares remain protected.

That said, my understanding of AD is limited, and I have very little experience with it. However, even if AD is NOT the problem, it's still a good idea to investigate it as a potential problem.

[mojohn]

dmizer, the output of smbclient -L OFFICE is:

Domain=[OFFICE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Sharename Type Comment
--------- ---- -------
My Docs Disk
IPC$ IPC Remote IPC
print$ Disk Printer Drivers
SharedDocs Disk
LaserJet3020 Printer hp LaserJet 3020 PCL 6
Printer4 Printer Canon PIXMA iP6000D
Printer2 Printer Print2Mail
backup (L) Disk
Printer Printer Print2PDF
Domain=[OFFICE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

Server Comment
--------- -------

Workgroup Master
--------- -------

After editing smb.conf to add netbios name = john-laptop, I restarted samba and got the following message in my terminal window:

john@john-laptop:~$ sudo mount -t cifs //office/backup /mnt/windowsmount error: could not find target server. TCP name office/backup not found
No ip address specified and hostname not found

So, I changed the netbios name to the IP address:

john@john-laptop:~$ sudo mount -t cifs //192.168.1.100/backup /mnt/windows
Password:
retrying with upper case share name
mount error 6 = No such device or address
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)
Any other thoughts?

Thanks, mojohn

[dmizer]

mojohn, do you have a samba server configured on your Ubuntu machine? If so, please post the contents of /etc/samba/smb.conf

Also, double check to make sure that cifs is actually installed:

sudo aptitude install smbfs

edit: actually on second thought, the (L) tag on the backup share name could be significant. I'm not sure what it means, but it could be some kind of special lock or security enabled on the backups share. Are you able to mount the "My Docs" share with something like this:

//office/My\040Docs /media/docs cifs guest,rw,file_mode=0777,dir_mode=0777 0 0

Of course, you will also have to make a /media/docs directory.

[artio]

..even if AD is NOT the problem, it's still a good idea to investigate it as a potential problem.

Thanks, dmizer, I'll take this up with the network administrators

[mojohn]

dmizer, cifs is installed. The complete text of my smb.conf file is:

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = MSHOME

# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no

# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = user

# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam

obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# load printers = yes

# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap

# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700

[printers]
comment = All Printers
browseable = no
path = /var/spool/samba
printable = yes
guest ok = no
read only = yes
create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
; write list = root, @ntadmin

# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes

# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom

[halful01]

Hi,

I am having a problem mounting a windows share using kerberos authentication.
I run the command:

sudo mount.cifs //smb.pass.psu.edu/emw5051 /media/pass --verbose -o user=dce.psu.edu/emw5051,password=***,sec=krb5

where *** is my actual password.
Then I get the output:

mount.cifs kernel mount options unc=//smb.pass.psu.edu\emw5051,ip=128.118.2.227,domain=dce.psu.edu,ver=1,user=emw5051,,,,,,,,,,,,,password=***,sec=krb5 
mount error 2 = No such file or directory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

With any other security option I get a permission denied error.
I have checked krb5.conf to make sure I have the correct settings.
I am running ubuntu 8.04.
I can't figure it out, help is appreciated.

[dmizer]

dmizer, cifs is installed. The complete text of my smb.conf file is:

Okay that doesn't tell me anything. Are you able to mount any other shares on that server? This could be a permissions problem with that particular share on the Windows computer itself.

Hi,

I am having a problem mounting a windows share using kerberos authentication.
I run the command:

sudo mount.cifs //smb.pass.psu.edu/emw5051 /media/pass --verbose -o user=dce.psu.edu/emw5051,password=***,sec=krb5

where *** is my actual password.
Then I get the output:

mount.cifs kernel mount options unc=//smb.pass.psu.edu\emw5051,ip=128.118.2.227,domain=dce.psu.edu,ver=1,user=emw5051,,,,,,,,,,,,,password=***,sec=krb5 
mount error 2 = No such file or directory
Refer to the mount.cifs(8) manual page (e.g.man mount.cifs)

With any other security option I get a permission denied error.
I have checked krb5.conf to make sure I have the correct settings.
I am running ubuntu 8.04.
I can't figure it out, help is appreciated.

The mount line does not look right at all, but I am really weak with AD, and this howto doesn't cover AD. But ... "smb.pass.psu.edu" seems like a strange netbios name. the "user" option should only be this: emw5051 you'll also need to add "dce.psu.edu" as a domain option. So once you know the correct netbios name of the server, your mount command should probably look something like this:

sudo mount.cifs //netbiosname/emw5051 /media/pass --verbose -o user=emw5051,password=***,domain=dce.psu.edu,sec=krb5

Also, I may not be correct here, but I believe this may not be possible unless you've successfully logged into the AD with your GDM login.

[LordKelvan]

Hi:

I tried this HOWTO, but I cannot get it working. My set-up is that I'm at school, and I would like to access my music folder on my home machine. I've already set-up the port-forwarding rules on my router for the appropriate ports (TCP 445 and TCP 139), and I've configured Windows Firewall to open these ports. My school computer is not running a firewall. The problem is that always times out when I try to connect to my shared folders. This happens regardless of whether I use "Connect to Server", typing "smb://...." into the location bar of Nautilus, or use CLI commands "mount -t cifs ....".

Do you have any suggestions as to what is wrong, or how I might diagnose the problem?

Cheers,
LK

[dmizer]

Hi:

I tried this HOWTO, but I cannot get it working. My set-up is that I'm at school, and I would like to access my music folder on my home machine. I've already set-up the port-forwarding rules on my router for the appropriate ports (TCP 445 and TCP 139), and I've configured Windows Firewall to open these ports. My school computer is not running a firewall. The problem is that always times out when I try to connect to my shared folders. This happens regardless of whether I use "Connect to Server", typing "smb://...." into the location bar of Nautilus, or use CLI commands "mount -t cifs ....".

Do you have any suggestions as to what is wrong, or how I might diagnose the problem?

Cheers,
LK

SAMBA is extremely unsafe to share over the internet. If your windows machine is not already compromized, it will be very soon. Please get that turned off quick.

Please investigate an alternate means of accessing your home network. You should be using an encrypted protocol like VPN or SSH.

[LordKelvan]

Hmm, you don't say.... well thanks for the tip. Is that why I always see people using SAMBA for home networks where both client and server are on the same network?

I'll disable the port-forwarding rules when I get home, and turn off sharing for now. Would you happen to have any free and simple solutions to my problem (like free VPN or something).

Cheers,
LK