Samba 3.3.3-1 i686 issue

i just upgraded samba on my 2 boxes and ran into this problem when restarting the service
[root@$$$ hasan]# /etc/rc.d/samba start
:: Starting Samba Server [BUSY]
/usr/sbin/smbd: error while loading shared libraries: libavahi-client.so.3: cannot open shared object file: No such file or directory [FAIL]

Hi all, I run into the same problem. I tried to `pacman -S --asdep avahi`, but that listed almost 30MB in dependencies:
dbus-core xcb-proto xproto libxdmcp libxau libxcb kbproto libx11 libice libsm dbus libdaemon glib2
While on my desktop Arch Linux this is ok, on another Arch (mini and GUIless, used with CoLinux) this is a no-no.
Is this dependency really necessary? Or it just "slipped" out of control? I'm curious, since I see many GUI-related libraries among these new unchecked deps, and I've never configured Samba in any other way than `nano /etc/samba/smb.conf`, so I suspect this avahi has to do with some leaked requisites from a Samba GUI config tool?
Last edited by ColdShine (2009-04-14 15:19:13)

Similar Messages

Samba timeout when trying to connect to a computer in a workgroup

Hello, seems like the best section to post this in...
Right after I installed my Archlinux setup, I spent a bunch of time trying to get samba running perfectly, mainly, it was just so that other (window$) computers could access mine. Upon getting it working perfectly, both ways, I didn't use it for a while (which is typically the case).
So today, I need to transfer lots and lots of data, but via Dolphin, browsing the workgroup (which I clicked), lists all the computers that are there, including my own (this).
That's good so far, but after I browse to one of those computers (even my own!!), shortly thereafter, I receive a timeout error.
I have tried restarting the samba daemon, netfs, I also tried stopping network manager, and starting the network daemon myself, hoping it was network manager's brokenness that was the problem. Nope.
Still left in this situation...and nothing that I can remember, has changed since the last time, I didn't screw with config files or anything. Although, I do think I changed routers between this time, I also remember seeing some updates for samba-related packages.
All out of ideas, I posted here.
I can post my smb.conf file..or anything else for that matter, if you want. I just want this problem to be solved, and currently am forced to boot into window$ to transfer lots of data. Naturally, I can't do anything during this time, when not in linux....and it kills me a little bit more each time I have to see it
EDIT: Also note that, I tried using the default config, but I still get timeouts(and restarting samba daemon of course). With 'smbtree', it lists all of the shares available on the workgroup also. I also use the gamin program, as opposed to FAM. Originally, I followed the wiki, and that was how I get it working in the first place, but no longer does it work correctly. The logs in /var/log/samba/ do not show anything interesting, and in fact, only show about 1-2 lines, just saying that it started..
I also had it say about a firewall possibly being in use, but on a reload/retry, it returns to a timeout error. I do not have any firewalls that I am aware of, on.
Update: Well I figured out if I run the following command: smbclient '\\NAS\Data' that I will then be taken to a prompt where I can do ls, cd, etc, and browse that share perfectly. What's going on here? Dolphin still times out on it and I would prefer to use a GUI for this..
Last edited by sreich (2009-06-26 17:00:14)

Well I decided to try to use 'smb4k', which I just recently found, it also sees all of the computers on my network, but it also sees their shares after I browse into it. Unfortunately, it fails to mount any of them...
"mount error: could not resolve address for NAS: Name or service not known
No ip address specified and hostname not found"
That is the message I receive after clicking (mounting) on one of the shares of the 'NAS' computer, the one on my network.
Perhaps this error will make things a bit more clear?
I've been even looking at the docs at samba.org, trying to debug this issue...
UPDATE: Seem to have limited the problem down, at least now I can mount a share on a computer but *only* if I specify the IP address manually.
So it appears that it cannot resolve the name of said computer/share, to an IP... what could be causing this, and how can I fix it?
Last edited by sreich (2009-06-26 19:17:12)

Kernel26 2.6.28-3: touchpad doesn't move cursor, touchpad buttons work

