Finder hangs up on Samba Shares

Hello guys,
I could nearly freak out.
I have installed SuSE as a VM for web development purposes. There is a Samba Server running on this VM. I could easily connect and edit files back on Mavericks. But right after the update to OS X Yosemite it's been the **** on earth.
Whenever I connect and try to edit files, Finder just starts hanging and the connection gets lost again. Finder hangs for about 2 min.
Does anyone know how to solve this?
Any help appreciated

"Try connecting to the drive with CIFS:\ instead of SMB:\. I have had the same issue and when trying it with the CIFS protocol it worked."
http://apple.stackexchange.com/questions/151345/vpn-client-is-not-working-after- yosemite-update-enforce-firewall-policy-…

Similar Messages

Finder hang after file delete NTFS Samba share after 10.6.7

I have Finder problem!
Before 10.6.7, I had no issue with a Samba share on win2008 server, I have full admin rights for the files.
Now, I can move the files, change the Directory they are into another, rename them, basically I can do what ever I want with them, except deleting them.
As soon as I try to delete a file or folder, Finder hangs, And I can't stop the process, killing the network connection does nothing, trying to unmount it wont work either.
Any clues? Suggestions?

I have tightened up to the problem to the ds_store invisible files.
If the folder that has a ds_store file in it and you trash it, it freezes up the mac. (For some reason not most files)
But after the freeze, the folder permissions get corrupted (or changed maybe not sure) then trashing doesn't work again.
But if you view the invisible ds store files and delete it you can trash the folder.
[email protected] let me know

Finder lock ups due to samba shares being invalidated by changing network

I often leave my macbook online for a long time unattended, for simplicity I tend to plug it into its power lead, and also connect it up to my gigabit network. I know i've set the priority in my connections to prefer the wired connection over wireless but just to keep things simple i disable airport so i can be sure that i will be connected via gigabit.
I'll then go in and map a network drive from one of my PCs on the lan, this is mounted and available.
Sometime in the future i'll go mobile again, like i just did today. Disconnecting power and gigabit ethernet, i re-enable airport. After a short while its all good to go.. I then start using the internet connection. All is fine.
Then finally i spot that my samba drive is still mapped, i've had trouble selecting this drive to use it, but sadly also you get real trouble by just trying to eject the mount. Doing so and nothing happens.. after 10-20 seconds everything is frozen, including the animated dock, and top toolbar, and you are presented with the spinning wheel of activity.
applealtesc does NOT bring up the force close dialog, and eventually i was forced to force a shutdown.. apple power button isn't it? I had the power button held down for a long time.
Generally i find the mounting samba drives a bit of a pain in the finder but i can put up with it. Samba shares on windows are a nightmare but they rarely bring down the whole system when a connection has been broken.. i'd love it if mac OS would time out the samba share and just give up, rather than hanging in the way it does do.
Obviously i'm accessing my LAN through a different interface and IP address than i was when i set up the connection. I am not sure if you have a similar problem as described if you just disconnect from the network and have no net connection at all.. not sure what it would do with a share in this way.
Is this worth logging as an actual bug? anyone got any suggestions to fix it?

Ok, no luck yet. Maybe I can ask another question directly related to this issue. I am trying to find the cause of this and I am wondering if there is a brief dropout in the connection to the NAS. By brief, I mean really brief. The NAS is connected via a Homeplug network connection (network via the homes power points) and maybe for a very brief period interferrence on the lines dropped the AFP connection.
Is it normal that it is then impossible for AFP to reconnect, even when the NAS is clearly back on the network?
Any drop will have to be very brief as I can always stream music without issues, and no drop or slow down has caused buffering issues.
But, I don't recall getting this issue when directly connected to the iMac via a short ethernet cable for the initial Time Machine backups that take over a day.
What I don't understand though, is if the connection did briefly drop and loose the AFP link, why can AFP no longer connect back? Why do I need to sleep the iMac and then wake it again.
HTTP connections to the NAS never seem to drop, and when I can't recconnect via AFP, I can always connect via HTTP? Is this expected of the AFP protocol? Or is it an unexpected issue?

