Apache access to mounted shares.

I keep trying to encourage my company to use our X Server for all the wonderful web stuff it does. So somebody has to help me please?
I've got Apache, MySql, PHP all up and running, and the application developed mostly. BUT... I need to serve some images that are on a Windows server with a custom application. That server doesn't run any Web server, and I don't even want to go there....
Here is what I tried so far:
1) Connect to the Server with Finder. This "works". I can see the server and browse the files in Finder. Unfortunately, only the user that connects to the windows server has any permissions to the file. I checked with Terminal and LS -l and the permissions are DRWX------. Since Apache on the Server runs as WWW, it doesn't have access to the file. I tried to do a CHMOD 744 on the diretory, but it is basically ignored (no error message, no change).
2) Use mount_smbfs. This lets me mount the Windows server within the Documents directory, and lets me set the permissions so that they are RWXR--R--. But Apache still can't serve the jpg file. The Apache error log says "failed because search permissions are missing on a component of the path".
Any suggestions on what I am doing wrong? XSERVE 10.4.6
Thanks...

Well, I have a very uggly work around that I will document, but not recommend. It is pretty resource intensive, and not particularly secure, but it works for our limited environment.
The application was simple enough that if I could copy the files I needed to a local drive, then things would work.
PHP can execute a system command, and that command runs as WWW (the Apache id), so what I ended up doing was checking to see if the file I needed was already on the local system (in a directory that WWW can access). If the file was not already there, then I would exec('smb_client....). Since you can include a command on the smb_client command line, I just included a command to copy the file I was looking for.
This is NOT a recommended solution... it is simply something that works for me..
1) PHP does not encourage running system commands under Apache. If the command hangs, you can hang Apache.
2) Running the client like this uses all the resource to establish the smb connection for each file I needed to copy, then tear it down.
As you can see, if you do this a lot, it could slow things down.
While I was writing this up, it occured to me that another option would be to have PHP see if the share was mounted, and if not, then it could issue the smb_mount command as WWW. I will have to try this next time I get some time on the server for testing.

Similar Messages

Accessing NFS mounted share in Finder no longer works in 10.5.3+

I have setup an automounted NFS share previously with Leopard against a RHEL 5 server at the office. I had to go through a few loops to punch a hole through the appfirewall to get the share accessible in the Finder.
A few months later when I returned to the office after a consultancy stint and upgrades to 10.5.3 and 10.5.4 the NFS mount no longer works. I have investigated it today and I can't get it to run even with the appfirewall disabled.
I've been doing some troubleshooting, and the interaction between the statd, lockd and perhaps the portmap seem a bit fishy, even with the appfirewall disabled. Both the statd and lockd complains that they can not register; lockd once and statd indefinitely.
Jul 2 15:17:10 ySubmarine com.apple.statd[521]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 2 15:17:10 ySubmarine com.apple.launchd[1] (com.apple.statd[521]): Exited with exit code: 1
Jul 2 15:17:10 ySubmarine com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
... and rpcinfo -p gets connection refused unless I start portmap using the launchctl utility.
This may be a bit obscure, and I'm not exactly an expert of NFS, so I wonder if someone else stumbled across this, and can point me in the right direction?
Johan