I issued a "sudo pacman -Syu" today. The following are the packages which were updated:
[corey@sariss ~]$ ls -l /var/cache/pacman/pkg/ | grep 2009-01-16
-rw-r--r-- 1 root root 712494 2009-01-16 15:07 catalyst-8.12-3-i686.pkg.tar.gz
-rw-r--r-- 1 root root 53907 2009-01-16 15:07 hdparm-9.6-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 29295975 2009-01-16 15:07 kernel26-2.6.28-3-i686.pkg.tar.gz
-rw-r--r-- 1 root root 2868747 2009-01-16 15:07 klibc-1.5.15-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 10840 2009-01-16 15:07 klibc-extras-2.5-2-i686.pkg.tar.gz
-rw-r--r-- 1 root root 40272 2009-01-16 15:07 klibc-kbd-1.15.20080312-8-i686.pkg.tar.gz
-rw-r--r-- 1 root root 37579 2009-01-16 15:07 klibc-module-init-tools-3.5-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 104013 2009-01-16 15:07 klibc-udev-135-2-i686.pkg.tar.gz
-rw-r--r-- 1 root root 4467592 2009-01-16 15:07 man-pages-3.16-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 16341 2009-01-16 15:07 mkinitcpio-0.5.20-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 303734 2009-01-16 15:07 module-init-tools-3.5-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 500508 2009-01-16 15:06 pacman-3.2.2-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 33495 2009-01-16 15:07 pycairo-1.8.0-2-i686.pkg.tar.gz
-rw-r--r-- 1 root root 18718108 2009-01-16 15:08 qt-4.4.3-4-i686.pkg.tar.gz
-rw-r--r-- 1 root root 793 2009-01-16 15:08 rpmextract-1.0-3-i686.pkg.tar.gz
-rw-r--r-- 1 root root 22588028 2009-01-16 15:08 samba-3.2.7-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 13741159 2009-01-16 15:08 smbclient-3.2.7-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 405587 2009-01-16 15:07 sqlite3-3.6.9-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 114138 2009-01-16 15:08 tdb-3.2.7-1-i686.pkg.tar.gz
-rw-r--r-- 1 root root 221718 2009-01-16 15:08 xterm-239-1-i686.pkg.tar.gz
After updating and rebooting, I notice my laptop touchpad no longer works. A USB optical mouse does work, and the touchpad mouse buttons work, but I cannot use the touchpad to move the mouse whatsoever. I have hotplugging disabled in xorg.conf.
I don't have a clue which package could have affected this... any suggestions will be greatly appreciated.
[EDIT]: On a hunch, I rolled back to kernel26 2.6.27.10-1, and my touchpad is working again. Clearly this is a problem with the new kernel. Suggestions are still appreciated, as I'd like to stay up-to-date!
Last edited by cmtptr (2009-01-16 23:31:48)

My Elantech touchpad won't work in Arch Linux with the 2.6.28 kernel either. I get a bunch of garbage in the kernel messages like below:
Jan 18 15:35:36 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:36 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:36 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:36 feathers psmouse.c: Touchpad at isa0060/serio4/input0 - driver resynched.
Jan 18 15:35:36 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:36 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:36 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:36 feathers psmouse.c: Touchpad at isa0060/serio4/input0 - driver resynched.
Jan 18 15:35:36 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:36 feathers psmouse.c: Touchpad at isa0060/serio4/input0 - driver resynched.
Jan 18 15:35:37 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:37 feathers psmouse.c: Touchpad at isa0060/serio4/input0 - driver resynched.
Jan 18 15:35:37 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:37 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:37 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:37 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:37 feathers psmouse.c: Touchpad at isa0060/serio4/input0 lost sync at byte 4
Jan 18 15:35:37 feathers psmouse.c: issuing reconnect request
Jan 18 15:35:37 feathers input: PS/2 Generic Mouse as /class/input/input8
Jan 18 15:35:37 feathers psmouse.c: Failed to enable mouse on isa0060/serio1
I do not have an fdl file for the Synaptics driver. Is that necessary? Also, I'm wondering if this could be connected to Ubuntu Bug #34501.

Windows Services don't show as started in Server Manager

