How to access a samba share?

Hi everyone
I tried setting up a diskless folding comp to push out a few more PPD, which I did succesfully. On my windows comp when I go to Network Places I can see it in the group "Diskless"
I downloaded fahmon to see if I could monitor it, and all I had to do was type "\\Fold-2cb9\c\etc\folding\1\" for client location and I could monitor it on the windows comp...how would I veiw it from my Linux machine?

I tried that and it didn't work...
I used this command:
sudo mount -t smbfs //Fold-2cb9/c ~/Fold
and this is what I got
Error connecting to 63.251.179.32 (Connection refused)
4099: Connection to Fold-2cb9 failed
SMB connection failed
Edit:
I downloaded smbnetfs and ran "smbnetfs ~/Fold/" and now I can browse through everything! Although for some reason I can't open the "Fold" folder in Thunar as soon as I try it, Thunar immediately kicks me out back into the home directory. Then I tried to type the address in Thunar's address bar and when I hit enter the folder disappeared Although when I looked at my home directory through Firefox I could see it was still there and I could browse through everything...bug maybe?
Ah well..I'm happy
Last edited by whaevr (2008-07-23 16:46:26)

Similar Messages

How to start my Samba share correctly?

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

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

How to access a Network Share between two servers in same data centre

I have two dedicated servers (both Windows 2012 Server) hosted in a data centre somewhere. I want to share a folder on one server with the other server, but it's obviously not as straight forward as one might think. My servers are called "Maximus"
and "Apprentice".
On Maximus I shared a folder by right clicking on it and choosing "Share with... / Specific People", I then typed in the name of a local user account which also exists on Apprentice with the same name and password. (so each server has a local
user account with the same name and password).
So then on Apprentice, I was hoping I could access the share (while being logged in as this user with whom the folder was shared) by simply typing "\\ipaddress\sharename" into the address bar in file explorer. Unfortunately it comes
back with "Windows can not access [ip address]".
Now, I do have a website setup on the IP address for Maximus. This is actually the reason I want to create this share. I need the second server for load balancing and need to share IIS config as well as the website itself. (So I will need
two shares eventually, but for now I'm just trying to get one to work). I don't know if the fact that the ip address is pointing to the website is causing me problems here or if it's something else.
Are there any network gurus out there who can tell me what the issue is and how to resolve it?

I can ping both servers in either direction, but I believe I may have found the problem. Apparently my host is blocking port 445 which Windows wants to use to connect to the share and they will not unblock it.
Is there a way to connect to the share through a different port?
To my knowledge, you cannot change the port. However, you can try disabling your security software for testing. If this fixes the problem then you need to adjust your security software configuration so that traffic on this port is not blocked or filtered.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Nemo and Nautilus crashing on accessing Samba shares

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

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

How do I get samba to be wide open??

I setup my mac mini with 10.4 some time ago and something recently happened where my wife (XP user) can't get into our shared folder. She can't access itunes music either.
I've been playing around with this for a couple days and got lost on what changes I've made. Right now I'm just trying to figure out how to get the samba shares totally wide open, then worry about how to secure it. What's the best way to open it up? Here's my config files. Thanks.
[global]
encrypt passwords = yes
workgroup = WORKGROUP
display charset = UTF-8-MAC
security = user
deadtime = 5
guest account = unknown
client ntlmv2 auth = no
preferred master = no
defer sharing violations = no
allow trusted domains = no
netbios name = TNNserver
lanman auth = YES
vfs objects = darwin_acls
wins support = no
brlm = yes
max smbd processes = 0
server string = Mac OS X
os level = 8
domain logons = no
passdb backend = opendirectorysam guest
dos charset = CP437
unix charset = UTF-8-MAC
auth methods = guest opendirectory
local master = yes
domain master = no
map to guest = Never
use spnego = yes
printer admin = @admin, @staff
ntlm auth = YES
log level = 0
[Public]
oplocks = 0
map archive = no
vfs objects = darwin_acls
path = /Shared Items/Public
read only = no
strict locking = 0
inherit permissions = 1
comment = macosx
create mask = 0666
guest ok = 0
directory mask = 0777

bump

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.

Windows samba share shows "zero KB" for file size....

Upgraded, clean install, to leopard and now I see "Zero KB" for file size on my Windows Home Server samba shares. Before the upgrade all that info was displayed but afterwards that info is gone. The only changed on my network was upgrading to Leopard. My linux samba server still works perfectly with 10.5 but the windows samba shares are not. I can browse, mount and copy files to and from the windows samba shares but the file size info isn't displayed. The file size isn't even displayed when I "Get Info" on a file. Previously using 10.4 all was working perfectly and all info was displayed and or was available if I wanted it. Not sure if it is something to do with how Windows Home Server handles samba or if it is how Leopard handles windows samba shares. No settings were changed on my network from when I was running 10.4. The only change on my home network/hardware has been upgrading to Leopard! No other changes were made to any servers or computers that were previously working perfectly with 10.4. Other than this "Zero KB" issue all has gone quite smoothly.

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

Able to view new files from a samba share only after refresh

Hello Guys,
I'm currently trying to access a samba share from windows server 2012
When I access the share I'm only able to view 210 files out of 460 files
and the remaining files are only viewable after refresh(F5)
This Issue is also appear to be Intermittent, I'm freaked out with this strange behaviour
and unable to run my scripts on the share they end up with unable to find the files!!
Please help me in resolving this
Thanks in Advance

Hi, this is due to an issue with samba interoperability.update your samba drivers
http://blogs.msdn.com/b/oldnewthing/archive/2006/03/30/564809.aspx#comments
MCP/MCSA/MCTS/MCITP

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.

How to remove samba share from dolphin?

Hi guys!
Can't remove samba share from dolphin. Moreover, can't found where this share mounted. mount doesn't shows that share mounted, but I can access it via smb:/192.168.1.5/share.
How to unmount this share?
Thanks in advance.

Why we may never know, but you can't delete it. Right-click on the toolbar & choose customize toolbar. Drag that Share button off into a cloud of smoke & click done. No more share button.

App freeze on accessing Samba shares

Hi,
I really didn't want to have to make a topic on this, as I've searched all over the place and I'm beginning to wonder if I'm the only one with this problem (unless I've somehow missed something).
Basically I have some Samba shares set up like this in my fstab:
# Share Mounts
//<address>/share1 /home/eldersnake/Shares/share1 cifs noauto,x-systemd.automount,users,uid=eldersnake,gid=users,password= 0 0
//<address>/share2 /home/eldersnake/Shares/share2 cifs noauto,x-systemd.automount,users,uid=eldersnake,gid=users,credentials=<credentials location> 0 0
The problem is periodically, trying to access/mount these shares through let's say, Dolphin (but it happens in any file manager I try) causes the program to simply hang. It will stay there, hung and cannot be killed, even with the "kill -9" command. Only rebooting gets rid of the process.
And looking at the process list with KDE's system monitor lists the affected program status as "disk sleep". Again, it cannot be killed. I've seen this happen with my file manager, Clementine (when I tried to open up a file, therefore it opened up the file dialog and I clicked on a share mount) and even in my terminal...
Even running
sudo mount /home/eldersnake/Shares/share1
for example, nothing happens. The terminal is simply hung and never completes.
I say this happens periodically because sometimes it seems to work just fine. Then some days, it does the above consistently. I'm really unable to pin it down.
Anyway I removed the x-systemd.automount option from fstab and so far I have not been able to reproduce this problem. I'd file a bug report but I can't help but wonder if I've missed something obvious and I'm unsure how to provide evidence that it's systemd specifically causing the problem. Thanks for any help.
EDIT: I should add this occasionally also happens on a separate machine, my netbook. Again, only after adding the systemd automount line to the fstab file.
Also manually mounting the share with
sudo mount -t cifs <share> <directory>
always works fine. It's simply when using the fstab entry combined with systemd automount.
EDIT: Took systemd-automount out of the title as I am not sure its the cause anymore.
Last edited by ElderSnake (2012-11-24 00:02:24)

Okay, still happening. Often I reboot and everything works fine but sometime later, can be 10 mins...could be 10 hours, this problem re-emerges.
I did however manage to catch this in dmesg
[ 4448.046038] kernel BUG at fs/dcache.c:2138!
[ 4448.046041] invalid opcode: 0000 [#1] PREEMPT SMP
[ 4448.046046] Modules linked in: fuse msr des_generic ecb md4 md5 hmac nls_utf8 cifs fscache usb_storage uas joydev hid_generic snd_usb_audio snd_usbmidi_lib snd_rawmidi usbhid snd_seq_device hid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer nvidia(PO) snd r8169 soundcore iTCO_wdt psmouse serio_raw acpi_cpufreq mperf coretemp mii evdev microcode firewire_ohci firewire_core crc_itu_t gpio_ich intel_agp i2c_i801 iTCO_vendor_support intel_gtt i2c_core lpc_ich processor pcspkr button vboxdrv(O) ext4 crc16 jbd2 mbcache sd_mod sr_mod cdrom ata_generic uhci_hcd pata_acpi pata_jmicron ata_piix libata scsi_mod ehci_hcd usbcore usb_common
[ 4448.046115] CPU 1
[ 4448.046120] Pid: 3062, comm: pool Tainted: P O 3.6.6-1-ARCH #1 Gigabyte Technology Co., Ltd. EP45-DS3/EP45-DS3
[ 4448.046123] RIP: 0010:[<ffffffff81195843>] [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.046133] RSP: 0018:ffff88009c627b88 EFLAGS: 00010286
[ 4448.046136] RAX: 00000000000176bd RBX: ffff880040ff7ddc RCX: 0000000000000013
[ 4448.046138] RDX: ffffc90000002000 RSI: ffffc900000bd5e8 RDI: ffff880040ff7d80
[ 4448.046141] RBP: ffff88009c627ba8 R08: 0000000000010000 R09: ffff88009c627fd8
[ 4448.046143] R10: ffff8800a751a4a0 R11: 0000000000000000 R12: ffff880040ff7d80
[ 4448.046146] R13: 0000000000000000 R14: 00000000fffffffe R15: 000000000000010f
[ 4448.046149] FS: 00007fb76933c700(0000) GS:ffff8800bfc80000(0000) knlGS:0000000000000000
[ 4448.046152] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 4448.046154] CR2: 00007fb74c0010b8 CR3: 000000003cb77000 CR4: 00000000000007e0
[ 4448.046157] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 4448.046160] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 4448.046163] Process pool (pid: 3062, threadinfo ffff88009c626000, task ffff8800638fa850)
[ 4448.046164] Stack:
[ 4448.046166] ffff8800a4af7e00 0000000000000000 ffff880040ff7ddc ffff880040ff7d80
[ 4448.046172] ffff88009c627bb8 ffffffff811958e6 ffff88009c627bd8 ffffffff8119591c
[ 4448.046176] 0000000000000000 ffff8800a4914480 ffff88009c627c38 ffffffffa0e6c973
[ 4448.046181] Call Trace:
[ 4448.046187] [<ffffffff811958e6>] _d_rehash+0x36/0x40
[ 4448.046191] [<ffffffff8119591c>] d_rehash+0x2c/0x40
[ 4448.046201] [<ffffffffa0e6c973>] cifs_lookup+0x263/0x360 [cifs]
[ 4448.046210] [<ffffffffa0e6cab2>] cifs_atomic_open+0x42/0x230 [cifs]
[ 4448.046214] [<ffffffff81197fa5>] ? d_lookup+0x35/0x60
[ 4448.046218] [<ffffffff8118eadf>] do_last+0x56f/0xea0
[ 4448.046223] [<ffffffff8118f4ca>] path_openat+0xba/0x520
[ 4448.046227] [<ffffffff8118fc91>] do_filp_open+0x41/0xa0
[ 4448.046232] [<ffffffff8119c766>] ? alloc_fd+0xd6/0x120
[ 4448.046237] [<ffffffff8117e9d6>] do_sys_open+0xf6/0x1e0
[ 4448.046241] [<ffffffff8117eae1>] sys_open+0x21/0x30
[ 4448.046246] [<ffffffff81499f2d>] system_call_fastpath+0x1a/0x1f
[ 4448.046248] Code: 48 89 16 0f ba 36 00 65 48 8b 04 25 f0 c6 00 00 83 a8 44 e0 ff ff 01 48 8b 80 38 e0 ff ff a8 08 75 0b 48 83 c4 10 5b 41 5c 5d c3 <0f> 0b e8 96 c2 2f 00 eb ee 49 89 c4 48 89 c3 41 83 ac 24 44 e0
[ 4448.046295] RIP [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.046300] RSP <ffff88009c627b88>
[ 4448.046322] ---[ end trace 822cd52e99a52b51 ]---
[ 4448.046327] note: pool[3062] exited with preempt_count 1
[ 4448.055386] ------------[ cut here ]------------
[ 4448.055393] kernel BUG at fs/dcache.c:2138!
[ 4448.055396] invalid opcode: 0000 [#2] PREEMPT SMP
[ 4448.055401] Modules linked in: fuse msr des_generic ecb md4 md5 hmac nls_utf8 cifs fscache usb_storage uas joydev hid_generic snd_usb_audio snd_usbmidi_lib snd_rawmidi usbhid snd_seq_device hid snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_page_alloc snd_timer nvidia(PO) snd r8169 soundcore iTCO_wdt psmouse serio_raw acpi_cpufreq mperf coretemp mii evdev microcode firewire_ohci firewire_core crc_itu_t gpio_ich intel_agp i2c_i801 iTCO_vendor_support intel_gtt i2c_core lpc_ich processor pcspkr button vboxdrv(O) ext4 crc16 jbd2 mbcache sd_mod sr_mod cdrom ata_generic uhci_hcd pata_acpi pata_jmicron ata_piix libata scsi_mod ehci_hcd usbcore usb_common
[ 4448.055471] CPU 1
[ 4448.055476] Pid: 3063, comm: pool Tainted: P D O 3.6.6-1-ARCH #1 Gigabyte Technology Co., Ltd. EP45-DS3/EP45-DS3
[ 4448.055479] RIP: 0010:[<ffffffff81195843>] [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.055488] RSP: 0000:ffff88003a059b88 EFLAGS: 00010286
[ 4448.055491] RAX: 000000000004ad5b RBX: ffff880040ff7a1c RCX: 0000000000000013
[ 4448.055494] RDX: ffffc90000002000 RSI: ffffc90000258ad8 RDI: ffff880040ff79c0
[ 4448.055496] RBP: ffff88003a059ba8 R08: 000000000001b2c0 R09: ffff8800bfc9b2c0
[ 4448.055499] R10: ffff8800a751ae60 R11: 0000000000000000 R12: ffff880040ff79c0
[ 4448.055501] R13: 0000000000000000 R14: 00000000fffffffe R15: 0000000000000110
[ 4448.055505] FS: 00007fb768b3b700(0000) GS:ffff8800bfc80000(0000) knlGS:0000000000000000
[ 4448.055507] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[ 4448.055510] CR2: 00007f8507000000 CR3: 000000003cb77000 CR4: 00000000000007e0
[ 4448.055513] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 4448.055515] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 4448.055518] Process pool (pid: 3063, threadinfo ffff88003a058000, task ffff8800638fc890)
[ 4448.055520] Stack:
[ 4448.055522] ffff8800ae280200 0000000000000000 ffff880040ff7a1c ffff880040ff79c0
[ 4448.055527] ffff88003a059bb8 ffffffff811958e6 ffff88003a059bd8 ffffffff8119591c
[ 4448.055531] 0000000000000000 ffff8800956d5cc0 ffff88003a059c38 ffffffffa0e6c973
[ 4448.055536] Call Trace:
[ 4448.055542] [<ffffffff811958e6>] _d_rehash+0x36/0x40
[ 4448.055546] [<ffffffff8119591c>] d_rehash+0x2c/0x40
[ 4448.055556] [<ffffffffa0e6c973>] cifs_lookup+0x263/0x360 [cifs]
[ 4448.055564] [<ffffffffa0e6cab2>] cifs_atomic_open+0x42/0x230 [cifs]
[ 4448.055568] [<ffffffff81197fa5>] ? d_lookup+0x35/0x60
[ 4448.055572] [<ffffffff8118eadf>] do_last+0x56f/0xea0
[ 4448.055577] [<ffffffff8118f4ca>] path_openat+0xba/0x520
[ 4448.055582] [<ffffffff8118fc91>] do_filp_open+0x41/0xa0
[ 4448.055586] [<ffffffff8119c766>] ? alloc_fd+0xd6/0x120
[ 4448.055591] [<ffffffff8117e9d6>] do_sys_open+0xf6/0x1e0
[ 4448.055595] [<ffffffff8117eae1>] sys_open+0x21/0x30
[ 4448.055600] [<ffffffff81499f2d>] system_call_fastpath+0x1a/0x1f
[ 4448.055602] Code: 48 89 16 0f ba 36 00 65 48 8b 04 25 f0 c6 00 00 83 a8 44 e0 ff ff 01 48 8b 80 38 e0 ff ff a8 08 75 0b 48 83 c4 10 5b 41 5c 5d c3 <0f> 0b e8 96 c2 2f 00 eb ee 49 89 c4 48 89 c3 41 83 ac 24 44 e0
[ 4448.055649] RIP [<ffffffff81195843>] __d_rehash+0x83/0xf0
[ 4448.055653] RSP <ffff88003a059b88>
[ 4448.055666] ---[ end trace 822cd52e99a52b52 ]---
[ 4448.055670] note: pool[3063] exited with preempt_count 1
Not sure what to make of it though other than it's something CIFS related, but whether CIFS itself is the problem I'm unsure. I just installed the samba daemon as suggested above though and will see how we go.
EDIT: The pid it's referring to in the stacktrace is a process which I noticed appears as a zombie after the problem occurs. The process is "gvfs-udisks2-vo".
Last edited by ElderSnake (2012-11-23 23:41:44)