Sorry for my late response, but I have finally got around to some trial and error. I can mount the share using mount_nfs (but need to use sudo), and it shows up as a mounted disk in the Finder. However, when I start to browse a directory on the share that I can write to, I end up with the lockd and statd failures.
$ mount_nfs -o resvport xxxx:/home /Users/yyyy/xxxx-home
mount_nfs: /Users/yyyy/xxxx-home: Permission denied
$ sudo mount_nfs -o resvport xxxx:/home /Users/yyyy/xxxx-home
Jul 7 10:37:34 zzzz com.apple.statd[253]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 7 10:37:34 zzzz com.apple.launchd[1] (com.apple.statd[253]): Exited with exit code: 1
Jul 7 10:37:34 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
Jul 7 10:37:44 zzzz com.apple.statd[254]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 7 10:37:44 zzzz com.apple.launchd[1] (com.apple.statd[254]): Exited with exit code: 1
Jul 7 10:37:44 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
Jul 7 10:37:54 zzzz com.apple.statd[255]: rpc.statd: unable to register (SM_PROG, SM_VERS, UDP)
Jul 7 10:37:54 zzzz com.apple.launchd[1] (com.apple.statd[255]): Exited with exit code: 1
Jul 7 10:37:54 zzzz com.apple.launchd[1] (com.apple.statd): Throttling respawn: Will start in 10 seconds
Jul 7 10:37:58 zzzz loginwindow[25]: 1 server now unresponsive
Jul 7 10:37:59 zzzz KernelEventAgent[26]: tid 00000000 unmounting 1 filesystems
Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: /net updated
Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: /home updated
Jul 7 10:38:02 zzzz com.apple.autofsd[40]: automount: no unmounts
Jul 7 10:38:02 zzzz loginwindow[25]: No servers unresponsive
... and firewall wide open.
I guess that the Finder somehow triggers file locking over NFS.

Can't access mounted shares as user

Just did a fresh install yesterday on an old machine and I can't seem to figure out how to access some mounted fat32 drives without becoming root. I added the user option to my fstab but that didn't change things. I can change the permissions of the folders manually but it resets to root on reboot.
heres the offending lines of my fstab:
/dev/sda1 /media/windowsxp vfat auto,exec,rw,user 0 2
/dev/sdc1 /media/windows2k vfat auto,exec,rw,user 0 2
/dev/sdc2 /media/windows7 ntfs auto,exec,rw,user 0 2
/dev/sdd1 /media/passport auto auto,exec,rw,user 0 2
Last edited by jcm65 (2010-12-25 18:29:15)

well I modified my fstab to:
/dev/sda1 /media/windowsxp vfat auto,exec,rw,user,dmask=000 0 2
/dev/sdc1 /media/windows2k vfat auto,exec,rw,user,dmask=000 0 2
/dev/sdc2 /media/windows7 ntfs auto,exec,rw,user,dmask=000 0 2
/dev/sdd1 /media/passport auto auto,exec,rw,user,dmask=000 0 2
and my /etc/group to:
root:x:0:root
bin:x:1:root,bin,daemon
daemon:x:2:root,bin,daemon
sys:x:3:root,bin
adm:x:4:root,daemon
tty:x:5:
disk:x:6:root,jeff
lp:x:7:daemon,jeff
mem:x:8:
kmem:x:9:
wheel:x:10:root,jeff
ftp:x:11:
mail:x:12:
uucp:x:14:
log:x:19:root
locate:x:21:
rfkill:x:24:
smmsp:x:25:
http:x:33:
games:x:50:jeff
network:x:90:
video:x:91:jeff
audio:x:92:jeff
optical:x:93:jeff,hal
floppy:x:94:jeff,hal
storage:x:95:jeff,hal
scanner:x:96:
power:x:98:jeff
nobody:x:99:
users:x:100:
dbus:x:81:
avahi:x:84:
hal:x:82:
(jeff is the user acount.)
and now I can acess the folders but still not the files.
Last edited by jcm65 (2010-12-25 18:28:54)

Mounting shares with nautilus