Server manager does not show Windows services as being started on one of our xserves - although Samba is up and operational just fine.
Even after re-starting the server after we moved a month or so ago it has not shown windows as being started. Samba came up ok after reboot with no intervention.
Here's the processes and PIDs:
xserve1:/var/run root# more smbd.pid
853
xserve1:/var/run root# ps ax | grep 853
8432 p2 R+ 0:00.00 grep 853
xserve1:/var/run root# more nmbd.pid
24215
xserve1:/var/run root# ps ax | grep 24215
24215 ?? Ss 0:16.63 /usr/sbin/nmbd -D
8441 p2 R+ 0:00.00 grep 24215
Not sure how to recalibrate Server Manager to recognise that the service is actually running.
Any clues?
Thanks,
Campbell
XServes Mac OS X (10.4.5) 12 Macs & several hundred too many PCs

That happened to me after the update to 10.4.4 and the issue was that somehow com.apple.smbd got set back to start in launchctl.
To see if this is your issue, run this command
Code:
ps alx | grep mbd
You will probably notice that there are not just one each of SMBD and NMBD but one of them has 2 processes. In my case it was like this
0 10269 1 0 31 0 30664 328 - S ?? 0:00.00 /usr/sbin/smbd -D
0 10275 1 0 31 0 28464 684 - Ss ?? 0:00.01 /usr/sbin/nmbd -D
0 10277 10275 0 31 0 28452 184 - S ?? 0:00.00 /usr/sbin/nmbd -D
501 10284 1959 0 31 0 27820 4 - R+ p1 0:00.00 grep mbd
Your post about smbd.pid being the 'wrong' one is the hint that this is going on.
So next run this
Code:
sudo launchctl list
and if you see in that list this
org.samba.smbd
you have the same issue. So to stop this I ran a GUI program called Lingon to unload and disable the offending plist (called smbd.plist in /System/Library/LaunchDaemons) but I think you can run the following to do the same thing
Code:
sudo launchctl unload -w org.samba.smbd
Peter
PowerMac G5 Dual 2.5Ghz Mac OS X (10.4.5) Server

Browsing SMB shares

Hi there,
I am seeing a strange problem with my new MacBook Pro. I have a windows machine on which I have a number of shares. With my older Macs I am able to enter smb://<machinename>/ in to the Connect to Server dialogue, and it shows me a list of the shares currently available on that machine, and then prompts me to log in to them.
On my MacBook if I try the same thing (smb://<machinename>/) without specifiying a specific share, the whole machine just hangs and sits there with a spinning beach ball. However, if I specify the name of one of the shares on the machine (eg. smb://<machinename>/<share>) then it connects perfectly.
Anyone else seeing this, or got any suggestions?
Thanks

got another samba update today but still same issue. Half the time it won't even open browse network itself (says something about it being mounted in another location)
Last edited by bwat47 (2011-08-18 04:01:05)

Viability question

Hello,
I have just been told to deploy a system which involves image and audio streaming and some other things. I've heard about JMF, but I'd like to ask for your expert oppinion. Here's a brief description of the system:
There's a central computer and 2 identical hosts. Each host has got a camera, microphone, speakers, a push button which is used to "ring" the central computer, and a small circuit which opens a door. As you can imagine this system will be used to guard remotely two doors.
The central computer must show the content of the webcams, and be able both to hear and to speak to the hosts.
a) JMF has support for video and audio streaming? Does it work with GNU/Linux? Which classes are involved? (last question is a "where to begin from" one)
b) In order to implement the "call" button and the door opening system I'm thinking about using serial or USB ports. How can I access them with Java? Can I use low enough level methods to activate the lines?
Thank you very much for your attention
P.D.: is there any similar system already implemented (and avalaiable)?

