Samba Shares and System Lockup

Hey Guys,
So I've been having this issue since I got my MacBook Pro, when I'm using it at work I'm connected to various Samba Shares on Windows Server 2003, a Drobo, and a Windows Vista machine. Now, if I dismount all of them when I'm heading out of the office then my system is fine, but if I forget to dismount one of them the entire system locks up upon waking the Mac up. I cannot do anything and I am forced to power down and power back up.
This is endlessly annoying, as I'm sure you can imagine and I lost a large Photoshop document last night as a result.
Any ideas guys?
Thanks
Chris Pressland

I purchased our first mac in December 2010. The macbook pro utilizes SMB file shares on one of my windows 7 PC's. I am experiencing the EXACT SAME problem as everyone in this thread. It crashes at least once a week. It's not just Finder but the entire OS freezes including the Dock. It allows you to browse throw the apple menu and select "Restart" but it only hangs endlessly after that. I'm a PC/Microsoft expert and as a new mac user my experience has been extremely disappointing.
Apple: There is an abundant amount of threads on the web regarding this very same issue. It's not just inconvenient. It's extremely disruptive and frustrating. I am almost on the verge of returning the macbook since apple hasn't cared to even address this issue.

Similar Messages

Unusual disk read write and system lockup - Gen 1 MacPro dual Intel

I have had this issue for a while - but I think it is getting worse (or I'm just more tired of it). The disks start reading/writing ( I can see it in Activity Monitor) and continue for several minutes. Meanwhile, the system is fully occupied and cant be used.
In the Activity Monitor window, I notice that ICalExternalSync is using up nearly a gig or memory and 2 gigs virtual memory - is this normal?
Also, the kernal_task item is using up 58 threads, another gig of virtual memory but just 80mb of real memory. Just seems odd.
Any suggestions?
Phil
Model Name: Mac Pro
Model Identifier: MacPro1,1
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 3 GB
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B08
SMC Version (system): 1.7f10

I answered my own question - it stopped when I quit IcalExternal sync using the Activity Monitor - so now the answer is why is this service flooding my system with disk read/writes?

Leopard 10.5.5 and Linux Samba shares not connecting

I have seen this talked about many times, but I have not found the answer. And my situation is always slightly different from others...so here it is!
when I try to connect to our samba share, here are my steps...
Go
Connect to Server
smb://10.xx.xx.xx
Connect
here's where the problem is: the enter username and password pops up, and asks me to put them in...there is no user/password on our samba shares, and I cannot connect via guest either.
in Tiger, there was a work around through terminal to connect, but that doesn't apply to Leopard. We only have 2 Leopard machines here, all the rest are still Tiger, but we are eyeing upgrades, and would be forced to go up to Leopard since we can't buy new Macs with Tiger anymore.

best answer...get rid of Linux share, replaced it with an OS X server, no problems at all...

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?

How to start my Samba share correctly?

Every time I reboot my system I have to use Gadmin-Samba to re-activate my Samba share and it is quite annoying.
When I start Gadmin-Samba I get this:
http://oi44.tinypic.com/10glij4.jpg
I have to deactivate first and then activate again, then my share can be accessed by other computers. Is there any way to solve this problem?

stryder wrote:I have never used gadmin-samba so cannot help you with it. If you have a fixed folder you want to share I would suggest you look for the wiki page on Samba and set up smb.conf and then put "samba" in the daemons line in your rc.conf.
Hi thanks for your replies. I did check the wiki page where is also the place I started from zero to configure Samba in my machine.
The problem in my system seems to be linked with the winbind server because in gadmin-samba's settings window I see an option to start winbind server. And I always see a message of "inactive servers: winbindd" when I open gadmin-samba.
What is this winbind or winbindd server and how do I start it automatically?

DFS Folder Target to Samba Share not working

Hello folks,
I'm on Server 2012 R2. I'm using a DFS Namespace that is configured as standalone server (i.e. not a domain-based namespace). The Namespace is the IP address of the server. I have also tried this with the hostname of the server and I get the same results.
Here's my problem:
I've created a folder target within DFS that points to a samba share on a linux-based NAS. The samba share is a 'cloud storage' share hosted by my server host, so I'm not entirely sure what specific technology it is. It does not have a public ACL - it requires
authentication and I cannot change that. I can connect to the Namespace fine from other servers. However, when I try to open the folder target, it tells me "Logon failure: unknown user name or bad password". Then, if I right-click the folder, select
Properties then the DFS tab, I see that the path is Active. If I click Check Status, I get Okay, and when I exit, the folder is now navigable and I have no problems browsing the folders. Sometimes when I close Explorer, the share will still be accessible when
I reopen Explorer and browse to it, but most of the time when I close and reopen, the same error is displayed and I have to Check Status again to regain access. If I logout of the session, log back in and try again, it always gives me the error until I Check
Status again.
The idea is to access this share from multiple instances of IIS, so obviously requiring user intervention is not going to be suitable. I have added a local user to the DFS server that matches the valid credentials on the samba share, and I've also added
them to all the servers trying to use this share. I've confirmed that all servers can browse directly to the share. I do notice that when I browse directly to the samba share after having not used it for some time (30 minutes or one hour), it takes longer
than expected to open - maybe 10 seconds. Could this lag be causing the issue? There are no errors or warnings in the logs on the DFS server. Any ideas what this could be? Have I missed something? Massive thanks for any guidance!

Hi,
Thanks for your posting.
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Unable to access samba share.

I'm setting up a ubuntu file server with samba shares and security = user.
These shares are able to be accessed and work correctly for both linux and windows clients. When I attempt to connect to the shares in OSX I get the usual username/password dialog box, however it doesn't accept the correct credentials.
I've googled for help for a few hours now, but cannot find anything that helps. I'm guessing its a security setting somewhere in OSX, but I'm not able to find out what.
Any ideas?

turns out that I was connecting to it incorrectly.
correct method is smb:\\workgroup;user@server\share

Aperture not seeing referenced masters on Samba share

Hello all,
I have moved my referenced masters from my laptop to a Samba-mounted RAID server. I go to mount the Samba share and for some reason, Aperture won't see my referenced masters. It also shows the volume as being offline, when I know for a fact it is mounted, and can browse the Aperture masters directory to find each and every master...
Is there any way to get aperture to see these masters?
Thanks,
-Noah

OK, this is a long shot, but it happened to me once.
I tried to relocate some managed images to an AFP share which I thought was mounted but wasn't. Because the path that I wanted to relocate to was already loaded I just clicked OK and this is what happened - Aperture created a Folder in /Volumes/ with the name of the AFP volume. So later when I did mount the volume none of my referenced files showed up. This is because while the name on the desktop was correct the Path to it was /Volumes/AFP-share 1/ instead of /Volumes/AFP-share/.
So in short look in /Volumes/ (you can get there by using the Go-->Go to Folder menu in the Finder and typing /Volumes/) and see if there is a folder in there that should not be:-) If there is check to see if there are any images in it and move those to your desktop before deleting the folder.