When I was using Ubuntu a few months ago Nautilus automatically mounted shared folders. That was really convenient and I'm trying to figure out how to do this on Arch. My shared folder icon comes up but when I try to open it I get the error, Unable to Mount Location: Failed to mount windows share.
I browsed the forum and the wiki looking for answers. I've messed with the samba.conf file and can't seem to get this to work. I even copied my roommates smb.conf from his computer running Ubuntu. Here's the smb.conf:
# Sample configuration file for the Samba suite for Debian GNU/Linux.
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
# Any line which starts with a ; (semi-colon) or a # (hash)
# is a comment and is ignored. In this example we will use a #
# for commentary and a ; for parts of the config file that you
# may wish to enable
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
; wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = true
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
; syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
; security = user
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
encrypt passwords = true
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
passdb backend = tdbsam
obey pam restrictions = yes
; guest account = nobody
invalid users = root
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how nsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
; domain logons = yes
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
; logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
; logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
########## Printing ##########
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
; load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap
# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
socket options = TCP_NODELAY
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
; domain master = auto
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
usershare owner only = False
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
; comment = Home Directories
; browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
; share modes = no
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
#[printers]
# comment = All Printers
# browseable = no
# path = /var/spool/samba
# printable = yes
# guest ok = no
# read only = yes
# create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
#[print$]
# comment = Printer Drivers
# path = /var/lib/samba/printers
# browseable = yes
# read only = yes
# guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# Replace 'ntadmin' with the name of the group your admin users are
# members of.
; write list = root, @ntadmin
# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
# The CD-ROM gets unmounted automatically after the connection to the
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
[usershares]
comment = Video Folder
path = /home/cd/video
read only = no
browseable = yes
writable = yes
public = yes
guest ok = yes
available = yes
usershares max shares = 100
usershares owner only = False

I'm having the same issue here, though not just in Nautilus.
Samba is working to some extent because I can access the directories I'm sharing on both of my Linux computer from a Windows laptop with no trouble. Come to think of it the Windows laptop (running XP) and my VirtualBox, also running XP, both access the samba shares fine.
However, I can not access them from the Linux computers. I have two Linux machines actually, Avalon and Atlantis. The one, Avalon, I can't access anything from/on (though Windows can access it just fine). The other one, Atlantis, I am sharing /homes and /srv, /srv mounts fine, but /homes will not. I'm sharing /srv on Avalon as well, but it won't mount.
To simplify, /srv on Atlantis is the only share I can access from either Linux machine. But only the /srv on Atlantis, not the /srv on Avalon.
I have smbnetfs installed. Here are my daemons from rc.conf:
DAEMONS=(syslog-ng network netfs smbnetfs crond dbus hal fam alsa mysqld mythbackend mpd openntpd lircd cups httpd sshd privoxy tor samba gdm)
I am curious though: does netfs and smbnetfs need to be running?
Any help would be appreciated. Thanks.
Frantic wrote:You should check your logs and see why the mount is failing, it's probably a small tweak (maybe fuse not loaded)
Probably something I should know already, but what logs should I check? Thanks.
Last edited by The Avatar of Time (2009-03-06 10:16:03)

Trying to access SMB share, can read but not write, I use the domain account to autenticate and domain account has access to the share. its a samba domain and im a Windows Admin by trade.

I have two I Mac's Intel i7 models.
I have some problems getting them to write files to SMB shares.
The domain user account I use when requested to enter when i first try to connect to the share seems to go though without a problem and it presents me with a list of mounts (shares) I select one and the folder opens, I can read files and copy them but I cant write to any of the folders.
I have also mounted the network locatiosn to a folder from the terminal while also specifying a user name and password to use but this also doesnt allow the specified user account to write data to the share.
I have confirmed the user account can write to the share by having the user do so from a windows box.
any help from any of you mac guys would be great!!!!
Im a windows fan boy / Windows Server based Network Administrator and am slowly becomming a fan of your macs (mainly due to the Unix terminal access letting me realise there is more control to be had than most haters would lead you to believe).
Peace Out

I should add that I originally formatted the problematic drive for FAT32 from the Mac, but then the WinXP computer couldn't see the drive when I plugged it in directly via USB. That's why I went with Seagate's utility to format it.

Accessing NFS mounts in Finder

I currently have trouble accessing NFS mounts with finder. The mount is O.K. I can access the directories on the NFS server in Terminal. However, in Finder when I click on the mount, instead of seeing the contents of the NFS mount I only see the "Alias" icon. Logs show nothing.
I am not sure when it worked the last time. It could well be that the problem only started after one of the lastest snow leopard updates. I know it worked when I upgraded to Snow Leopard.
Any ideas?