Access to Samba\vfiler share via shortname

I wasn't sure which section to post this under as it occurs on different
operating Systems (Windows XP SP3, WIndows 7, Windows 8, Server 2003, Server
2008) and is random.
Basically, some of our end users experience problems accessing shares to a
vfiler for example with shortname \\example\share.
They can access this specific share via ip address or fqdn
\\example.domain.local\share. The
user can even access \\example and be
able to
view shares there but when clicking on the share it comes back with network
error or access denied.
This does not happen to all users at a time and on the same
workstations\servers and there are no specific times. On the end users
workstation DNS and wins is working, they have
no problems accessing other
vfilers or F&P Windows shares.
I tried all flushing DNS and wins cache, tried rebuilding CSC (Offline files)
to no avail. We don't have this enabled in our environment in any case
but
gave it a try.
One way I got it working via shortname is by adding a new security group to
the security permissions on the share. The group only had my account as a
member
and exsiting groups remained. After this the end user was able to map
via shortname.
I've tried many things and just can't figure this out or where to look. My
team doesn't manage the vfilers or samba shares so
can't look at the logs or
anything.
Another scenarion I have is for a Samba share, very similar situation but
this time its accessing the share on a Windows 2008 R2 server.
Basically
similar symptoms, can't access via shortname, get 'Network Error', tried several
things, even Windows Network Diagnostic
where it states that "The remote
device or resource won't accept the connection', "The device or resource (samba)
is not setup to accept connection
on port "The File and printer sharing
(SMB)". Port 139 is open, can access other shares on different storage devices
successfully.
What's weird is that after some time, An hour, 2 or 3 later functionality
returns without any changes. Obviously restarting the server resolved this
quicker.
There are no scheduled tasks or tasks running in the background,
Windows firewall is disabled, disabled AV etc.
I managed to get a log from this Samba device but not sure if its
related or not.
[root@samba] [09:30:52] /var/log/samba
# tail /var/adm/messages
Apr
3 08:33:06 samba adbindd[24524]: [ID 323999 auth.error] ERROR samba.adbindd2
Task exit with cims error: Error sending response: Broken pipe
Apr 3
09:10:07 samba adbindd[24524]: [ID 323999 auth.error] ERROR samba.adbindd2 Task
exit with cims error: Error sending response: Broken pipe
Only other thing I can think of is that is may have something to do with the
device, folder redirection, cache or something of that sort.
I'm stuck, anyone have any ideas. I would like to know what else to try if
the issue re-coccurs.
MCSE: 2003, MCITP: Enterprise Administrator, MCITP: Enterprise Messaging Administrator