Mounting samba share starts avahi, ssh and sftp at client

The problem is at the client. When i mount a samba share (with # mount), avahi is started, which starts ssh and sftp. This is wrong on many levels.
Not sure how long this has been going on, someone else already asked this on stackexchange on 11.2.15, but didn't get any answers.
Journal output immediatly after mounting (hostname, ip etc. removed):
Mär 18 01:35:51 hostname dbus[434]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
Mär 18 01:35:51 hostname systemd[1]: Cannot add dependency job for unit boot.automount, ignoring: Unit boot.automount is masked.
Mär 18 01:35:51 hostname systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Mär 18 01:35:51 hostname systemd[1]: Starting Avahi mDNS/DNS-SD Stack Activation Socket.
Mär 18 01:35:51 hostname systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Mär 18 01:35:51 hostname avahi-daemon[2583]: Found user 'avahi' (UID 84) and group 'avahi' (GID 84).
Mär 18 01:35:51 hostname avahi-daemon[2583]: Successfully dropped root privileges.
Mär 18 01:35:51 hostname avahi-daemon[2583]: avahi-daemon 0.6.31 starting up.
Mär 18 01:35:51 hostname avahi-daemon[2583]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Mär 18 01:35:51 hostname dbus[434]: [system] Successfully activated service 'org.freedesktop.Avahi'
Mär 18 01:35:51 hostname systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Mär 18 01:35:51 hostname avahi-daemon[2583]: Successfully called chroot().
Mär 18 01:35:51 hostname avahi-daemon[2583]: Successfully dropped remaining capabilities.
Mär 18 01:35:51 hostname avahi-daemon[2583]: Loading service file /services/sftp-ssh.service.
Mär 18 01:35:51 hostname avahi-daemon[2583]: Loading service file /services/ssh.service.
Mär 18 01:35:51 hostname avahi-daemon[2583]: Joining mDNS multicast group on interface enp1234.IPv4 with address myip.
Mär 18 01:35:51 hostname avahi-daemon[2583]: New relevant interface enp1234.IPv4 for mDNS.
Mär 18 01:35:51 hostname avahi-daemon[2583]: Network interface enumeration completed.
Mär 18 01:35:51 hostname avahi-daemon[2583]: Registering new address record for myip on enp1234.IPv4.
Mär 18 01:35:51 hostname avahi-daemon[2583]: Registering HINFO record with values 'X86_64'/'LINUX'.
Mär 18 01:35:52 hostname avahi-daemon[2583]: Server startup complete. Host name is hostname.local. Local service cookie is 123.
Mär 18 01:35:53 hostname avahi-daemon[2583]: Service "hostname" (/services/ssh.service) successfully established.
Mär 18 01:35:53 hostname avahi-daemon[2583]: Service "hostname" (/services/sftp-ssh.service) successfully established.

Thanks for your answer.
snakeroot wrote:Are you sure it is actually starting ssh and ssftp or is it just having avahi advertise them as existing?
I'm not sure if anything is started, the term "Service ssh successfully established" sounds like the ssh serrver is started to me, but it might just be strange wording. What does "advertise as existing" mean?
From the snippet you quoted, it looks like the latter. Unless you have alread started socket activation for ssh or sftp, whether via systemd *.socket or inetd, I'm not sure it would actually be started.
I didn't enable anything manually.
I think you can rm/mv the sftp-ssh.service and ssh.service files /etc/avahi/services/ and prevent those services from being advertised.
OK thanks for the hint. Nontheless i would rather stop avahi from starting than configuring it.
Begin rant...
I'm a bit annoyed that avahi is starting without my permission. Seems like systemd is getting a bit overzealous with starting services. Interestingly this was one of the big problems with upstart, and was supposed to be solved with systemd. I still like systemd.

Nemo and Nautilus crashing on accessing Samba shares

Hi,
I've made a clean install on a new laptop, and I've installed the cinnamon desktop environment. I've installed the following versions of these packages in order to get samba to work with nautilus:
Name : smbclient
Version : 3.6.12-1o
Name : gvfs-smb
Version : 1.14.2-3
Name : nautilus
Version : 3.6.3-1
Name : gnome-vfs
Version : 2.24.4-6
However, I get a segmentation fault every time I try to access any samba share or just by simply typing smb:// into the address bar.
Using the gnome-control-center printer setup also causes a segfault. Here is the dmesg output:
[ 748.193864] nautilus[3051]: segfault at 0 ip 00000000004c 1a89 sp 00007fff15bf8440 error 4 in nautilus[400000+14c000]
Can anyone help?
I'm unable to find any specific help on the forum for this particular problem
Thanks!
Last edited by shawntan (2013-02-01 09:12:44)

I've been trying to isolate the problem, and I think it has to do with gvfs-smb.
I am able to access shares via smbclient, and I even tried installing KDE's dolphin, which worked flawlessly as well.
I'll see what happens if I use an older version of gvfs-smb.

Leopard and Samba Shares

Hi,
I have a Samba-Server (3.0.28a) on a Linux machine running with shares for
Windows- and Mac-Users.
All new files and directories that was saved on the
server have the right permissions during the
configuration file smb.conf and the parameters
"create mask" and "directory mask".
Since the update to Leopard for the Mac, the permissions
will be ignored. Every file copied from the Mac to the
server have the permission 0644 and directories 0755
independet of "create mask = 0640" and "directory mask = 0750"
of the smb.conf configuration. The permissions of files,
copied with Windows to the Samba server are good.
Tests with the parameters like "force create mode" and
"force directory mode" have no success. The user permissions
are the same and doesn't changed.
1. Is there a bug in Mac OS 10.5.2 (Leopard) to work with Samba shares,
or a problem with ACLs? Because Tiger doesn't use ACLs (i think so) and all was fine, but in the Samba configuration ACL support is switched on.
Sometimes the finder (Leopard) doesn't show directories and files on shares, after a reboot of the Mac the objects are available again!? For me it's look
like an inconsistent performance.
2. Or is there a change in the permission technology
by Leopard, where is a different handling in Samba necessary?
Thank you and
best regards
oelauge

There is a change in Samba and the Leopard SMB client that can have adverse affects on how ACLs are interpreted. Filesystem ACLs have been supported starting in Mac OS X 10.4, so that hasn't changed directly in 10.5.
But this problem would be a server-side problem on your Linux box. Here's why:
Whenever files are copied, Mac OS X uses the following protocol: the POSIX permission bits of the copy are always retained. In other words, if the original file is 0755, then the copy will be 0755; however, the POSIX owner will be changed to the currently connected user. (Currently-connected can mean the user who logged in for cases where no permission masking applies. These cases will be limited to situations where the server and client are part of a common directory domain, such as Active Directory or Open Directory. For all other situations, masked permissions apply, and the currently logged-in user receives the permissions assigned to the user who connected to the share point.) Typically, the POSIX group is changed to match the group of the destination container (the folder that will hold the copy).
So, let's say Joey copies this file (to which Joey can only read):
SomeFile.txt
POSIX owner: Sally
POSIX group: SallyandFriends
POSIX permissions: 0644
...to this folder on the SMB server where Joey connected as snoopy, and snoopy is a member of peanuts...
ServerFolder
POSIX owner: linus
POSIX group: peanuts
POSIX permissions: 0777
...thus, Joey's copy should look like this:
SomeFile.txt - copy
POSIX owner: snoopy (because Joey connected to the server as snoopy - these are masked permissions)
POSIX group: peanuts (inherited from the parent)
POSIX permissions: 0755 (preserved)
The create and directory masks are for newly-created files and folders on the server, but not copied files or folders!
The real solution here would be to enable ACLs on your Linux server volume.
--Gerrit

Samba share shows up only after I restart samba

I've been setting up a laptop with Arch to use at work and home. The problem is I can not see my samba share until I restart the samba service. The server is available though. I can connect with \\IPADDRESS\SHARE. It's just not listed under Network Places or smbtree.
I have samba under DAEMONS in rc.conf and I've tried starting it in rc.local too. But even if I leave it out of those and start samba manually, I have to restart samba before the share will show up on any client.
The clients are Arch, Windows, and Ubuntu and the share is not available any of them. And the problem happens when I'm at work or at home. I've been googling, but I can't find much about a share being available but not being listed.
My /etc/samba/smb.conf:
#======================= Global Settings =====================================
[global]
# workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
workgroup = MYWORKGOUP
# server string is the equivalent of the NT Description field
server string = Work Files
# 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.0. 192.168.1. 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
# Allow Symlinks (Needed this option after 3.4.6 due to security issues)
unix extensions = no
#============================ 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
wins support = no
;[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
[mike]
comment = Work Files
path = /home/MYUSER/.samba_share
valid users = MYUSER
available = yes
browsable = yes
public = yes
writable = yes
# Needed this option after 3.4.6 due to security issues
wide links = yes

I removed the . (and moved the directory to match) but I still have the same issue.
Here's the smbd.log after a rebooting and then restarting samba:
[2010/05/04 07:25:41.262266, 0] smbd/server.c:500(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
[2010/05/04 07:25:41.266578, 0] smbd/server.c:500(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
[2010/05/04 07:26:01.041577, 1] smbd/server.c:267(remove_child_pid)
Scheduled cleanup of brl and lock database after unclean shutdown
[2010/05/04 07:26:21.051370, 1] smbd/server.c:240(cleanup_timeout_fn)
Cleaning up brl and lock database after unclean shutdown
[2010/05/04 07:26:45.716653, 1] smbd/server.c:267(remove_child_pid)
Scheduled cleanup of brl and lock database after unclean shutdown
[2010/05/04 07:36:46.016675, 0] smbd/server.c:500(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
[2010/05/04 07:36:46.017386, 0] smbd/server.c:500(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Address already in use
And log.nmbd:
[2010/05/04 07:25:41, 0] nmbd/nmbd.c:857(main)
nmbd version 3.5.2 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2010/05/04 07:26:48.718046, 0] nmbd/nmbd.c:71(terminate)
Got SIGTERM: going down...
[2010/05/04 07:27:26, 0] nmbd/nmbd.c:857(main)
nmbd version 3.5.2 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
[2010/05/04 07:27:26.544934, 0] nmbd/nmbd.c:696(open_sockets)
[2010/05/04 07:36:46, 0] nmbd/nmbd.c:857(main)
nmbd version 3.5.2 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010

[Solved] Help Setting Samba Share In Qemu With XP Guest

Hello all,
After getting around all the quirks of setting an XP guest inside qemu, the only (though, pretty important) thing I can't solve is setting a samba share between the Arch host and the XP guest.
I tried whatever I could think of that's relevant, with no success:
Qemu is launched with:
qemu-system-x86_64 -machine type=pc,accel=kvm -cpu host -boot d -m 1024 -net user,smb={my home folder} -net nic,model=virtio -rtc base=localtime -drive file=XP.qcow2,if=virtio -spice port=5900,disable-ticketing,image-compression=off,jpeg-wan-compression=never,zlib-glz-wan-compression=never,playback-compression=off -vga qxl -global qxl-vga.vram_size=67108864 -device virtio-serial-pci -device virtserialport,chardev=spicechannel0,name=com.redhat.spice.0 -chardev spicevmc,id=spicechannel0,name=vdagent -balloon virtio
I installed samba, added a user, and started the service according to the wiki.
I allowed the samba ports in UFW (using the CIFS rule).
Whenever I try accessing the share inside my XP guest (\\10.0.2.4\qemu), I usually end up with a target not found error, or at times, a password prompt that will not accept the samba user/password.
Anything else I forgot to do?
Thanks, Adam.
* EDIT *
I somehow missed the section regarding the guest OS able to access the host OS normal samba shares at 10.0.2.2.
Default samba share for home folder works as expected.
Last edited by adam777 (2013-07-15 16:05:44)

Thanks.
I tried toying with the options a bit more, with no success.
I then decided to try Spice+QXL anyway, and am very happy with it.
Aside from the lengthy compilation of the Qemu version that supports Spice from the AUR, once I got it set up, installing the guest was a breeze.
Using the Spice guest tools for windows, everything was set up very conveniently (virtio for network, hdd, qxl driver, mouse integration etc.).
Responsiveness is much better comparing to previous attempts with "vga std", "vga cirrus" and normal adapter.
Bottom line, I'm sticking with Spice+QXL, seems to work best for me.

AutoFS + Samba share problems when share not online (especially in itunes)

I'm trying to look into having some or all of my media on a server for a couple of my macs, the main one of interest right now being a mac mini working as a HTPC under a tv, being operated 99% of the time with just the apple remote and frontrow.
A friend informed me that if you have your itunes library not managed and add files from a remote share then everything works pretty well. Namely if you try to play a file it will seemingly automount the remote file and start it playing. If the remote server is not available it will quickly discover this and after a short pause start giving explanation marks next to the broken tracks. Get the remote destination connected and then try to play a broken track and it will successfully mount the track and play.
Basically perfect.
I quickly tried accessing these files via a symbolic link or alias to them on the remote drive, in doing this i can be somewhat insulated from problems of trying to move the library to other machines/shares in the future. This all works fine but you do lose the ability for itunes to automatically mount the remote drive, which is a bit of a step back, but not a big deal on my normal machine. On my HTPC machine however i'd really like front row to be able to just work, hence automatically mounting the server as required.
The only problem was that when i tried with files directly added to the itunes library from a remote location frontrow would NOT automount the tracks/videos when you attempted to play them like itunes would do.
I've just spent the last few hours following the advice here
http://rajeev.name/blog/2007/11/22/autofs-goodness-in-apples-leopard-105-part-i/
to setup autofs in the hope that this would let me get auto mounting working as it does with itunes and directly added to the library remote files.
I boiled this down to the following settings
as root
vi /etc/auto_master
and add
/smb auto_smb
then create this new config file
vi /etc/auto_smb
and add
<Mount dir under /smb folder> -fstype=smbfs ://<share user>:<share pass>@<ip address>/<share point>
ie.
testMount -fstype=smbfs ://netuser:[email protected]/remoteMount
finally tell automount to throw away its cache
automount -vc
then the mount should be setup
df -h
shows the indirect map waiting
map auto_smb 0Bi 0Bi 0Bi 100% /smb
and by triggering it
ls /smb/testMount
you should connect and get a listing, a subsequent df shows
df -h
//[email protected]/Media 466Gi 325Gi 141Gi 70% /smb/Media
Everything worked well with the share getting mounted nicely when present, frontrow could just start playing the files it needed, perfect!!
The problem came when i wanted to simulate the media server being offline, basically frontrow, a lot of the system including finder, cd commands attempting to access the share, and itunes if you tried that would all freeze for long periods of time as they tried their best to get the files they were looking for.
I tried looking into getting this to gracefully time out and think i got somewhere by trying to setup the samba share to be soft linked.. I wasn't sure in what files i could add this to, first attempts didn't seem to do anything but adding this seemed to make a difference
/etc/nsmb.conf
containing something like
#Configuration file for example.com
[default]
minauth=ntlmv2
streams=yes
soft=yes
to turn soft samba shares on. Things like cd in a terminal seemed to behave quite well with this, when no remote share present you would get empty folders and the like. Finder would also seem to be reasonable with it.
Frustratingly itunes and frontrow both still have quite massive pauses even when finder and cds in the background show that perhaps the soft links are working and failing like they should.
I'm now left wondering what i can do to fix it, and resorting to perhaps having the files added via a symbolic link, using the login items to launch the remote share every boot and then having it so that all i need to do is reboot the HTPC mac mini if the server is on for it to pick it up and let me play the files. Otherwise they'll just be unavailable and will fail gracefully without locking up itunes. The perfect solution would be to either have a crontab running, or some applescript bound somehow to whenever frontrow is ran which manually tries to tell finder to do the equivelant mount the login items setup does.
It's frustrating though as its so close, and the autofs solution if it did work better would seem to be the perfect solution. Has anyone dabbled with this and got any suggestions as to options you can setup to make things not go horribly wrong when a remote share is NOT present, preferrably within the context of itunes or front row not complaining, but to be honest any suggestions i'll be able to try out myself.
Sorry i've written so much, perhaps some of it will be helpful reference as it took me a while to decipher that link at the top into just setting up a samba autofs.
Cheers.

It seems like it's not only the ArchLinux workstation that displays the norwegian letters wrong. The only machine that shows this correc is the machine that created the file/catalogue.
It seems like the windows 2000 displays the cataloge created by windows XP just fine.

Samba shares no longer visible after migration to systemd

EDIT: Note the file server is CLI only.
I upgraded my file server to systemd about a week ago and have yet to get the Samba share visible from other devices within my network. Eveything worked fine under initscripts and other than system upgrades the only thing that has changed about the system is the migration to systemd and addition of the netcfg package. I can connect manually by typing "smb://<IP>" in a file manager address field but when trying to access the Share via browsing on two different WD media players, a Xoom tablet, typing "smb://" in the address bar of a basic file manager like Thunar or PCManFM or using browsing the Network or Samba Shares links in the Network place from Dolphin the share just doesn't show up.
The fact that I can access the Share directly, it's just not visible when browsing, makes me think samba is working properly but I'm not sure how to further diagnose the issue and I'd really like to solve the problem and learn something rather than just load up a previous image of the PC before the systemd migration.
Commands from client
my /etc/hosts...
cat /etc/hosts
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost dads-pc
192.168.10.131 dads-pc.HOMESERVER dads-pc
192.168.10.100 Serverbox.HOMESERVER Serverbox
Master Browser search, this does look odd, I don't use it on any machine so where the heck did the .255 at the end of the IP address come from?
$ nmblookup -M HOMESERVER
querying HOMESERVER on 192.168.10.255
name_query failed to find name HOMESERVER#1d
I can sign in fine...
$ smbclient -L Serverbox
Enter dad's password:
Failed to load upcase.dat, will use lame ASCII-only case sensitivity rules
Failed to load lowcase.dat, will use lame ASCII-only case sensitivity rules
Domain=[HOMESERVER] OS=[Unix] Server=[Samba 3.6.9]
Sharename Type Comment
IPC$ IPC IPC Service (Samba Server)
Server Disk The Family Network Share Files
ParentalMovies Disk Movie folders for Mom and Dad
Movies Disk Family Movie folders
Domain=[HOMESERVER] OS=[Unix] Server=[Samba 3.6.9]
Server Comment
SERVERBOX Samba Server
Workgroup Master
HOMESERVER SERVERBOX
I can sign in as one of the media players fine...
$ smbclient -L Serverbox -U lr_mediaplayer
Enter lr_mediaplayer's password:
Failed to load upcase.dat, will use lame ASCII-only case sensitivity rules
Failed to load lowcase.dat, will use lame ASCII-only case sensitivity rules
Domain=[HOMESERVER] OS=[Unix] Server=[Samba 3.6.9]
Sharename Type Comment
IPC$ IPC IPC Service (Samba Server)
Server Disk The Family Network Share Files
ParentalMovies Disk Movie folders for Mom and Dad
Movies Disk Family Movie folders
Domain=[HOMESERVER] OS=[Unix] Server=[Samba 3.6.9]
Server Comment
SERVERBOX Samba Server
Workgroup Master
HOMESERVER SERVERBOX
Commands from Server
Both smbd and nmbd services appear functional...
$ systemctl status smbd nmbd
smbd.service - Samba SMB/CIFS server
Loaded: loaded (/etc/systemd/system/smbd.service; enabled)
Active: active (running) since Mon, 2012-11-19 17:48:07 CST; 2h 9min ago
Main PID: 534 (smbd)
CGroup: name=systemd:/system/smbd.service
├ 534 /usr/sbin/smbd -F
├ 551 /usr/sbin/smbd -F
└ 559 /usr/sbin/smbd -F
nmbd.service - Samba NetBIOS name server
Loaded: loaded (/etc/systemd/system/nmbd.service; enabled)
Active: active (running) since Mon, 2012-11-19 17:48:07 CST; 2h 9min ago
Main PID: 536 (nmbd)
CGroup: name=systemd:/system/nmbd.service
└ 536 /usr/sbin/nmbd -F
The global portion of my /etc/samba/smb.conf file...
[global]
workgroup = HOMESERVER
server string = Samba Server
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = No
valid users = dad, lisa, administrator,lr_mediaplayer, xoom, br_mediaplayer
read list = dad, lisa, administrator, lr_mediaplayer, xoom, br_mediaplayer
write list = dad, lisa, administrator
load printers = no
write cache size = 262144
large readwrite = yes
# These next lines have been added after systemd conversion based on web research, none of which has helped.
log level = 10
name resolve order = host bcast lmhosts wins
interfaces = eth0 192.168.10.100/19
preferred master = yes
Testing of the /etc/samba/smb.conf file, no errors ...
$ testparm smb.conf
Load smb config files from smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[Movies]"
Processing section "[ParentalMovies]"
Processing section "[Server]"
Loaded services file OK.
WARNING: You have some share names that are longer than 12 characters.
These may not be accessible to some older clients.
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)
Server role: ROLE_STANDALONE
My network config file for [email protected]...
$ cat /etc/network.d/eth0
CONNECTION='ethernet'
DESCRIPTION='A basic static ethernet connection using iproute'
INTERFACE='eth0'
IP='static'
ADDR='192.168.10.100'
#ROUTES=('192.168.0.0/24 via 192.168.1.2')
GATEWAY='192.168.10.1'
DNS=('76.85.229.110' '76.85.229.111')
Master Browser search and again with the rogue .255 ending for the IP address being broadcast.
$ nmblookup -M HOMESERVER
INFO: Current debug levels:
all: 10
tdb: 10
printdrivers: 10
lanman: 10
smb: 10
rpc_parse: 10
rpc_srv: 10
rpc_cli: 10
passdb: 10
sam: 10
auth: 10
winbind: 10
vfs: 10
idmap: 10
quota: 10
acls: 10
locking: 10
msdfs: 10
dmapi: 10
registry: 10
doing parameter name resolve order = host bcast lmhosts wins
doing parameter log file = /var/log/samba/%m.log
doing parameter max log size = 50
doing parameter dns proxy = No
doing parameter valid users = dad, lisa, administrator,lr_mediaplayer, xoom, br_mediaplayer
doing parameter read list = dad, lisa, administrator, lr_mediaplayer, xoom, br_mediaplayer
doing parameter write list = dad, lisa, administrator
doing parameter load printers = no
doing parameter write cache size = 262144
doing parameter large readwrite = yes
doing parameter preferred master = yes
pm_process() returned Yes
lp_servicenumber: couldn't find homes
set_server_role: role = ROLE_STANDALONE
Substituting charset 'UTF-8' for LOCALE
added interface eth0 ip=fe80::3285:a9ff:fe8e:90f7%eth0 bcast=fe80::ffff:ffff:ffff:ffff%eth0 netmask=ffff:ffff:ffff:ffff::
added interface eth0 ip=192.168.10.100 bcast=192.168.10.255 netmask=255.255.255.0
bind succeeded on port 0
Socket options:
SO_KEEPALIVE = 0
SO_REUSEADDR = 1
SO_BROADCAST = 1
Could not test socket option TCP_NODELAY.
Could not test socket option TCP_KEEPCNT.
Could not test socket option TCP_KEEPIDLE.
Could not test socket option TCP_KEEPINTVL.
IPTOS_LOWDELAY = 0
IPTOS_THROUGHPUT = 0
SO_SNDBUF = 212992
SO_RCVBUF = 212992
SO_SNDLOWAT = 1
SO_RCVLOWAT = 1
SO_SNDTIMEO = 0
SO_RCVTIMEO = 0
Could not test socket option TCP_QUICKACK.
Socket opened.
lang_tdb_init: /usr/lib/samba/en_US.UTF-8.msg: No such file or directory
querying HOMESERVER on 192.168.10.255
bind succeeded on port 0
Socket options:
SO_KEEPALIVE = 0
SO_REUSEADDR = 1
SO_BROADCAST = 1
Could not test socket option TCP_NODELAY.
Could not test socket option TCP_KEEPCNT.
Could not test socket option TCP_KEEPIDLE.
Could not test socket option TCP_KEEPINTVL.
IPTOS_LOWDELAY = 0
IPTOS_THROUGHPUT = 0
SO_SNDBUF = 212992
SO_RCVBUF = 212992
SO_SNDLOWAT = 1
SO_RCVLOWAT = 1
SO_SNDTIMEO = 0
SO_RCVTIMEO = 0
Could not test socket option TCP_QUICKACK.
parse_nmb: packet id = 9235
nmb packet from 192.168.10.100(35072) header: id=9235 opcode=Query(0) response=Yes
header: flags: bcast=No rec_avail=Yes rec_des=Yes trunc=No auth=Yes
header: rcode=0 qdcount=0 ancount=1 nscount=0 arcount=0
answers: nmb_name=HOMESERVER<1d> rr_type=32 rr_class=1 ttl=259200
answers 0 char .....d hex 0000C0A80A64
Got a positive name query response from 192.168.10.100 ( 192.168.10.100 )
192.168.10.100 HOMESERVER<1d>
Thank you.
Last edited by imatechguy (2012-11-20 03:16:39)

ChojinDSL wrote:Do you have a firewall running on that server?
Are your clients also using systemd?
Yes I do have a firewall, iptables, and it's the same configuration from before the migration to systemd. Also note that I can access the shares when explicitly defining the path whether that's in a File Manager, cli or other so access isn't being blocked. For lack of a better explanation the whole thing gives the appearance that although the Share is active it's just not broadcasting it's existence like it should be.
I have two PC's, both Arch, one with Openbox and one running KDE that I have migrated to systemd. Both can access the Share when the path is explicitly defined but don't see it when trying to just browse for the the Share. I have a Xoom tablet, running Android Jelly Bean, that exhibits the same behavior. I also have two media players, one an older WD LiveTV Plus model the other a newer WD LiveTV model, neither of which can see the share and browsing is the only option for those devices. So I've got a pretty good assortment of devices and operating systems that could see the share when browsing previously but can not see the same share by browsing since the migration to systemd on the file server.
Thank you.

Samba Shares and System Lockup

Similar Messages

Maybe you are looking for