Yosemite 10.10.1: Finder/CIFS mount problem: wrong folder count/folders not shown @samba shares

Hello to all,
we have several MacBook Pro (15" MBP Retina 2012/13"MBP Retina 2014) running. After upgrading to Yosemite 10.10.1 we had one nightmare after the other.
Most problems could be solved with 3rd party software upgrades but there are several problems with the operating system itselve which can not really be called a professional productive system at the moment...
Ok., one thing after the other...here is one of our biggest problems:
After upgrading from Mavericks or Mountain Lion to Yosemite 10.10.1 the CIFS/SMB mounts to our samba 3.x servers, running on Ubuntu Linux LTS 12.04 makes trouble. We could mount the server shares but after browsing with the Finder the beach ball occures and the Finder hangs forever. Sometimes we could not refresh the Finder, killing the process ended in a complete hang-up of the system which ended in a switch off death blow. This is not amusing because we have 30Tb of customer data there, which has to be worked out.
We heard about the SMB3 protocol which will be used per default in Yosemite and so we decided after some testings to upgrate our Ubuntu servers to the latest LSF 14.04. release with samba 4.1.6 installed. There was no message from Apple for this SMB protocol release upgrade, never heard something related to Yosemite (Why?).
Ok, after these server upgrades and disabling most of the Spotlight functions the performance to the CIFS shares was a little bit better as before but now we have another problem with the Finder...if you browse to the shares there are folders missing which have lots of files in it. For example there is a folder with 60 subfolders and 3562 files on the first level in it, the Finder shows 220 files and 15 folders. The Terminal shows a different count with "find . -maxdepth 1 -type d | wc -l" or "find . -maxdepth 1 -type f | wc -l" but there is also a difference to the original file and folder count. It doesn`t matter if the clients are connected via WiFi or Gigabit Ethernet. We have no access problems. We have the same behavior if we set the files and folders to 0777 permissions on the servers. The deletion of the preferences files of the users on the MacBooks does not solve the problem. If we use the "Go To Folder" option and type the path to a folder which is not shown in the Finder you get an result or not. But it is also possible that the result is not correct and there are also still files or subfolders missing.
In my opinion this is a timeout problem and a "special SMB3 protocol interpretation" which is buggy. We have one hint found in /var/log/system.log:
"Jan 23 14:35:49 wsosx33.clients.getcom.de KernelEventAgent[69]: tid 54485244 type 'smbfs', mounted on '/Volumes/customersdata2015', from '//x144067:@srvlxp013.servers.getcom.de/customersdata2015', not responding"
We had no problems with Mavericks at all, we still have no problems with Windows 7 Pro/Ultimate, Windows 2008R2 (native or virtual) or Linux Mint 17/17.1 clients, neither with samba 3.x nor with our actual environment and different newer samba releases.
We believe that this is a big bug in Yosemite, but we cannot go back to Mavericks because of incompatible TimeCapsule backups. Our workarround at the moment is that we have installed Linux Mint on our MacBooks to get 80% of our daily jobs done, rest has to be done with Windows 7 installed over virtualbox @Linux.
We have no clue at the moment how to solve this problem, the samba logs do not give any hint. The access from other operating systems is perfect and very fast, but not with Yosemite. We checked different tips found in the internet but nothing helped.
Does anybody has another idea to get Yosemite working or should we keep Linux Mint until Apple will provide a CIFS/SMB patch and going on with our workaround solution, which is productive at the moment ??? Our staff is not amused and wants one solution and not this workaround with two operating system. We have to decide wether we wait until Apple will get this fixed or we have to switch to Microsoft Windows (which is a No Go for me, but I will not be asked...).
Thanks in advance
C.

Hi William,
thank you for your response.
As you can read in my post I talked about CIFS/SMB.
It makes no difference if we mount the share over CIFS or SMB.
Folders with lots of files will not be shown even if we use SMB3 or an older protocol.
As mentioned I believe this is a timeout problem.
Does anybody know how the CIFS/SMB timeout setting in Yosemite could be changed?
Kind regards
C.

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.

Automount: system hang on not available shares -- solution, alternatives?

hello,
i'm using snow leopard 10.6.5 on my macbook pro 13.3 with automount. my automount-entry looks like this (/etc/auto_master):
/Users/abc/backup -fstype=smbfs ://abc:[email protected]/SHARE
Works very well. I am connected to the network by wlan.
Now I disable wlan (or switch my location to somewhere the share is not available). Once a programm (e.g. finder) tries to access the mount location, it hangs for ever. It should simply error out with something like "path not available" after e.g. 5 seconds and give up to try to connect (until the next access of the folder).
So how can i have samba shares available when the network is up and no hang when the network is down? Is there any tool? I assume with "automount" it is not possible...?
Regards,
Markus
Message was edited by: cpo_123

simple shell script is the solution for different wlan.
#!/bin/bash
while true; do
current_wlan="$(/System/Library/PrivateFrameworks/Apple80211.framework/Versions /Current/Resources/airport -I | grep " SSID" | sed 's/.*SSID: //' | sed 's/ /__/g')";
if [ -f "/etc/auto_mount/$current_wlan" ]; then
if [ "$(readlink /etc/auto_lnk)" != "/etc/auto_mount/$current_wlan" ]; then
rm /etc/auto_lnk;
ln -s /etc/auto_mount/$current_wlan /etc/auto_lnk
automount -c
fi;
else
if [ -e "/etc/auto_lnk" ]; then
rm /etc/auto_lnk;
automount -c
fi;
fi;
sleep 15;
done;
Simply run as root. Add /etc/auto_lnk to /etc/auto_master and put a file with auto_master-syntax in /etc/auto_mount/WIFINAME.

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

How do I add myself to the "staff" group for a samba share?

Hi all,
I've been struggling with this for a few hours now. I searched but could not find the answer (neither here nor google).
I am trying to set up a samba share on my raspberry pi and have it accessible by all other computer on my local network (just a home network). I want it set up so that when I access the share via my linux desktop I have read/write privileges, but when other users (my family, variety of linux and windows machines) access it they have read-only access and do not have to enter a password. I am not sharing any printers. The raspberry pi and my desktop are both running arch.
I am currently able to mount the share, but I only have read-only access. In the smb.conf file it has a pre-configured section for A publicly accessible directory, but read only, except for people in the "staff" group, which is the section I have tried to use. My user name on my desktop is 'gav', and I have created a user with the same name on the pi. On both the pi and the desktop I have added 'gav' to the staff group (using groupadd and usermod -aG).
On Windows machines: a Windows 7 desktop found the share and prompted for a password, I entered my password (as 'gav') and could access files, but read-only. A windows 8 laptop couldn't see it at all.
Here are some outputs of some things:
testparm (on the pi)
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
params.c:Parameter() - Ignoring badly formed line in configuration file: i
Processing section "[sharedfiles]"
Loaded services file OK.
Server role: ROLE_STANDALONE
[global]
workgroup = PISERVER
server string = Shared Media
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = No
idmap config * : backend = tdb
[sharedfiles]
comment = Proper share
path = /mnt/sambashare
write list = @staff
guest ok = Yes
I'm not sure which is the 'badly formed line', any idea how I find out?
smbtree (on desktop)
WORKGROUP
PISERVER
\\PI Shared Media
\\PI\sharedfiles Proper share
\\PI\IPC$ IPC Service (Shared Media)
ASUSROUTER
smbclient -L PI -U% (on desktop)
Domain=[PISERVER] OS=[Unix] Server=[Samba 4.1.0]
Sharename Type Comment
IPC$ IPC IPC Service (Shared Media)
sharedfiles Disk Proper share
Domain=[PISERVER] OS=[Unix] Server=[Samba 4.1.0]
Server Comment
PI Shared Media
Workgroup Master
ASUSROUTER DSL-N55U
PISERVER PI
WORKGROUP SHODAN
command I entered to mount share (as root)
mount -t cifs //PI/sharedfiles /media/pi -o user=gav,password=pass,workgroup=PISERVER,ip=192.168.1.199
Any help would be appreciated, please let me know if there are any more outputs I can provide.
Thank you for reading
Last edited by gav989 (2013-11-10 13:34:46)

Consider using sshfs to mount your Pi from your Linux boxes. It's much easier to configure and manage than samba. It sounds like you already have your Windows machines mounting your Pi so Samba is doing its job in that respect.
More info on sshfs in the Wiki: https://wiki.archlinux.org/index.php/Sshfs
To help get you off the dime, here's a modified line from my fstab that I use to mount my Pi with:
gav@PI:/mnt/backup /mnt/rpi/backup fuse.sshfs rw,relatime,user_id=0,group_id=0,allow_other 0 0
Subsitute my mount points with yours.
For a password-less mount:
ssh-copy-id gav@PI
after you've set up ssh and generated some keys on your client box.
Here are some relevant lines from the smb.conf file on my Pi that I use for my one Windows box in the house that might help you with your write permissions:
security = user
hosts allow = 192.168.1.0/255.255.255.0
guest account = gav
; And my share setup:
[rpi]
comment = Public Stuff
path = /mnt
writable = yes
; printable = no
; write list = @krb
[torrent_dl]
path = /mnt/video/torrent_dl
writable = yes
create mask = 0770
directory mask = 0770
guest ok = Yes
case sensitive = No
read only = No
Hope this helps.

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.

[solved] Can't connect to samba shares

This is probably my fault, but for the life of me I can't figure this out. I started out trying to get usershares to work by following the wiki at https://wiki.archlinux.org/index.php/samba, and I am unable to connect to the resulting shares either from the local host or from my netbook. It tells me permission denied. I then tried creating a public share with guest access, because I couldn't get the usershares to work. I am unable to get that working either. I have
chmod 777 -R
the folder I am sharing, as well as the
/var/lib/samba/usershare
folder. Please help. Here is my smb.conf:
#======================= Global Settings =====================================
[global]
workgroup = OSHANNON
server string = MDSHANNJARO
hosts allow = 192.168.1. 127.
log file = /var/log/samba/%m.log
max log size = 50
security = user
map to guest = Bad User
guest account = nobody
dns proxy = no
usershare path = /var/lib/samba/usershare
usershare max shares = 100
usershare allow guests = Yes
usershare owner only = False
#============================ Share Definitions ==============================
[Bleach]
path = /mnt/Data/Bleach
read only = no
guest ok = yes
I tried adding the nobody user since there was no users listed when running
pdbedit -L
using
pdbedit -a -u nobody
and just pressed enter for the password field. This did not help.
testparm says
Load smb config files from /etc/samba/smb.conf
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)
Processing section "[Bleach]"
Loaded services file OK.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions
[global]
workgroup = OSHANNON
server string = MDSHANNJARO
map to guest = Bad User
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = No
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = No
usershare path = /var/lib/samba/usershare
idmap config * : backend = tdb
hosts allow = 192.168.1., 127.
[Bleach]
path = /mnt/Data/Bleach
read only = No
guest ok = Yes
Last edited by mdshann (2014-03-04 06:01:04)

uninstalled samba, reinstalled it. deleted old config file. created new config with just the contents that the wiki states is necessary for usershares to work. the current smb.conf looks like
[global]
usershare path = /var/lib/samba/usershare
usershare max shares = 100
usershare allow guests = yes
usershare owner only = False
added my user to samba using
pdbedit -a -u mdshann
started smbd and nmbd and enabled both. tried to share a folder, caja says samba is not installed. use yaourt to search for caja and find package mate-file-manager-share. installed said package, killed and restarted caja. shared folder and told it to add permissions automatically. checked the boxes to allow guest and to allow users to change files. still I cannot connect. just for reference, I have used the wiki article sections from the beginning of the article through adding a user. I did not use the creating a share section as I want usershares to work through MATE and CAJA. It creates the share and it is visible on the network, I just can't connect to it.
Pretty much the same as what I tired before, with the same result. Only difference is I haven't tried manually creating the share through smb.conf, but that didn't work before either. No reason to think it will work now, the problem was the same whether I used the gui usershares option or adding the share to smb.conf.
I was able to get samba working with a very similar config file as in my first post, on arch based manjaro on my server at work. I did not enable or use usershares at work, but creating the shares in smb.conf worked just fine. Why will the same procedure not work on arch? Same packages for the most part, manjaro just adds a few. In fact, when I set up samba on manjaro, I used the arch wiki article, as Manjaro's wiki is sparse. Main reason we used manjaro at work was the speed of installation was much quicker, and we needed the machine back up quickly so we could start backing up our customers data. (I own a PC repair shop.)
On a side note, this community has served me well in the past the few times I have have issues since I started using arch 5 years ago. Why my post has gone so long without a reply other than being chastised for trying to call attention to a 3 day old unanswered thread is beyond me, but I am not thrilled by it. It has now been a full 2 weeks since my original post. I have never had this issue before, and if I can't bump or somehow call attention to my thread I am unsure of how to get help. Am I supposed to keep posting new threads on the same issue? I would think those would get closed rather quickly if I had. Should I post nonsense on this thread, I mean anything other than the word bump. A discussion of cat videos maybe?

Best options for migrating Samba shares to DFS

My team is in the process of setting up a new domain for our organization. We want to slowly migrate users from non-AD accounts and workstations to AD (2012). One of the pieces we are having trouble coming to a consensus on is the best method(s) for migrating
the Samba shares from our RHEL server to DFS.
One idea was to join the Samba server to the domain then add the shares into DFS to allow the non-AD users to continue to use the old server and the new users to use the DFS server. As we had time (small team) we would join the individual workstations, have
the users start using their AD credentials, and move their mapped drives to the DFS share. Later, we could add a DFS server for replication and eventually drop the Samba server once everyone was migrated.
Another opinion that we should simply copy the departmental shares across to the DFS server and move whole departments rather than individual users, locking down the old Samba shares as we go.
These are pretty much theoretical at this point as I can't seem to find any documentation on how best to migrate from Samba to DFS. I would appreciate ideas.
Thanks.

Hi,
You could map drives to old server using the DFS server credential:
net use \\DFS server\\share Z: /user:domain\username password
Then run the robocopy command to migrate the shared folder from the old server to the DFS server:
robocopy “\\source server\drive$\folder path” Z:\ /COPYALL /B /SEC /MIR /R:0 /W:0 /LOG:c:\logs\robolog.txt /NFL /NDL
For more detailed information about the robocopy command, you could refer to the artice below:
Robocopy
http://technet.microsoft.com/en-us/library/cc733145.aspx
Best Regards,
Mandy
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

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

Can't browse samba shares after samba upgrade (3.0.26a-4 - 3.0.27A-1)

Hi all,
After today's samba update, i am unable to browse my samba shares:
As seen in pacman.log:
[2007-11-16 15:55] updating smbclient (3.0.26a-2 -> 3.0.27A-1)
[2007-11-16 15:55] updating samba (3.0.26a-4 -> 3.0.27A-1)
Ive had this samba server running for a long time and never had any trouble. Apart from the system update i havent changed anything.
I have tried two machines to access it, a ubuntu and a windows one. The ubuntu one would mount it all right, but when you try browsing it it gives an 'Input/output error', these are the last lines found in /var/log/messages file:
Nov 16 19:42:06 Naboo kernel: [ 855.043000] SMB connection re-established (-5)
Nov 16 19:42:34 Naboo kernel: [ 883.442000] smb_add_request: request [cdccae80, mid=11] timed out!
Nov 16 19:42:34 Naboo kernel: [ 883.442000] smb_proc_readdir_long: error=-5, breaking
Nov 16 19:42:34 Naboo kernel: [ 883.488000] SMB connection re-established (-5)
Nov 16 19:42:36 Naboo kernel: [ 885.375000] smb_add_request: request [cdccac80, mid=18] timed out!
Nov 16 19:42:36 Naboo kernel: [ 885.375000] smb_proc_readdir_long: error=-5, breaking
Nov 16 19:43:04 Naboo kernel: [ 913.607000] smb_add_request: request [cdccae80, mid=21] timed out!
Nov 16 19:43:04 Naboo kernel: [ 913.608000] smb_proc_readdir_long: error=-5, breaking
Nov 16 19:43:05 Naboo kernel: [ 913.648000] SMB connection re-established (-5)
The windows machine would actually show the files in the shared directory but after a very long wait. Browsing and reading files was taking such a long time that windows seemed like frozen so i had to restart.
I also tried rebooting the server but to no avail.
Anyone else with the same problem?
Last edited by feralert (2007-11-16 20:48:31)

Same problem here. I can Browse remote smb filesystem with smbclient but when I mount smbfs i cannot browse folder - my terminal hangs and in syslog i receive
Nov 19 09:35:16 skyscraper SMB connection re-established (-5)
Nov 19 09:35:16 skyscraper smb_proc_readdir_long: error=-512, breaking
Nov 19 09:35:17 skyscraper SMB connection re-established (-5)
Nov 19 09:35:18 skyscraper smb_proc_readdir_long: error=-512, breaking
Nov 19 09:35:18 skyscraper SMB connection re-established (-5)
Nov 19 09:35:27 skyscraper SMB connection re-established (-5)
Nov 19 09:35:48 skyscraper smb_add_request: request [d34f2b00, mid=22] timed out!
Nov 19 09:35:48 skyscraper smb_proc_readdir_long: error=-5, breaking
Nov 19 09:36:18 skyscraper smb_add_request: request [d34f2b00, mid=31] timed out!
Nov 19 09:36:18 skyscraper smb_proc_readdir_long: error=-5, breaking

Leopard unable to send folders to a samba share

We are currently experiencing a problem trying to copy a pro tools project onto one of our servers via a samba share on the server. When we try to copy/move a directory finder reports that it does not have sufficiant privalages to do so.
But when we selected individual files inside the directory tree and copied them, they all went over fine and where able to create directories on the server from the client.
I then used terminal and ls -la to view the contents of the directories and discovered there were a fair few hidden temporary files. All belong to the correct user as far as samba is concerned, but some had the "@", Extended attributes flag attatched. I am able to interrogate them using xattr which shows com.apple.<this part varies> I'm unsure completely what com. files represent, as I am generally a linux user (sorry apple! but hey we're both unixy..)
Does anyone know of a fix, or if this is a common problem? or any way I can stop osx from spuriously creating these hidden files? or am I going to havto script something.. umm.. somewhere.
Oh, the server is running Fedora Linux, and the client is an Imac running OSX Leopard.
Any information would be greatly appreciated!
Stewart
I am having difficulty finding a sollution to this problem.

do you get error -36 or error -50? there are several bugs related to that in snow leopard finder. not sure which one is affecting you. try this link first
http://support.apple.com/kb/HT4017
next, see this post. It could be a problem with split resource forks for hidden .DS_Store files if it only affects folders
http://discussions.apple.com/thread.jspa?messageID=11122044&#11122044
also see this link for yet another bug
http://db.tidbits.com/article/10772

Finder hangs up on Samba Shares

Similar Messages

Maybe you are looking for