Hi,
I installed KB 2194664 and haven't had the problem since.
http://support.microsoft.com/kb/2194664
If it happens again I will revisit.
Thanks.
MCSE: 2003, MCITP: Enterprise Administrator, MCITP: Enterprise Messaging Administrator

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

Unable to Access OS X Samba Shares (from Win98 machine) after 10.4.6

I've got a Windows 98 machine networked with my Mac. Under OS X, I used Share Points to setup shares on the Mac, which I was able to access fine from the Windows 98 (not SE) machine. Until I installed 10.4.6. Now when I try to access the same shares from Win98, I'm asked for a password. When I enter the password, it says resource not available.
I'm pretty sure it's got something to do with Windows 98 because I hooked up a Win XP notebook and was able to access the shares on OS X using the same password (that failed when trying to access from 98).
Any ideas?
Thanks!

I don't know if this will help, but I have discovered that with AFP access, passwords are now case sensitive, whereas they were not in 10.4.5 and earlier. I went to the Windows Server and looked at how the username and password was set up for access, and saw that they were set up with both having initial caps and the rest lower case. In 10.4.5 and earlier, we were logging in over the network with all lower case on both without a problem. With 10.4.6, we have to type them both with initial caps. I banged my head against the wall and spent several days on these forums looking for this answer with no results. Today our part time PC IT guy was in and I asked him if he had any suggestions, and within 3 minutes he had solve my problem.
Thanks, Apple!

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 to access a samba share?

Similar Messages

Maybe you are looking for