Hello gvde,
Two weeks ago I bought a NAS device that touted NFS as one of the features. As I am a fan of Unix boxes I chose an NAS that would support that protocol. I was disappointed to find out that my Macbook would not connect to it. As mentioned in previous posts (by others) on this forum, I could see my NFS share via the command line, but not when using Finder. I was getting pretty upset and racking my brain trying to figure it out. I called the NAS manufacturer which was no help. I used a Ubuntu LiveCD (which connected fine). I was about ready to give up. Then, in another forum someone had mentioned the NFS manager App.
After I installed the app and attempted to configure my NFS shares, the app stated something along the lines of (paraphrasing) "default permissions were incorrect". It then asked me if I would authenticate to have the NFS manager fix the problem. I was at my wits end so I thought why not. Long story short, this app saved me! My shares survive a reboot, Finder is quick and snappy with displaying the network shares, and all is right with the world. Maybe in 10.6.3 Apple will have fixed the default permissions issue. Try the app. It's donationware. I hope this post helps someone else.
http://www.macupdate.com/info.php/id/5984/nfs-manager

Accessing Windows CIFS Shares via Nautilus

Hi,
I've recently installed and configured Solaris 11, am having problems accessing Windows CIFS shares via Nautilus.
I've installed both samba (needed for CUPS to print to printers connect to a windows pc) and smb/client. The smb/client and samba services are running. The smb/server service is not installed.
I can print to any printer on the windows PC I'm trying to access via Nautilus, so I know my username/password for accessing the pc are correct.
I can also manually mount any share on the windows PC via the cli (eg mount -F smfs -o user=elin //elink/users /mnt), and browse the files directly that way, except the file permisssions don't seem to align with any unix user. Again this just shows that the username/password combination is ok.
For Samba, I'm using the default smb.conf file as /etc/samba/samba.conf. Workgroup is set to WORKGROUP in smb.conf.
On the Windows pc, in the security event viewer, I can see the auth request, however is failing with bad password (event ID 4776, error code 0x006a). In the default group policy object for networking, I've set to accept "LM & NT, NTLMv2 when neogiatated", as this allows legacy clients to connect. (Legacy meaning NT4, Win95, etc, and also has the benefit of allowing other OSes to connect as well).
I'm also able to access the WIndows PC CIFS shares from an Arch Linux based setup (running GNOME 3.2 w/ Nautilus 3.2), so I doubt it's the Windows side of things causing the problems. Additionally, when I was running Solaris 10u9 (just before upgrading to Sol11), I was able to access the shares via Nautilus as well.
So my question is:
1. Does Nautilus use Samba or the Oracle smb/client service to handle mount windows CIFS shares?
2. What log files or configuration files do I need to looking at to help with this error?
As a side question,
I've found that on a clean installation running the "Print Manager" accesses CUPS fine, but once you install a printer, it'll no longer connect to CUPS, unless run from the cli "sudo system-config-printers". So this is a permissions issue, where's the best place to fix/handle that one.

Replying to my own thread, as I have a possible but very-hackish solution.
To add some further details to my original post.
There are 4 PCs on the LAN.
1. Hellfire - OS = Solaris 11 11/11
2. Brimstone - OS = Arch Linux
3. Elink - OS = Win7 Pro x64 SP1
4. IsaacPC - OS = WinXP Home SP3
Attempting to connect to Elink from Hellfire, accessing CIFS shares via Nautulis fails. (Mounting shares via Nautulis fails, but works fine from CLI using 'mount' command which to my understanding uses the smb/client service to work). Elink also hosts all the printers on the LAN, a HP LJ1200 and an Epson Fax/Printer/Scanner.
Helfire does attempt to authenticate, as listed in the event logs on the Win7 PC (elink), but is returning bad password when using Nautulis. (but printing from hellfire to either printer on elink works fine, as does mounting CIFS shares using 'mount').
Booting the live CD of Solaris 11, also exhibits the same non-working behaviour when attempting to mount CIFS shares in Nautulis.
Attempting to access CIFS shares on elink from Brimstone (via Nautulis 3.2 within GNOME 3.2), or from IsaacPC works fine.
Hellfire configuration.
Samba is installed, but NOT running (samba is needed for accessing the printers on elink, as CUPS needs smbspool which is part of the samba package), and the native smb/client service is also running.
smb.conf is a direct copy of the default *.conf file, except the WORKGROUP is set to 'WORKGORUP'. There is a symlink to smb.conf in /etc/sfw/smb.conf -> /etc/samba/smb.conf
Onto the hackish-fix.
I've noticed that there are 2 copies of libsmbclient.so installed on the system, one in /usr/sfw/lib (part of the "libsmbclient" package) and another in /usr/lib/samba (part of the "samba" package).
"libsmbclient" appears to be based on samba 3.5.8 codebase, and is linked to the gvfsd-smb daemon (this is the software that Nautulis uses to talk SMB to access CIFS shares).
"samba" is based on the samba 3.5.10 codebase, and it's installation has nothing to do with GNOME or Nautulis in any manner.
Using any of the samba included tools to test SMB/CIFS functions, work with 1 minor exception (which I'll list below). eg, using smbclient I can list all shares on any PC on the LAN, etc.
So as a hunch, I renamed the libsmbclient.so.0 in /usr/sfw/lib, and symlinked /usr/sfw/lib/libsmbclient.so.0 -> /usr/lib/samba/libsmbclient.so.0 (so that gvfsd-smb is linked against the slightly newer version of the libsmbclient.so as included in the samba package located in /usr/lib/samba).
I rebooted Hellfire, and now I'm able to access CIFS shares via Nautulis, provided that some form of authentication is needed (that is a username and password is needed - guest access and blanks passwords don't work - but these IMO should be disabled immediately as part of a baseline security package in regards to Windows - so no harm there).
Now to the minor exception I noted earlier. When using smbclient to actually connect and transfer files, I get:
ld.so.1: smbclient: fatal: relocation error: file /usr/lib/libreadline.so.5: symbol tgetent: referenced symbol not found
As far as I know, tgetent is part of libtermcap.so, so I guess when building smbclient or libreadline.so, the link reference to termcap was left out? (or something like that). Anyway, that's another issue...

Same mounted shares different user accounts problem

I have two accounts on my MacPro that mount 4 smb shares from a Windows Server and two AFP shares from a NAS in an automater script
The shares work fine but when the other user logs on they can see the mounted shares but they are the generic blue folder icon with the red circle no access icon at the bottom of the icon.
They do not have access to the "icon" share even though they have the same share mounted and have access to the share.
When I remove the phantom "icon" share it removes the "real" mounted share from the other users account.
What or can I do anything to stop the redundant nonaccessable shares from being mounted?
Thank You

One additional comment on this: I did change iTunes preferences so that the location of iTunes files is the shared folder. With that I'd expect each user to be pointed to the same iTunes folder, but that's not the behavior.

When i login with microsoft account cannot access with administrative share c$

i have a problem when i login to windows with microsoft account cannot access any network computer with administrative sharing c$,d$ with windows 8.1
but when i login with local account can access
and some people tell me create key in regedit t fix it
after enter user name and password show this error
and i apply your instruction and not fix until now
note:
my Machine windows 8.1 if another machine in network windows 7 can access a hidden share if machine in network windows 8.1 show this message in image 2
but if i login with local user can i access all machine hidden share network windows 7 and 8.1

yes this computer i want to access name poland2-work and have two users
first :administrator
second : poland 2

Windows XP users can't access SMB/CIFS shares on MAC OSX10.4.4 Xserve bug?

The Xserves are new for us. This problem involves two of the 10.4 xerserves.
1 serves as an Open Directory System Master(10.4.3). 2 Serves as a file share & backup (10.4.4).
Both are production machines and cannot easily be restarted.
There is no Windows network, Active Directory or Windows domain in our network.
We created a SMB and AFP share on the file server which is a member of the Open Directory. (It is bound and kerberized to server 1).
The users all have accounts in the OD system and all passwords are Open Directory. Our users can ssh into the various xserves (including the file share server 2) and authenticate against OD.
We made the shares available via smb under Protocols --> Windows File Settings. We turned the Windows Service on in Server Admin. I'ts a standalone server and all the authentication types are checked under access.
The MAC (powerbook) users can access the share fine. The Windows users can't. The Windows laptops can see the file share server (through search - not visable is Network Neighborhood) but when they try and connect they are presented by an authentication box that just keeps cycling over and over regardless of what the user types as user name & passwd.
I tried to access the smb share with my powerbook(10.4.4) and have the same issue. I'm presented with an authentication box but authentication fails.
The Windows File Service Log shows:
auth.c:checkntlmpassword(312)
checkntlmpassword: Authentication for user [csmith] -> [csmith] FAILED with error NTSTATUS_WRONGPASSWORD
[2006/02/24 21:52:03, 1] authods.c:opendirectory_authuser(212)
User "csmith" failed to authenticate with "dsAuthMethodStandard:dsAuthSMBNTKey" (-14090)
[2006/02/24 21:52:03, 1] authods.c:opendirectory_smb_pwd_checkntlmv1(427)
opendirectorysmb_pwd_checkntlmv1: [-14090]opendirectoryauthuser
[2006/02/24 21:52:03, 2] /SourceCache/samba/samba-92.15/samba/source/auth/auth.c:checkntlmpassword(312)
checkntlmpassword: Authentication for user [csmith] -> [csmith] FAILED with error NTSTATUS_WRONGPASSWORD
[2006/02/24 21:52:03, 1] authods.c:opendirectory_authuser(212)
User "csmith" failed to authenticate with "dsAuthMethodStandard:dsAuthSMBNTKey" (-14090)
[2006/02/24 21:52:03, 1] authods.c:opendirectory_smb_pwd_checkntlmv1(427)
opendirectorysmb_pwd_checkntlmv1: [-14090]opendirectoryauthuser
[2006/02/24 21:52:03, 2] /SourceCache/samba/samba-92.15/samba/source/auth/auth.c:checkntlmpassword(312)
checkntlmpassword: Authentication for user [csmith] -> [csmith] FAILED with error NTSTATUS_WRONGPASSWORD
[2006/02/24 21:52:03, 2] /SourceCache/samba/samba-92.15/samba/source/smbd/server.c:exit_server(595)
Closing connections
I've googled this error and it seems that there a lot of engineers out there with the same problem but no answers. Could this be a bug with Apple's SMB process? Is there something I've missed? (I've looked at the smb.conf and have even turned off deny clear text passwords - I've even tried granting guest access) Anyone have any ideas?

On the server itself, run the following in the Terminal:
(from a few different sources):
run ps -auxw | grep Password
to see if Password service is running
Also check the logs in /Library/Logs/PasswordService
Try: id username
and see if you get some info returned.
Ex: id jimguy
You should get some info about uid, gid, groups.
sudo killall -USR1 DirectoryService
Then try to login from a client machine.
Be sure to re-issue
sudo killall -USR1 DirectoryService
in order to stop the (far more) verbose logging.
Then check the logs in /Library/Logs/DirectoryService
In Open Directory, you might want to revert to standalone (this will destory the existing OD setup) and then re-promote to OD Master. You'll lose all OD users however when doing so. If you don't have many, this may be best.
You'll want to verify the hostname, and forward & reverse DNS lookups before re-promoting, and watch for any errors when promoting to OD master
See, when you say "The real clue is that I'm unable to access the shares from my Powerbook G4 with my Open Directory account. I can log in to the file share as the local admin though and that's why I'm thinking there is a bug in the samba/OD relationship. " - that's the real clue indeed.
The local admin account, the first admin account you setup on the server, is indeed local, and resides in NetInfo, not Open Directory.
So something is afoul in your OD.

I cant access the root share of a windows server after upgrading to mountain lion

Hi Guys,
Since upgrading to mountain lion i cant access the shared drives on our windows server. For example in a windows machine if i go to run the type \\server\ i get all the visible shares available. in my previous version i was able to do the same (obviously i would authenticate with my AD account). now when i try to access those same shares i get the message below:
"The operation cant be completed becuase the original item for "/" cant be found"
I can however connect to the shares directly for example if i connect to server path \\server\data it works ok.
I have verified my account details and they are ok - i have also disconnected and reconnected the connection.
This was working fine before the upgrade. can anyone help??

well iv just managed to get to 35 gig free (just deleting iphone backups) and im now able to get past the next screen on bootcamp.
unfortunatly its only allowing me to create a new partition not delete the current.
this is leading me to think the old ones master partition has become damaged and the hard drive dosent know it exists any more.
if this is the case (please tell me im wrong though) what options do i have as i dont want to / have the money to buy another hard drive to back everything up to it with.
thanks again
gareth

Cannot access local DFS shares while VPN is active

Hi
We use Windows Server 2008 Standard as a domain controller. It also hosts DFS. Although the namespaces are hosted on the server, the data is stored on a Windows 2008 Storage Server. We do not use DFS replication.
I have several DFS shares mapped on my Windows 7 client, which has just replaced my XP client, and can access them without any problems.
However, as soon as I connect to a remote network (located on a different domain - it has nothing to do with our network at all), I am unable to access our DFS shares. If I try to access a DFS share an error message pops up stating:
Location is not available
Logon failure: unknown user name or bad password.
The first time I connected the VPN a network dialog popped up asking what type of network it was and I chose Work. After connecting via the VPN I use remote desktop to carry out daily maintenance on a server on the remote network.
Other local resources are available. I can ping machines via IP, name and FQDN. I can access the same DFS shares using UNC paths. So, although I receive the error message described above when accessing AD-name.local-backslash-share-name1 I have no trouble
accessing server-name-backslash-share-name1
As soon as I close the VPN connection normal functionality is restored and I can again access the DFS shares without any problems.
Can someone help me fix this, please? When this was setup on my XP machine I never experienced this problem.
Also, is there a way of typing LAN addresses without the forum software converting them to a customised hyperlink? Thanks!

Thank you, fupin
Sabrina's suggestion to edit the pbk file worked. I changed the setting from 1 to 0 and connected to the remote network via the VPN and am still able to access the local DFS shares.
As per the OPs comments, the username and password I am using for the remote network are both different from the credentials I am using on the local network.
... take the steps in the KB 822707 to resolve it:
1). Locate the .pbk file that contains the entry that you dial. To do so, click Start, click Search, type *.pbk in the All or part of the file name box, and then
click Search.
2). Open the file in Notepad.
3). Locate the following entry: UseRasCredentials=1
4). Modify the entry to the following: UseRasCredentials=0
5). On the File menu, click Save, and the click Exit.
Cheers!