Originally Posted by ataubman
For some values of "heavily used", yes I'd say it should work for you OK. The main problem being, if you do discover any problems there are unlikely to be any new patches for NW.
For CIFS on NetWare I'd go further and replace "are unlikely to" with "will not". Okay there might be the odd FTF but I'd say you've got to be pretty special to now get an issue fixed.
With the release of Windows Vista in 2006 Microsoft introduced SMB2 (SMB 2.0) with SMB 2.1 introduced with Windows 7 & Windows Server 2008 R2 and SMB 2.2 coming with Windows 8. CIFS on neither NetWare or OES (Linux) can do SMB2 so SMB1 is used instead. See Server Message Block - Wikipedia, the free encyclopedia
CIFS on NetWare is (understandably) behind the curve but CIFS in OES requires enhancements plus Samba needs updating (OES11 has Samba 3.4).
@Lawrence, the issue with using CIFS is not usually "Large userbase and very heavy volume use" but one of the number of CIFS connections to be supported.
In answer to your question, if this is a "new" install then skip NetWare and go with OES. If DSfW I'd be inclined to go with OES11 but for just CIFS (not Samba) either OES2 SP3 (fully patched) or OES11 will work.
HTH.

Browsing SMB shares in nautilus broken

After some recent updates to samba (don't remember exactly what was updated, but I remember it was definitely some stuff to do with samba and this problem came up right after) I can no longer view any of my windows shares. I use gnome 3 and view my windows shares through nautilus. This used to work fine after only installing samba and gvfs-smb. Now when I try and browser shares it constantly freezes, in seemingly random places. Sometimes just clicking "browse networks" nothing happens. Sometimes it works fine and I can click windows network, but when I click "WORKGROUP" it freezes and then says unable to retrieve share list.
Last edited by bwat47 (2011-08-14 17:30:36)

got another samba update today but still same issue. Half the time it won't even open browse network itself (says something about it being mounted in another location)
Last edited by bwat47 (2011-08-18 04:01:05)

Samba 3.2.6 patch for security issue

I know the security issue is hard to trigger, but I created a new PKGBUILD for samba 3.2.6 containing the patch.
Excerpt from the patch commentary:
commit 288fa94ac7cfdf7457b5098c33fc840bed3d5410
Author: Michael Adam <[email protected]>
AuthorDate: Thu Dec 18 18:01:55 2008 +0100
Commit: Karolin Seeger <[email protected]>
CommitDate: Fri Dec 19 08:30:23 2008 +0100
smbd: prevent access to root filesystem when connecting with empty service name
This only applies to a setup with "registry shares = yes"
Michael
And here's the PKGBUILD:
# $Id: PKGBUILD 22200 2008-12-22 22:24:26Z tpowa $
# Maintainer: judd <[email protected]>
pkgname=samba
pkgver=3.2.6
# We use the 'A' to fake out pacman's version comparators. Samba chooses
# to append 'a','b',etc to their subsequent releases, which pamcan
# misconstrues as alpha, beta, etc. Bad samba!
_realver=3.2.6
pkgrel=2.1
pkgdesc="Tools to access a server's filespace and printers via SMB"
arch=(i686 x86_64)
url="http://www.samba.org"
license=('GPL3')
backup=(etc/logrotate.d/samba etc/pam.d/samba etc/samba/smb.conf etc/xinetd.d/swat etc/conf.d/samba)
depends=('db>=4.7' 'popt' 'libcups' 'acl' 'libldap' 'smbclient=3.2.6' 'libcap' 'heimdal>=1.2-1' 'pam' 'fam' 'gnutls>=2.4.1' 'tdb=3.2.6')
options=(!makeflags)
source=(http://us1.samba.org/samba/ftp/stable/${pkgname}-${_realver}.tar.gz \
no-clients.patch samba samba.logrotate swat.xinetd samba.pam samba.conf.d \
ftp://us1.samba.org/pub/samba/patches/security/samba-3.2.6-CVE-2009-0022.patch)
build() {
cd ${srcdir}/${pkgname}-${_realver}/source
patch -Np2 -i ${srcdir}/no-clients.patch || return 1
patch -Np2 -i ${srcdir}/samba-3.2.6-CVE-2009-0022.patch || return 1
./configure --prefix=/usr --with-configdir=/etc/samba \
--with-lockdir=/var/cache/samba \
--with-piddir=/var/run/samba \
--with-fhs --with-pam --with-ads --with-acl-support \
--without-cifsmount --without-libsmbclient \
--with-syslog --with-pam_smbpass \
--localstatedir=/var --disable-dnssd --libdir=/usr/lib/samba
make || return 1
mkdir -p ${pkgdir}/var/log/samba
mkdir -p ${pkgdir}/etc/samba/private
chmod 700 ${pkgdir}/etc/samba/private
make DESTDIR=$startdir/pkg install
chmod 644 ${pkgdir}/usr/include/*.h
rm -rf ${pkgdir}/usr/var
(cd script; cp installbin.sh i; cat i | sed 's/\/sbin\///' > installbin.sh)
install -D -m755 ../../samba ${pkgdir}/etc/rc.d/samba
install -D -m644 ../../samba.conf.d ${pkgdir}/etc/conf.d/samba
mkdir -p ${pkgdir}/etc/samba
cat ../examples/smb.conf.default | \
sed 's|log file = .*$|log file = /var/log/samba/log.%m|g' >${pkgdir}/etc/samba/smb.conf.default
install -D -m644 ../../samba.logrotate ${pkgdir}/etc/logrotate.d/samba
install -D -m644 ../../swat.xinetd ${pkgdir}/etc/xinetd.d/swat
install -D -m644 ../../samba.pam ${pkgdir}/etc/pam.d/samba
# symlink libs
for i in ${pkgdir}/usr/lib/samba/libsmbshare*; do
ln -sf samba/$(basename $i) ${pkgdir}/usr/lib/$(basename $i)
done
# spool directory
install -d -m1777 ${pkgdir}/var/spool/samba
sed -i 's|/usr/spool/samba|/var/spool/samba|g' ${pkgdir}/etc/samba/smb.conf.default
# fix logrotate
sed -i -e 's|log.%m|%m.log|g' ${pkgdir}/etc/samba/smb.conf.default
# nsswitch libraries
install -D -m755 nsswitch/libnss_wins.so ${pkgdir}/lib/libnss_wins.so
ln -s libnss_wins.so ${pkgdir}/lib/libnss_wins.so.2
install -D -m755 nsswitch/libnss_winbind.so ${pkgdir}/lib/libnss_winbind.so
install -D -m755 bin/pam_winbind.so ${pkgdir}/lib/security/pam_winbind.so
# remove conflict files of smbclient and tdb
for man in libsmbclient smbspool \
umount.cifs mount.cifs net; do
rm -f ${pkgdir}/usr/share/man/man8/${man}.8
done
for i in libnetapi* libtdb* libtalloc* libwbclient*; do
rm -f ${pkgdir}/usr/lib/samba/$i
done
rm -f ${pkgdir}/usr/bin/tdbbackup
rm -f ${pkgdir}/usr/include/{tdb.h,talloc.h,netapi.h}
for man in rpcclient smbcacls smbclient smbcquotas \
smbtree smbtar nmblookup smbget; do
rm -f ${pkgdir}/usr/share/man/man1/${man}.1
done
rm -f ${pkgdir}/usr/share/man/man7/libsmbclient.7
rm -f ${pkgdir}/usr/include/libsmbclient.h
md5sums=('0cd27c7afbb8211616eea4010f32271c'
'a676f0dde2c434aeb5125376b8797a64'
'e93533fa2296c07c1f645dfdd373657f'
'5697da77590ec092cc8a883bae06093c'
'a4bbfa39fee95bba2e7ad6b535fae7e6'
'96f82c38f3f540b53f3e5144900acf17'
'f2f2e348acd1ccb566e95fa8a561b828'
'e15ab37115101cf3a8d110f0c1f8e29e')
I think a security task force should be initiated (I know discussions existed, but I don't know what were the consequences), so that important packages (like those providing services) could be updated in a timely manner. This is a minor issue as I stated earlier, but it could be worse. Those interested, let's initiate a discussion with the developers of important packages and try to get some things working. People (mostly trusted users) who can generate early packages are welcome, so that they can provide early versions of unvulnerable packages.

ckristi wrote:I don't know about other packages, but I believe when I checked the PKGBUILD for PHP, that the security fix was included in 5.2.7.
Check http://repos.archlinux.org/viewvc.cgi/p … iew=markup for more info.
And don't get me wrong, I am a little bit concerned about the way vulnerabilities are treated in Arch, 'cause my home server is running this distro.
And I really would think we should start some serious discussions about this security issues and the way they should be treated. I know the developers are doing their best and I'm not going to put fingers at all. They should be helped in maintaining packages for important services. We'll benefit from it and their tasks would be easier.
Why don't you start a wiki page tracking the latest vulnerabilities disclosed on various security mailing lists which are not fixed in arch. This will make it much easier for the devs.
This thing has been already discussed multiple times and already a wiki page exists for Arch Security Team but it seems nobody followed up with that.
http://wiki.archlinux.org/index.php/Security_Task_Force

[SOLVED] Trying to get samba to work, smbtree issues:

I am having a bit of an issue getting my computer to show up to my Mint laptop. Running smbtree as it stands right now produces this output:
Enter mikeyd's password:
WORKGROUP
\\MINT mint server (Samba, LinuxMint)
\\MINT\IPC$ IPC Service (mint server (Samba, LinuxMint))
\\MINT\print$ Printer Drivers
Here is my smb.conf file:
http://pastebin.com/M5neuVPt
# 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]
usershare path = /var/lib/samba/usershares
usershare max shares = 100
usershare allow guests = yes
usershare owner only = False
# workgroup = NT-Domain-Name or Workgroup-Name
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = %h server (Samba, ArchBoxMTD)
# 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 = bsd
# 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
# Security mode. Most people will want user level security. See
# security_level.txt for details.
security = user
# Use password server option only with security = server
; password server = <NT-Server-Name>
# 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 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*UNIX*password* %n\n *ReType*new*UNIX*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
# 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 = 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
# Use only if you have an NT server on your network that has been
# configured at install time to be a primary domain controller.
; domain controller = <NT-Domain-Controller-SMBName>
# 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
# All NetBIOS names must be resolved to IP Addresses
# 'Name Resolve Order' allows the named resolution mechanism to be specified
# the default order is "host lmhosts wins bcast". "host" means use the unix
# system gethostbyname() function call that will use either /etc/hosts OR
# DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
# and the /etc/resolv.conf file. "host" therefore is system configuration
# dependant. This parameter is most often of use to prevent DNS lookups
# in order to resolve NetBIOS names to IP Addresses. Use with care!
# The example below excludes use of name resolution for machines that are NOT
# on the local network segment
# - OR - are not deliberately to be known via lmhosts or via WINS.
; name resolve order = wins lmhosts bcast
# 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 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 ==============================
[homes]
comment = Home Directories
browseable = yes
writable = yes
public = yes
path = /home/mikeyd
guest ok = yes
share modes = yes
# Un-comment the following and create the netlogon directory for Domain Logons
; [netlogon]
; comment = Network Logon Service
; path = /home/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 = /home/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
; read only = yes
; 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
On the mint laptop, it can see its own share as well.
This is my /etc/hostname output
archboxmtd
This might help too:
mikeyd@archboxmtd ~ $ net usershare info
[Videos]
path=/home/mikeyd/Videos
comment=
usershare_acl=Everyone:F,
guest_ok=y
I have tried to get things working by following:
https://wiki.archlinux.org/index.php/Samba
https://wiki.archlinux.org/index.php/Sa … leshooting
Hopefully that gives you helpful uber dudes something to go on.
Thank you for any help you can give. I am pretty technical, but have been away from Arch and smb for a while. I should be able to follow any suggestions fine.
Thanks!
Last edited by degmic71 (2013-07-09 00:30:38)

Answered my own question, nmdb was the culprit.... dang, well saving this page for future ref:
This did it:
Starting the service
Start/enable Samba via the smbd and nmbd at boot:
systemctl enable smbd.service
systemctl enable nmbd.service
Run them right now as well (otherwise you'd have to reboot):
systemctl start smbd.service
systemctl start nmbd.service
Swat is a nice web interface too

Samba, usershares and process_usershare_file permission issue

So, after configuring the usershares as explained on the wiki, my shares are working as expected.
There is one issue though, I am constantly getting this message in my journal for each of my shares:
smbd[12799]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsprocess_usershare_file: stat of /var/lib/samba/usershare/<sharename> failed. Permission denied
(yes, that's the formatting, two messages glued together)
Searching on the net, it seems that the issue is with stat() and lstat() requiring execution permissions in the whole path to the file as described here.
Are the instructions on the wiki incomplete, and should I be setting permissions to 1770 and group to sambashare for the whole path?
Or is there another way to get rid off that message?

Yes,I have made sign applet, and able to run the .exe file while I put the code inside the paint() method
Code:
     public void paint(Graphics g) {
          try
               String command = "D:/projects/pywin32-208.win32-py2.4.exe";
               Process process = Runtime.getRuntime().exec(command);
               System.out.println("Executing command: " + command);
               g.drawString("hello java", 10,10);
          catch(Exception e){
               g.drawString("Exception :"+e, 10,10);
This code is working after sign applet. But I am trying to run the .exe file inside the testSumNum() method, when I click the button on html page.
Please suggest me what needs to do.

Does Mavericks fix interoperability issues using Samba?

Has anyone who has gotten Mavericks to work experimented with it as a server for Windows shares using Samba? This has been a long-standing interoperability issue with OS X and I'm wondering if Apple has fixed it with this release?

I usually do it by doing something like this from a client...
curl -I http://bnesse6/NetBoot/NetBootSP0/NetBoot_DS_Test.nbi/NetInstall.dmg
or
curl http://bnesse6/NetBoot/NetBootSP0/NetBoot_DS_Test.nbi/NBImageInfo.plist
The first line should connect an pull header info, the second one should fetch the NBImageInfo.plist.
Be aware that this is harder when you have spaces in the pathname.

Samba connection issues

Well, at some point, it would appear that my Samba shares stopped being available. If I attempt to navigate from my laptop to the share, I just keep getting challanged for a username/password. When I look through my samba.log file, all I am seeing is this error:
[2009/11/30 18:43:39, 0] smbd/server.c:457(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
I am going to assume that something broke on one of the updates since I had this working for quite some time before the last few weeks. I did a quick Google search and see some issues posted in the Ubuntu forums, but no real answers.
Anybody else seeing these errors?

Yeah I'm seeing both that error, and I have also started getting an error that looks like it's related to some ipv6 issues:
Matchname failed on x.y.z ::ffff:192.168.1.1
I tried everything, connecting from various windows based pc's, but I kept getting that error. Tried disabling ipv6, but that just resulted in silent errors. I also keep getting challenged for username/password, and get the above error.
For now I have compiled my own samba, which I run out of /usr/local. I hope someone can enlighten me/us on this problem, since my samba has been running for years through multiple arch-updates, and now brutally stopped.
Could it be ipv6 DNS issues? I run my own DNS.
/Rassie

Mac G5 10.3.9 Samba Issue with Windows 2000 Advanced Server??

I have just installed a new Windows 2000 Advanced Server network but the Mac G5s running OS X 10.3.9 Panther cannot navigate the server - the finder just hangs with a beachball. The PCs can navigate without any problems.
Navigation is fine on the G4 running OS X 10.2.8 Jaguar on the same network.
On the G5 I have tried creating a new user and put the Mac using DHCP but this doesn't solve the problem.
I think I have tracked down the problem to Samba but am not sure - When I type in the direct samba link to the server:-
smb://10.10.0.5
The "SMB Mount" screen asks me which share I would like to mount. This works without a problem. I create a shortcut to the share. This also works until I reboot, then the problem reoccurs!
I think I need to reinstall Samba, or update the Samba software?
Does anyone have any thoughts,
John
G5 Mac OS X (10.3.9)

HELP FROM A GUY WHO IS NOT A SYS ADMIN OR ON AN I.T. STAFF!
And with that dislcaimer...
What sort of settings do you have checked in your Directory Access > Services panel? That is, do you have SMB turned on?
Also, I would make sure that your server and computer's clocks are showing the exact same times-- just in case there is a synchronization issue.
Our Macs have had similar, but not identical, problems in the past.

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 = no

875739 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

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 AM

After 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.

Samba 3.3.3-1 i686 issue

Similar Messages

Maybe you are looking for