Samba UTF8
Hi!
In rc.conf
# LOCALIZATION
LOCALE="en_US.UTF-8"
DAEMON_LOCALE="yes"
HARDWARECLOCK=""
TIMEZONE=""
KEYMAP="de_CH-latin1"
CONSOLEFONT="Lat2-Terminus16"
CONSOLEMAP=
USECOLOR="yes"
in smb.conf
server string = Media Server %h (%v)
unix charset = UTF-8
display charset = UTF-8
A folder named "Bløf" copied from Win7 to the samba share. The folder appears as "Bløf" on the file system and I couldn't care less but that whenever I try to have f.I. sox to interpret the folder I get "Invalid or incomplete multibyte or wide character"
What would be the proper settings in smb.conf and rc.conf to properly deal with UTF-8 characters?
Try set DAEMON_LOCALE="no", I think that was what fixed by character
encoding in Linux VT when I reinstalled by computer recently.
Similar Messages
-
It is not the best place for this post but since we have to start from the kernel....
I tried to send and e-mail about this to the mailing list and I receved no answer so lets try by the forum.
Basically I started to think about that since samba 3.0 (that use UTF8 as
default) came out.
By looking at Archlinux:
Kernel NLS option is compiled with iso8859-1 (western european)
Kernel Remote filesystem NLS use cp437 (united state)
There is no iso10496/utf8 fonts in the system.
An interesting step for arch should be moving to utf8.
Opinion??Basically is this.
Normally you can't visualize all the possible chars in the world.
In fact you chose the "type of char" you want to see/support on your system.
For instance if you use iso8859-1 charset you can visualize accetend letters like òàùèìéç etc. basically the ones you find in western european language (like Italian French German Spanish Portugues....) but if you try to visualize something in Russian Bulgarian Rumenian etc. there are different kind of letters/accent and instead of the correct char you probably see question mark under windows or strange char with linux. Imagine if you try to read a japanese document.
This limitation of "chars quantity" was due to the necessity to use only 8 bit for the coding in order to save space in memory and hd.
Now modern computers have huge ammount of memory and so UTF8 came out.
Basically this standard provide the coding for any chars in the planet. By setting this on your computer and programs you are able to read any kin of document with any coding. Offcourse not everybody need it but anyway all the system (operating systems and programs) are moving to this standard. -
Error -6602 while connecting to samba shares.
Hi everyone, i have some problems with samba client on MacOSX 10.5.8, the problem is that it connects to some shares and some not, and I don't know why, please help.
Here is my samba configurations on Ubuntu server, the problem starts after logging as a user kuba with password, it shows Erro -6602. Login and pass are correct, I use them with a parallel desktops windows xp, and it works. Mac is working with other server which stands on PLD Linux. I don't know if it will be usefull but if i can tell you that password doesn't contain any special chars, the only one is undescore char. The same password and user with some additional letters works on PLD.
I can connect to samba shares on this server with smbtree command, if I use
smbclient //server/share -U user with a password authentication it shows a wrong password (but it's correct).
When I delete the valid user definition I can connect to samba, but only with a readonly mode...
[global]
netbios name = ubunteon
server string = ubunteon
workgroup = *********
announce as = NT Server
announce version = 4.9
security = share
encrypt passwords = yes
update encrypted = no
unix password sync = no
smb passwd file = /etc/samba/smbpasswd
logon script = startup.bat
logon drive =
add user script = sudo /usr/sbin/useradd -g smbusers %u
delete user script = sudo /usr/sbin/userdel -r %u
add group script = sudo /usr/sbin/groupadd %g
delete group script = sudo /usr/sbin/groupdel %g
add user to group script = sudo /usr/sbin/usermod -G %g %u
add machine script = sudo /usr/sbin/useradd -g smbmachines -c 'Konto komputera %I' -s /bin/false -d /var/lib/samba/nobody %u
passwd chat debug = no
passwd chat = New*UNIX*password %n\n ReType*new*UNIX*password %n\n passwd:*all*authentication*tokens*updatedsuccess fully*
passwd program = /usr/bin/smbpasswd -L -a %u
nt acl support = no
nt pipe support = yes
map to guest = Bad User
log file = /var/log/samba/log.%m
max log size = 50
log level = 1
os level = 255
domain logons = no
preferred master = yes
domain master = yes
local master = yes
time server = yes
browse list = yes
enhanced browsing = yes
idmap uid = 16777216-33554431
idmap gid = 16777216-33554431
winbind enum groups = yes
winbind enum users = yes
winbind use default domain = no
winbind separator = +
unix charset = UTF8
display charset = UTF8
dos charset = CP852
wins support = yes
read raw = yes
write raw = yes
oplocks = no
level2 oplocks = no
max xmit = 65535
getwd cache = yes
dos filetimes = yes
dos filemode = yes
dos filetime resolution = yes
deadtime = 15
default case = lower
preserve case = yes
short preserve case = yes
case sensitive = no
socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=16384 SO_RCVBUF=16384
dns proxy = no
name resolve order = hosts lmhosts wins bcast
guest account = guest
admin users = smbroot
invalid users = root
load printers = yes
printing = cups
printcap name = cups
[www]
comment = Webpages
path = /home/user/public_html
public = no
read only = no
browseable = no
create mask = 0755
directory mask = 0755
valid users = user
browseable = yes
writeable = yes
#printable = yes
[devel]
comment = Development Zone
path = /home/user/0-Developement
public = no
read only = no
browseable = no
create mask = 0755
directory mask = 0755
valid users = user
browseable = yes
writeable = yes
#printable = yes
[pdfprints]
comment = Development Zone
path = /home/user/PDF
public = no
read only = no
browseable = no
create mask = 0755
directory mask = 0755
valid users = user
browseable = yes
writeable = yes
#printable = yes
[home]
comment = Home
path = /home/user
public = no
read only = no
browseable = yes
writeable = yes
valid users = user
[oferty]
comment = Oferty
path = /home/user/public_html/2-Oferty
public = no
read only = no
browseable = yes
writeable = yes
valid users = user
#udostepnienia widziane przez wszystkich
#drukarki
[printers]
comment = Drukarki sieciowe
browseable = no
path = /var/spool/samba
printable = yes
writable = no
create mode = 0700
#drivery do drukarek sieciowych
[print$]
path = /srv/samba/printers
guest ok = yes
browseable = no
read only = yes
write list = smbroot
#katalog domowy
--------------------------------------------------------------Hi Ramya,
Following checks may help to resolve the issue.
1) Whether Port 21 is open and allowed to connect with FTP.
2) Ping, FTP and telnet possible from PI box to FTP.
3) User mentioned in Communication channel have authorization for read and write on FTP server.
4) FTP ports are open.
5) Firewall setting done properly. -
Quandary about Samba media repository
Hi folks,
I have recently tried to make my den greener by turning devices off when not in use. I run an environment with Mac, Linux, and Windows. I managed to offload all my server functions either to my web host or to network devices I can turn off when not in use except for my media storage, which needs to be available from all three platforms.
Currently I have the media storage on my Ubuntu Linux desktop system, shared using Samba. However, there are a number of albums that don't show up in iTunes because of accented characters. For instance, take Motorhead with the umlaut on the second "o". I could butcher the stored names to fit, but I'd rather not. When I look at these directories natively on my Linux box, they're there and I can play the music with no problem. However, when I go into Finder on the Mac, I see the "Motorhead" directory, but when I click on it, it disappears - weird. I have no difficulty seeing or playing any of these files from Windows or my Linux laptop, so this appears to be some kind of client-side problem. I have no problem with any of the other files or directories on this share from any platform.
The plot thickens. For Christmas, I got a new 160Gb iPod to replace my 30 Gb iPod that was just about full. As it happens, the 40 Gb drive I'm using for storage is just about full, too. So I'm almost immediately in the market for about 160 Gb of RAID 1 storage . I can see three choices:
Ideally, it would be useful if I could have it be storage I can attach to any of my systems rather than having to fire up a server as well as the system I am using, so I'm thinking maybe USB2 or Firewire storage I can shlep around. Of course, it would need to have a file system that was readable from all three platforms, which poses a bit of a problem, I think. Also, using a removable drive with a laptop would presumably entail plugging it in when I want to use it, which might be awkward.
Alternatively, I could use a network storage device that I could just flick on when I want to access music or movies. However, whatever I use would need to be readily accessible from all three platforms, which poses challenges. The things I'm seeing at Best Buy are geared toward Windows, using some kind of proprietary transparent local caching arrangement. Obviously, anything using SMB networking will still face the same challenges I've got today but at least it will just be there, where right now it is a bit of a fussy manual process logging in and getting the drive mounted on Ubuntu.
Another option is to continue with the current approach and just RAID a pair of big SATA drives on my Linux box, which supports it. However, I would first need to make sure I could access all of the music, regardless of the characters used in file or directory names, even from the Mac. So I've got to figure out the filename problem before I can move and, since I've got less than 1 Gb left on the current drive, it is getting pretty urgent.
Does anybody have any suggestions on resolving the current problem with names or on what technology to focus on for either of the other approaches?
RalphMAdding more information after further research...
It occurred to me that I hadn't gone quite as far as I might on my Linux laptop. I hadn't actually tried to mount the share as a filesystem. So I dug into that and found a couple of things that might be relevant.
There are apparently two implementation of an SMB client mount - one, smbfs, hasn't been maintained for a while, while the newer one, cifs, is VFS-based. Playing around with it, I got very similar results to what I was seeing on the Mac mounting with -t smbfs. However, I was able to play music from the Motorhead folder cleanly using cifs, provided I supplied the iocharset=utf8 option on the -t cifs mount. (I did not try to see if the smbfs client supported that option, though.)
I don't know what the Mac is using under the covers for mounting SMB clients, smbfs or cifs. I am a little worried that because it is VFS-based, cifs may not be entirely portable to Darwin/FreeBSD, so I could be out of luck. On the other hand, if they are using CIFS, it could just be a matter of forcing the right option on the mount. Does anybody know? Does anybody know how Leopard is handling mounts under the covers, so I could look at the configuration files to figure it out?
I'm really a little frustrated with the networking on this system. I've got NFS shares for the way I had things configured before that I can't figure out how to shut off. The tools I used for digging under the covers before seem to be gone and the arrangement of the file system has changed - I no longer find the familar Unix folder names for half the stuff. When I try to specify WINS settings through the Network item on System Preferences, it won't persist the workgroup I give it but it doesn't give me any other place to specify it either, so it comes up in WORKGROUP where everything else in the lab comes up under MACKSOFT. None of this is particularly relevant to the problem at hand, but networking seems to be the place I'm spending the most "fiddle time" on an otherwise well-behaved and self-contained system.
Ralph -
New to Solaris, Some Samba and NTFS issues.
Hi Im new to solaris and trying out ZFS which has been great.
Im haivng some trouble that I cant find up to date info on so here goes:
First how do you mount an NTFS volume in Solaris 11 Express?
I need to access the data on an NTFS drive to populate my new ZFS tank.
Secondly, I have read only access on my samba shares from windows machines but my smb.conf looks right. a copy of my smb.conf will follow
Any suggestions would be appreciated.
# 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 (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = Samba Server
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = share
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/samba/log/log.%m
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
passdb backend = smbpasswd
# 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.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/sfw/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# 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
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = no
writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/sfw/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
# Set public = yes to allow user 'guest account' to print
guest ok = no
writable = no
printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = no
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
[Series]
comment = TV Series
path = /home/Kirby/Series
public = yes
only guest = yes
writable = yes
printable = no875739 wrote:
Hi Im new to solaris and trying out ZFS which has been great.
Im haivng some trouble that I cant find up to date info on so here goes:
First how do you mount an NTFS volume in Solaris 11 Express?
I need to access the data on an NTFS drive to populate my new ZFS tank.I never had a need for it but I think you'll have to compile fuse ntfs-3g manually.
http://web.archiveorange.com/archive/v/u46DbWSGcIzl7pexf4hQ
>
Secondly, I have read only access on my samba shares from windows machines but my smb.conf looks right. a copy of my smb.conf will follow
Any suggestions would be appreciated.You don't need to use Samba in Solaris 11 Express.
http://download.oracle.com/docs/cd/E19963-01/html/821-1448/gaynd.html#gayne -
[SOLVED] Share Multiple Directories With Samba On Arch Linux and XP
Hello,
I have had the worst luck so far with Samba, which is far more likely because of an error on my part than on Samba's.
I can only seem to share one directory regardless of how I setup my smb.conf. And worse yet, if I mess with Samba, smb.conf, after the first time I set it up it doesn't work again until I reinstall my OS. Now I'm sure that reinstalling isn't the only option, but I haven't figured out how to make it work again any other way. I've tried uninstalling it, deleting it from the cache, deleting /etc/samba and so on, still can't connect to it from XP when I reinstall it.
I'm running Arch64 and I want to share some directories with a laptop running Windows XP.
I want to share my home folder, but have it accessible from XP only by me, share my mother's home folder, and have it accessible on XP only by her (well actually I guess it needs to be accessible by both, since i'm the admin), share my media-server (a collection of five hard drives where I store movies and such), and have it read/write by both of us. And finally share /srv so I can work on that from the XP computer as well. I think that's all. And I would like to share printers between the two computers. I would also like to access XP files from here.
I've always been able to get the media-server to share, but that's it, nothing else. And it doesn't always work right. It doesn't seem to want to follow sym links, but like I say if I mess with it it will stop working all together. So I'm not sure what to do.
A thought was to instead make a /media/samba-share directory and share that, and inside it have symlinks to my home, media-server, etc. However, that will only work if samba will follow symlinks for me.
Here is the smb.conf I am planning to use at the moment:
# 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 (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = MEDIA-SERVER
netbios name = Avalon
encrypt passwords = true
# server string is the equivalent of the NT Description field
server string = Samba Server
# Symlinks
follow symlinks = yes
wide symlinks = yes
unix extensions = no
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = user
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam
# 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.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# 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
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
include = /etc/samba/usershare.conf
#============================ Share Definitions ==============================
[homes]
comment = Home Directories
browseable = yes
writable = yes
[media-server]
comment = Media Server
path = /media/media-server
browseable = yes
writable = yes
printable = yes
valid users = theavataroftime, christina
follow symlinks = yes
[theavataroftime]
comment = The Avatar of Time's Home Directory
path = /home/theavataroftime
browseable = yes
writable = yes
printable = yes
valid users = theavataroftime
follow symlinks = yes
[christina]
comment = Christina's Home Directory
path = /home/christina
browseable = yes
writable = yes
printable = yes
valid users = christina
follow symlinks = yes
[server]
comment = Server
path = /srv
browseable = yes
writable = yes
printable = yes
valid users = theavataroftime, christina
follow symlinks = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
Set public = yes to allow user 'guest account' to print
guest ok = yes
writable = no
printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
;[public]
; path = /usr/somewhere/else/public
; public = yes
; only guest = yes
; writable = yes
; printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
Now I wouldn't think I would need to list my home and mom's home seperately, but since [homes] has never worked for me in the past i thought i would give it a try. Does this look like something that would do what I am wanting?
Otherwise I would delete [homes], [media-server], [theavataroftime], [christina], and [server] and replace them with just [samba-share] with all those as symlinks inside that directory as before mentioned.
Anyway, thanks for the help. Any good guide on this matter would be appreciated, I have looked at several, but more can't hurt . Networking isn't my thing so to speak, so please be specific in any explanations. Thanks again.
Last edited by The Avatar of Time (2009-03-02 03:38:12)Well it seems that my trouble all started when I began using the 'printable = yes' option for shares. Since I removed that the troubles seem to have left me.
Does anyone know why that is listed as on option in smb.conf here:
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff
As well as in a few other examples if it doesn't work? I seen the example and assumed that option was needed to print from those shared directories.
Also, it seems that the comma is not needed between the 'valid users' names.
Also, I guess it wasn't Windows XP's fault either but rather my own ignorance. I like the idea of blaming Windows better though.....
I hope this servers to help others to aviod my mistakes. -
Finder lock ups due to samba shares being invalidated by changing network
I often leave my macbook online for a long time unattended, for simplicity I tend to plug it into its power lead, and also connect it up to my gigabit network. I know i've set the priority in my connections to prefer the wired connection over wireless but just to keep things simple i disable airport so i can be sure that i will be connected via gigabit.
I'll then go in and map a network drive from one of my PCs on the lan, this is mounted and available.
Sometime in the future i'll go mobile again, like i just did today. Disconnecting power and gigabit ethernet, i re-enable airport. After a short while its all good to go.. I then start using the internet connection. All is fine.
Then finally i spot that my samba drive is still mapped, i've had trouble selecting this drive to use it, but sadly also you get real trouble by just trying to eject the mount. Doing so and nothing happens.. after 10-20 seconds everything is frozen, including the animated dock, and top toolbar, and you are presented with the spinning wheel of activity.
applealtesc does NOT bring up the force close dialog, and eventually i was forced to force a shutdown.. apple power button isn't it? I had the power button held down for a long time.
Generally i find the mounting samba drives a bit of a pain in the finder but i can put up with it. Samba shares on windows are a nightmare but they rarely bring down the whole system when a connection has been broken.. i'd love it if mac OS would time out the samba share and just give up, rather than hanging in the way it does do.
Obviously i'm accessing my LAN through a different interface and IP address than i was when i set up the connection. I am not sure if you have a similar problem as described if you just disconnect from the network and have no net connection at all.. not sure what it would do with a share in this way.
Is this worth logging as an actual bug? anyone got any suggestions to fix it?Ok, no luck yet. Maybe I can ask another question directly related to this issue. I am trying to find the cause of this and I am wondering if there is a brief dropout in the connection to the NAS. By brief, I mean really brief. The NAS is connected via a Homeplug network connection (network via the homes power points) and maybe for a very brief period interferrence on the lines dropped the AFP connection.
Is it normal that it is then impossible for AFP to reconnect, even when the NAS is clearly back on the network?
Any drop will have to be very brief as I can always stream music without issues, and no drop or slow down has caused buffering issues.
But, I don't recall getting this issue when directly connected to the iMac via a short ethernet cable for the initial Time Machine backups that take over a day.
What I don't understand though, is if the connection did briefly drop and loose the AFP link, why can AFP no longer connect back? Why do I need to sleep the iMac and then wake it again.
HTTP connections to the NAS never seem to drop, and when I can't recconnect via AFP, I can always connect via HTTP? Is this expected of the AFP protocol? Or is it an unexpected issue? -
Yosemite 10.10.1: Finder/CIFS mount problem: wrong folder count/folders not shown @samba shares
Hello to all,
we have several MacBook Pro (15" MBP Retina 2012/13"MBP Retina 2014) running. After upgrading to Yosemite 10.10.1 we had one nightmare after the other.
Most problems could be solved with 3rd party software upgrades but there are several problems with the operating system itselve which can not really be called a professional productive system at the moment...
Ok., one thing after the other...here is one of our biggest problems:
After upgrading from Mavericks or Mountain Lion to Yosemite 10.10.1 the CIFS/SMB mounts to our samba 3.x servers, running on Ubuntu Linux LTS 12.04 makes trouble. We could mount the server shares but after browsing with the Finder the beach ball occures and the Finder hangs forever. Sometimes we could not refresh the Finder, killing the process ended in a complete hang-up of the system which ended in a switch off death blow. This is not amusing because we have 30Tb of customer data there, which has to be worked out.
We heard about the SMB3 protocol which will be used per default in Yosemite and so we decided after some testings to upgrate our Ubuntu servers to the latest LSF 14.04. release with samba 4.1.6 installed. There was no message from Apple for this SMB protocol release upgrade, never heard something related to Yosemite (Why?).
Ok, after these server upgrades and disabling most of the Spotlight functions the performance to the CIFS shares was a little bit better as before but now we have another problem with the Finder...if you browse to the shares there are folders missing which have lots of files in it. For example there is a folder with 60 subfolders and 3562 files on the first level in it, the Finder shows 220 files and 15 folders. The Terminal shows a different count with "find . -maxdepth 1 -type d | wc -l" or "find . -maxdepth 1 -type f | wc -l" but there is also a difference to the original file and folder count. It doesn`t matter if the clients are connected via WiFi or Gigabit Ethernet. We have no access problems. We have the same behavior if we set the files and folders to 0777 permissions on the servers. The deletion of the preferences files of the users on the MacBooks does not solve the problem. If we use the "Go To Folder" option and type the path to a folder which is not shown in the Finder you get an result or not. But it is also possible that the result is not correct and there are also still files or subfolders missing.
In my opinion this is a timeout problem and a "special SMB3 protocol interpretation" which is buggy. We have one hint found in /var/log/system.log:
"Jan 23 14:35:49 wsosx33.clients.getcom.de KernelEventAgent[69]: tid 54485244 type 'smbfs', mounted on '/Volumes/customersdata2015', from '//x144067:@srvlxp013.servers.getcom.de/customersdata2015', not responding"
We had no problems with Mavericks at all, we still have no problems with Windows 7 Pro/Ultimate, Windows 2008R2 (native or virtual) or Linux Mint 17/17.1 clients, neither with samba 3.x nor with our actual environment and different newer samba releases.
We believe that this is a big bug in Yosemite, but we cannot go back to Mavericks because of incompatible TimeCapsule backups. Our workarround at the moment is that we have installed Linux Mint on our MacBooks to get 80% of our daily jobs done, rest has to be done with Windows 7 installed over virtualbox @Linux.
We have no clue at the moment how to solve this problem, the samba logs do not give any hint. The access from other operating systems is perfect and very fast, but not with Yosemite. We checked different tips found in the internet but nothing helped.
Does anybody has another idea to get Yosemite working or should we keep Linux Mint until Apple will provide a CIFS/SMB patch and going on with our workaround solution, which is productive at the moment ??? Our staff is not amused and wants one solution and not this workaround with two operating system. We have to decide wether we wait until Apple will get this fixed or we have to switch to Microsoft Windows (which is a No Go for me, but I will not be asked...).
Thanks in advance
C.Hi William,
thank you for your response.
As you can read in my post I talked about CIFS/SMB.
It makes no difference if we mount the share over CIFS or SMB.
Folders with lots of files will not be shown even if we use SMB3 or an older protocol.
As mentioned I believe this is a timeout problem.
Does anybody know how the CIFS/SMB timeout setting in Yosemite could be changed?
Kind regards
C. -
Hi --
I've been able to insert Arabic data into an MS Access table programmatically,
using SQL and the \u notation. For example:
insert into MY_TABLE values ('\u0663'); // arabic character
Then, I can read this data out using ResultSet's getCharacterStream method. The data comes back out fine, and can be displayed in a simple JTextField as Arabic.
(This required opening the database connection using the "charSet = "UTF8" property in the call to DriverManager's getConnection method.)
My problem is that I have another Access table in which the data was entered manually -- having set the Control Panel Regional setting to Arabic, and using the MS Office Tool language Arabic. The data looks fine in the Access GUI (the Arabic characters show up as Arabic).
However, when I read the data using the same method in the first example, I get back question marks. I guess there's something different about the way the data was encoded? I read that Access stores all character data as Unicode, but I'm not sure if that implies a particular encoding (such as UTF8) or not.
Is there any way to figure out how the manually-entered data is encoded?
Or is there something else I'm doing wrong?
Thanks for any help.
-JHowever, when I read the data using the same method
in the first example, I get back question marks. I
guess there's something different about the way the
data was encoded? I read that Access stores all
character data as Unicode, but I'm not sure if that
implies a particular encoding (such as UTF8) or not.
Is there any way to figure out how the
manually-entered data is encoded?
Please see the article here: http://office.microsoft.com/en-us/assistance/HP052604161033.aspx
It suggests that Access stores data in UTF-16 or UTF-8 depending on whether a "Unicode Comression" feature is selected. So, I'd say you should try retrieving data from the other db as UTF-16.
Regards,
John O'Conner -
Map linux shared folders to Z drive in Windows Client. Unable to login through Samba Server
Hi,
I am trying to map my linux machine to a network drive Z in Windows 7 . I added user guid in smbusers and created a password for this user through smbpasswd . Started Samba server on linuc, but when trying to create a network drive, it is asking for the login. I used credentials as GUID/<CREATEDPWD> . Not able to login with these credentials. Am I missing something. My Domain is ORADEV. I attached related files smb.conf,lmhosts,smbusers files. Please let me know if i am not configuring samba server correctly.
Here is the sm.conf file Details :
# 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 (perhaps too
# many!) most of which are not shown in this example
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = ORADEV
# server string is the equivalent of the NT Description field
server string = %L (ST Samba Host), RedHat AS %v
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# if you want to automatically load your printer list rather
# than setting them up individually then you'll need this
# printcap name = /etc/printcap
# load printers = yes
# It should not be necessary to spell out the print system type unless
# yours is non-standard. Currently supported print systems include:
# bsd, sysv, plp, lprng, aix, hpux, qnx
# printing = lprng
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
guest account = adoddi
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 0
# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = server
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
password server = *
password server =Samba Server
# Password Level allows matching of _n_ characters of the password for
# all combinations of upper and lower case.
; password level = 8
; username level = 8
# You may wish to use password encryption. Please read
# ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
# Do not enable this option unless you have read those documents
encrypt passwords = yes
smb passwd file = /etc/samba/smbpasswd
# The following is needed to keep smbclient from spouting spurious errors
# when Samba is built with support for SSL.
; ssl CA certFile = /usr/share/ssl/certs/ca-bundle.crt
# The following are needed to allow password changing from Windows to
# update the Linux sytsem password also.
# NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
# NOTE2: You do NOT need these to allow workstations to change only
# the encrypted SMB passwords. They allow the Unix password
# to be kept in sync with the SMB password.
; unix password sync = Yes
; passwd program = /usr/bin/passwd %u
; passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
# Unix users can map to different SMB User names
; username map = /etc/samba/smbusers
# 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 = /etc/samba/smb.conf.%m
# This parameter will control whether or not Samba should obey PAM's
# account and session management directives. The default behavior is
# to use PAM for clear text authentication only and to ignore any
# account or session management. Note that Samba always ignores PAM
# for authentication in the case of encrypt passwords = yes
; obey pam restrictions = yes
# Most people will find that this option gives better performance.
# See speed.txt and the manual pages for details
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Configure remote browse list synchronisation here
# request announcement to, or browse list sync from:
# a specific host or from / to a whole subnet (see below)
; remote browse sync = 192.168.3.25 192.168.5.255
# Cause this host to announce itself to local subnets here
; remote announce = 192.168.1.255 192.168.2.44
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
domain master = no
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
preferred master = no
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# 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 = 130.35.62.34
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The built-in default for versions 1.9.17 is yes,
# this has been changed in version 1.9.18 to no.
dns proxy = no
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
; preserve case = no
; short preserve case = no
# Default case is normally upper case for all DOS files
; default case = lower
# Be very careful with case sensitivity - it can break things!
; case sensitive = no
#============================ Share Definitions ==============================
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
[ade]
comment = ADE Directory
path = /ade_global/
public = no
writable = yes
[homes]
comment = Home Directories (UNIX Home Dirs auto_home)
browseable = no
writable = yes
valid users = %S
create mode = 0664
directory mode = 0775
# If you want users samba doesn't recognize to be mapped to a guest user
map to guest = bad user
security = user
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
#[printers]
# comment = All Printers
# path = /var/spool/samba
# browseable = no
# Set public = yes to allow user 'guest account' to print
# guest ok = no
# writable = no
# printable = yes
# This one is useful for people to share files
[tmp]
comment = Temporary file space on %L
path = /tmp
read only = no
public = yes
# This is for the /private dir
[private]
comment = /private file space on %L
path = /private
read only = no
public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /home/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
[public]
path =: /usr/somewhere/else/public
public = yes
only guest = yes
writable = yes
printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
Here is the smbusers file : adoddi is my GUID
# Unix_name = SMB_name1 SMB_name2 ...
root = administrator admin
nobody = guest pcguest smbguest
adoddi = adoddi
lcmHosts File :
127.0.0.1 localhostHi,
To clarify a couple of things:
1- "reverse-route" does not have anything to do with this issue, the problem relies on the Windows 7 machine.
2- Do you connect with an Admin account (Windows admin)?
3- Do you run the VPN client as an administrator?
4- Have you tried to disable any AV or software protection on the machine (just for testing).?
Let me know.
Portu.
Please rate any helpul posts
Message was edited by: Javier Portuguez -
[SOLVED]Samba not working despite all my efforts
Hi all, this be my first post ever.
I am somewhat of a noob, jumped over to arch64 after ubuntu about a month ago, so please bear with me if I seem a little "behind".
I've spent probably a total of 24 hours trying to get my Samba shares available to my other housemates. They can see the shares, but cannot mount them (windows and linux). All I want is for a public share to be writable, everything else read-only and the security to be "share" (I don't want unix accounts for each of my housemates, and this would be annoying for anyone else who drops in with their laptops). I've trolled the internet for every how-to guide and nothing seems to work. What is further annoying is that one of my housemates also runs arch and his (near) exact smb.conf doesn't work for me.
Anyway, to business. My smb.conf:
# 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 (perhaps too
# many!) most of which are not shown in this example
# For a step to step guide on installing, configuring and using samba,
# read the Samba-HOWTO-Collection. This may be obtained from:
# http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
# Many working examples of smb.conf files can be found in the
# Samba-Guide which is generated daily and can be downloaded from:
# http://www.samba.org/samba/docs/Samba-Guide.pdf
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentry and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command "testparm"
# to check that you have not made any basic syntactic errors.
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = HOUSEOTDAMNED
# server string is the equivalent of the NT Description field
server string = ***
# Security mode. Defines in which mode Samba will operate. Possible
# values are share, user, server, domain and ads. Most people will want
# user level security. See the Samba-HOWTO-Collection for details.
security = share
# This option is important for security. It allows you to restrict
# connections to machines which are on your local network. The
# following example restricts access to two C class networks and
# the "loopback" interface. For more examples of the syntax see
# the smb.conf man page
; hosts allow = 192.168.1. 192.168.2. 127.
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
load printers = yes
# you may wish to override the location of the printcap file
; printcap name = /etc/printcap
# on SystemV system setting printcap name to lpstat should allow
# you to automatically obtain a printer list from the SystemV spool
# system
; printcap name = lpstat
# It should not be necessary to specify the print system type unless
# it is non-standard. Currently supported print systems include:
# bsd, cups, sysv, plp, lprng, aix, hpux, qnx
; printing = cups
# Uncomment this if you want a guest account, you must add this to /etc/passwd
# otherwise the user "nobody" is used
; guest account = pcguest
# this tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/%m.log
# Put a capping on the size of the log files (in Kb).
max log size = 50
# Use password server option only with security = server
# The argument list may include:
# password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
# or to auto-locate the domain controller/s
# password server = *
; password server = <NT-Server-Name>
# Use the realm option only with security = ads
# Specifies the Active Directory realm the host is part of
; realm = MY_REALM
# Backend to store user information in. New installations should
# use either tdbsam or ldapsam. smbpasswd is available for backwards
# compatibility. tdbsam requires no further configuration.
; passdb backend = tdbsam
# 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.
# Note: Consider carefully the location in the configuration file of
# this line. The included file is read at that point.
; include = /usr/local/samba/lib/smb.conf.%m
# Configure Samba to use multiple interfaces
# If you have multiple network interfaces then you must list them
# here. See the man page for details.
; interfaces = 192.168.12.2/24 192.168.13.2/24
# Browser Control Options:
# set local master to no if you don't want Samba to become a master
# browser on your network. Otherwise the normal election rules apply
; local master = no
# OS Level determines the precedence of this server in master browser
# elections. The default value should be reasonable
; os level = 33
# Domain Master specifies Samba to be the Domain Master Browser. This
# allows Samba to collate browse lists between subnets. Don't use this
# if you already have a Windows NT domain controller doing this job
; domain master = yes
# Preferred Master causes Samba to force a local browser election on startup
# and gives it a slightly higher chance of winning the election
; preferred master = yes
# Enable this if you want Samba to be a domain logon server for
# Windows95 workstations.
; domain logons = yes
# if you enable domain logons then you may want a per-machine or
# per user logon script
# run a specific logon batch file per workstation (machine)
; logon script = %m.bat
# run a specific logon batch file per username
; logon script = %U.bat
# Where to store roving profiles (only for Win95 and WinNT)
# %L substitutes for this servers netbios name, %U is username
# You must uncomment the [Profiles] share below
; logon path = \\%L\Profiles\%U
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
; wins support = yes
# 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
# WINS Proxy - Tells Samba to answer name resolution queries on
# behalf of a non WINS capable client, for this to work there must be
# at least one WINS Server on the network. The default is NO.
; wins proxy = yes
# DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
# via DNS nslookups. The default is NO.
dns proxy = no
# These scripts are used on a domain controller or stand-alone
# machine to add or delete corresponding unix accounts
; add user script = /usr/sbin/useradd %u
; add group script = /usr/sbin/groupadd %g
; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
; delete user script = /usr/sbin/userdel %u
; delete user from group script = /usr/sbin/deluser %u %g
; delete group script = /usr/sbin/groupdel %g
#============================ Share Definitions ==============================
;[homes]
; comment = Home Directories
; browseable = no
; writable = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /usr/local/samba/lib/netlogon
; guest ok = yes
; writable = no
; share modes = no
# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
;[Profiles]
; path = /usr/local/samba/profiles
; browseable = no
; guest ok = yes
# NOTE: If you have a BSD-style print system there is no need to
# specifically define each individual printer
[printers]
comment = All Printers
path = /var/spool/samba
browseable = yes
public = yes
guest ok = yes
writable = no
printable = yes
# This one is useful for people to share files
;[tmp]
; comment = Temporary file space
; path = /tmp
; read only = no
; public = yes
# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = @staff
# Other examples.
# A private printer, usable only by fred. Spool data will be placed in fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
; comment = Fred's Printer
; valid users = fred
; path = /homes/fred
; printer = freds_printer
; public = no
; writable = no
; printable = yes
# A private directory, usable only by fred. Note that fred requires write
# access to the directory.
;[fredsdir]
; comment = Fred's Service
; path = /usr/somewhere/private
; valid users = fred
; public = no
; writable = yes
; printable = no
# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %U option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
; comment = PC Directories
; path = /usr/pc/%m
; public = no
; writable = yes
# A publicly accessible directory, read/write to all users. Note that all files
# created in the directory by users will be owned by the default user, so
# any user with access can delete any other user's files. Obviously this
# directory must be writable by the default user. Another user could of course
# be specified, in which case all files would be owned by that user instead.
[public]
path = /home/***/Data/public/
public = yes
guest ok = yes
only guest = yes
guest account = nobody
browsable = yes
writable = yes
printable = no
# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
; comment = Mary's and Fred's stuff
; path = /usr/somewhere/shared
; valid users = mary fred
; public = no
; writable = yes
; printable = no
; create mask = 0765
The group "nobody" does exist in /etc/group. I have also made sure that "public" has 777 permissions. The others shares aren't here as I kinda figured as one works, the others would follow suit when I add them.
If it helps, my rc.conf daemons and modules:
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(vboxdrv usblp acpi_cpufreq cpufreq_ondemand cpufreq_powersave fuse)
DAEMONS=(@syslog-ng @alsa @cpufreq hal fam gdm !network @crond @portmap @networkmanager @samba @netfs @cups @ntpd @xinetd)
For what it's worth, I don't think my housemate uses networkmanager.
Any help would be greatly appreciated, this is driving me insane. Please let me know if any more info would help also.
Thanks!
Last edited by o1911 (2009-05-15 09:35:13)That did it- thank you very much!
edit: not sure how to put [SOLVED] in the topic...
Last edited by o1911 (2009-05-15 08:36:39) -
Samba and Solaris, access slow via XP
Hi everyone,
I've new to solaris and I've installed 10, update 5. I've configured samba (very badly I believe) so that I can access my solaris box from my XP 64 computer.
Both are on a local network (connected via a Belkin router) and in the same workgroup. I can see the XP machine from solaris, but not access anything (I just get a 'cannot show contents of directory' message). This is not my main problem, since I mostly want to access the solaris system from XP (I want to set up the solaris box as a RAID Z NAS). This works to a degree. I can see and access my solaris filesystem from XP. Hurray. I have two problems:
1. I have set guest to NO, but I never get asked for a password (I've set up an account on the solaris system with a password using smbpasswd). I just get access. Why is this? I don't want a bunch of ner-do-wels skulking about my server and erasing files and such.
2. While I can stream music fine, after a minute or so, if I want to browse files from XP it stalls for about one minute (I think it is re-logging in) and while this happens any music being streamed stops. How do I stay connected and logged in? Here is my smb.conf:
# Samba config file created using SWAT
# from 192.168.2.3 (192.168.2.3)
# Date: 2008/05/11 18:46:15
[global]
socket options = TCP_NODELAY SO_KEEPALIVE IPTOS_LOWDELAY
ldap ssl = no
[home]
read only = No
guest ok = No
available = No
[homes]
valid users = %S
read only = No
guest ok = No
As you can tell I'm pretty new to all this so you may have to dumb down your answers a little. Thanks for the help.
CiscoYup.....repeatable!
Delete mapped drive.
Connect via USB
Playbook shows in windows explorer as PlayBook [Pin: number] Y: being the drive that XP has mapped it to.
Then search for the PlayBook by ip address \\192.168.1.x
It shows up under workgroup by its ip address
Disconect USB cable
Workgroup connect remains (via wifi)
Strange to say the least. -
Issues with Samba and Solaris 10 when number of group is greater than 16
Has anyone heard if Sun plan to increase the value of ngroups_max from 16 to something larger in the next release of Solaris.
I have just upgraded Samba from version 3.2 to 3.3-3.4 and now users that belong to more than 16 groups have no access the shares.
I know the value can be increased via /etc/system but this breaks other stuff.
What I need is either Samba to take this limitation into account or SUN to overcome the restriction.
Edited by: neilnewman on Sep 22, 2009 8:30 AM
Edited by: neilnewman on Sep 22, 2009 8:34 AMAfter some more digging around to help myself, I found a way to get users that belong to more than 16 Windows groups access to the Samba shares under Solaris.
Using a source copy of Samba 3.2.15
cd source/lib
edit util.c
around line 460 I added the following of lines of code:
if (*num_gids >14)
*num_gids=15;
Provided the users in question that require Samba access have the group they need within the first 15 groups, all works OK.
I presume this could also be done with latter versions of Samba, but I have not taken a look at this point. -
Fstab,samba and ntfs trouble!!
Hi!
I have setup samba, everything is working..but!
I use gnome-2.12 for the moment, with hal/dbus and I have been trying to figure out WHY the h*ll gnome can mount the smbfs harddrive, but not unmount it when finished...this ends up with I having like twenty different "mount /mnt/samba " pids if I do a ps -ef
then I have to umount every single one of them by hand and as root!
So , i figured, hey, I must make umount accessible by my user, and I did, it workes because I can umount my ordinary harddrive as a user, but not the sambashare...
SO I read some more with google, and found that this is a bug in umount, so my question is:
Can I use smbumount with the sambashares instead ?? (because that one work)...the trouble is that I can't seem to find any option in GNOME to set which command to use when mounting/unmounting smbfs
or, even better perhaps, is there other ways to get shared files from a Windows machine than using Samba?
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
none /dev/pts devpts defaults 0 0
none /dev/shm tmpfs defaults 0 0
/dev/cdrom /mnt/cd auto ro,user,noauto,unhide 0 0
/dev/hda7 swap swap defaults 0 0
/dev/hda2 / reiserfs defaults 0 0
/dev/hda5 /mnt/blandad ntfs rw,uid=1000,gid=100,owner,noauto,exec,umask=0000,nls=iso8859-1 0 0
/dev/hda6 /home/spel reiserfs users,auto 0 0
//server/film /mnt/film smbfs noauto,users,gid=users,nls=iso8859-1,noatime,exec,username=guest,password,workgroup=HEM 0 0
//server/music /mnt/musik smbfs noauto,users,gid=users,iocharset=iso8859-1,noatime,exec,username=guest,password,workgroup=HEM 0 0
//server/backup /mnt/backup smbfs noauto,users,gid=users,iocharset=iso8859-1,noatime,exec,username=guest,password,workgroup=HEM 0 0CyberTron wrote:is there other ways to get shared files from a Windows machine than using Samba?
If you install M$ SFU on the Windoze box, you can use NFS to connect to it. -
Two-way SSL: Private key is incorrectly read if the charset is set to UTF8
Looks like PEMInputStream and other related classes assumes the application charset
"iso81", but if the charset is something else, then "java.security.KeyManagementException"
is thrown.
We have everything setup and two-way ssl works when the encoding is not set. but
brakes if the encoding is UTF8.
WLS 7.0
OS - HP-UX
Is there any other workaround (not setting UTF8 is not a solution, ours is a WW
app).
ThanksI would suggest posting this to the security newsgroup.
-- Rob
Govinda Raj wrote:
Looks like PEMInputStream and other related classes assumes the application charset
"iso81", but if the charset is something else, then "java.security.KeyManagementException"
is thrown.
We have everything setup and two-way ssl works when the encoding is not set. but
brakes if the encoding is UTF8.
WLS 7.0
OS - HP-UX
Is there any other workaround (not setting UTF8 is not a solution, ours is a WW
app).
Thanks
Maybe you are looking for
-
need help
-
What do I need to do to make a our website currently running on a WINDOWS based server to a Linux Se
Will dreamweaver convert my site to work on LINUX servers..? All my pages are .asp.
-
Can't download music onto nokia 5800 - please hel...
Hi I've got music in my music vault which I just can't seem to download. Everytime it says insufficient memory. I've checked all the trouble shooting advice etc... and looked at filemangager and deleted lots of files. Basically there should be enough
-
BPF - Impossible to create BPF
I'd like to create a BPF in BPC 7.5 NW SP3 version but I've got errors (message box) when I choose "Create new BPF Template" in the Action Pane in Administration Interface : System.Xml.XmlException: The root is missing. at System.Xml.XmlTextReader.Re
-
Hi, I have a large table about 8 GB i need to add a new column to this table and update new column values of all the present records. Please let me know any good methods for the same. while doing i same i also intend to partition the table. Thanks in