Cant access a DFS share from a Windows 7 computer

I am having DFS share access issues with a Windows 7 workstation.
My setup is I have 6 windows 7 stations accessing this DFS Share.
All computers have the same Administrator password and another User/Password
All but 1 are working as they should.
The DFS share is running under Server 2008 R2 and contains files from this and another server.
From the workstation, I can see the server under Network.
I can open it and see the individually shared volumes and I have full read/write permissions.
I can see the DFS share and I can map it.
If I try to open the shared volumes within the DFS file I get a message saying I dont have permission.
Interestingly, when I look at the properties of the DFS share form the workstation, I dont see a DFS tab.
If I do this from a workstation is is able to connect fully to the share, I see a DFS tab in the properties.
I tried to include everything,
Thanks in advance

Hi,
Please try hotfix in the following KB,and check the result.
You cannot access a DFS share through a mapped network drive on a computer that is running Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/kb/983620/en-us
Some steps for troubleshooting DFS you can try
http://technet.microsoft.com/en-us/library/cc962144.aspx
How to troubleshoot Distributed File System Namespace access failures in Windows
http://support.microsoft.com/kb/975440/en-us
use command dfsutil /pktinfo to test the access to the DFS root and connectivity to the root shares
http://blogs.technet.com/b/askds/archive/2009/06/04/the-case-of-the-random-dfs-access-denial.aspx
Regarding to the missing dfs tab, there's a policy, locate to User Configuration\Administrative Templates\Windows Components\Windows Explorer\remove dfs tab, then users can not view or change the properties of the dfs shares
Yolanda Zhu
TechNet Community Support

No access on podcast share from Windows clients

Hello together!
I have the following scenatio at home:
* 1 Server with Windows 2008 R2 with logged in user and iTunes running (everything is shared)
* 1 Laptop with Windows 7 x64 & iTunes
* 1 Desktop with Windows 7 x86 & iTunes
* 1 Macbook with Mac OS X Leopard & iTunes
With this constellation I want to have access to my iTunes library located on the server from all other computer. With the MacBook this funktions without any problem to access everything (podcasts too).
On both Windows computer the directory pocasts is invisible. I can find the podcast files in the main directory but they are grey and the the playback does not start.
Is here anyone who had already the same problem and perhaps solved it? Thank you in advance for your replies.
P.S. Generally I can play the files by changing the kind of media to movie.
Message was edited by: Mattn81

Oleg,
I had the exact same problem here - we have two XSERVE machines here running OSX 10.5.7 server, and we're accessing a samba share on these servers from Windows XP SP3 clients.
When moving a file, I noticed a message in /var/log/samba/log.smbd :
[2009/06/15 12:45:30, 0, pid=50709] /SourceCache/samba/samba-187.8/samba/source/modules/vfsdarwin_acls.c:fsp_setacl(126)
darwinacl: failed to set ACL on <filename>: Invalid argument
!#acl 1
I tried to look this up on google, but had no success.
Searching the file /etc/smb.conf for "acl" showed the following line:
vfs objects = darwinacl,darwin_streams
(Un)commenting this line (inserting a ";" in front of the first character) and restarting s,b solved the problem here - I'm now able to move files without having the permissions set to 0000, and the error in log.smbd doesn't appear any more.

Why Can't I Access My Leopard Shares from Vista

I can access my Vista shares from Leopard via Go->Connect To Server (although they don't automatically just appear in Finder as they did in Tiger). In Vista, I can see my MBPro, but when I click on it there's a long wait followed by a Network Error, saying Vista can't access my Mac and telling me the network path was not found. I don't get even get a Login dialog box into which to enter my username and password. My MBPro is connected wirelessly to my Airport Extreme network, while the PC is connected via cable into the back of the AE.
Yes, I've turned on File Sharing.
Yes, I've made sure that the Workgroup is the same both in Leopard and Vista.
Yes, I've created a new NETBios name for my MBPro and can confirm that Vista sees my Mac by the new name.
Yes, I've made sure that SMB file sharing (and only SMB) is enabled.
Yes, I've made sure that my username and passwords are identical in both Leopard and Vista.
Yes, I've created an entirely new Network location.
Yes, I've made sure "Read & Write" are enabled.
Yes, I've set my Mac firewall to allow all incoming connections and made sure my Windows firewall is turned off.
Yes, I spent 45 minutes on a call with a very helpful and patient Apple tech support rep who wasn't able to solve the problem.
Can anyone offer any other advice?
Thanks.

There is a bit of work you need to do on Vista because of Vista's authentication model:
To enable Windows Vista to connect to Mac OS X with Windows File Sharing enabled, you will need to change the following policy in Windows Vista:
Start>Run>secpol.msc [enter]
Click on "Local Policies" --> "Security Options"
Navigate to the policy "Network Security: LAN Manager authentication level" and double-click it to get its Properties. By default Windows Vista sets the policy to "NTVLM2 responses only". Use the drop-down arrow to change this to "LM and NTLM – use NTLMV2 session security if negotiated".
In Vista Home Premium, you won't have this tool so:
1. Run the registry editor elevated and open this key:
HKEYLOCALMACHINE\SYSTEM\CurrentControlSet\Control\Lsa
1. If it doesn't already exist, create a DWORD value named
LmCompatibilityLevel
3. Set the value to 1
4. Reboot
If you are using a third-party firewall on Vista, uninstall it; don't just turn it off. If you are using Vista's built-in firewall (which is adequate for most people), you don't need to turn it off - just configure it for file/printer sharing. Make sure Vista thinks your LAN is Private and not Public.

Apache access to mounted shares.

Similar Messages

Maybe you are looking for