Can't connect to Samba shares after upgrading

imiric · 2011-09-07 00:37:35

Hi,

I recently upgraded to Samba 3.6.0-8 (among other things, including a new kernel 3.0-ARCH), and all my shares have become unavailable from Windows 7. I can't connect to any, nor can I see the shares list. My Arch box has essentially become invisible as far as CIFS shares go. I can still ping it normally, and access it through SSH, so it doesn't seem to be a major network issue, this is specifically with Samba.

I have since tried changing my workgroup in Samba, downgrading to 3.6.0-{1,4}, disabling firewalls, changing Win7's security settings, and restarting several times, to no avail. Nothing has changed with my Windows box, I only performed a major upgrade to Arch (it is currently up-to-date).

I don't see any relevant errors in the Samba logs, and I can browse the shares just fine locally in Arch, I just can't see them from Windows.

Anyone have a clue?

Thanks,

IM

ralvez · 2011-09-07 02:48:18

A while back I had some similar situation with my wife's Win7 PC. I was fine connecting from Arch but she lost the shares.
After checking passwords and other things I deleted the share from win 7 and created a new network connection and it went back to normal.
Hope this helps.

R.

calliuz · 2011-09-07 07:54:03

Assure that you still have free space left (check with

df -h

) on your Samba share and root etc partitions after upgrading! You could for example run

sudo pacman -Sc

to recover some in /var/cache/pacman and if this folder is located on the root ( / ) partition then Samba will often magically work again...

Last edited by calliuz (2011-09-07 08:31:57)

imiric · 2011-09-08 23:41:17

Umm space? No, that's definitely not the issue.

@ralvez: Right, I've already done that. The thing that's bothering me is that there were absolutely no changes to the machine, the only thing I did was upgrade (a lot of packages, admittedly). After rebooting, my Arch box is just not visible in my Windows workgroup.

/sigh

calliuz · 2011-09-09 21:19:40

Have you checked
http://wiki.samba.org/index.php/Windows7
and
http://www.samba.org/samba/docs/man/Sam … nosis.html
?

Last edited by calliuz (2011-09-09 21:20:14)

skanky · 2011-09-21 16:20:31

Something like this happened to me, however I found that restarting samba fixes it for that boot - they are both PCs so get shutdown and restarted together, so I couldn't say which boot.

I think I need to restart it after the Win7 machine tries to connect - not just after a Linux box reboot. It's on my list of things to fix, but dropped down in priority once I'd discovered this workaround.

firecat53 · 2011-09-21 18:17:25

Is your arch server configured to allow samba traffic? With the recent removal of hosts.allow and hosts.deny, I wonder if this could be the issue? Do you have ufw or iptables? I know you said you disabled the firewall, but it wasn't clear if that was on the client or server.

Scott

edit: here's the ufw rule I use (/etc/ufw/applications.d/samba):

[Samba]
title=Windows file and printer server for Unix
description=Tools to access a server's filespace and printers via SMB
ports=137,138/udp|139,445/tcp

Last edited by firecat53 (2011-09-21 18:18:59)

Arch Linux

#1 2011-09-07 00:37:35

Can't connect to Samba shares after upgrading

#2 2011-09-07 02:48:18

Re: Can't connect to Samba shares after upgrading

#3 2011-09-07 07:54:03

Re: Can't connect to Samba shares after upgrading

#4 2011-09-08 23:41:17

Re: Can't connect to Samba shares after upgrading

#5 2011-09-09 21:19:40

Re: Can't connect to Samba shares after upgrading

#6 2011-09-21 16:20:31

Re: Can't connect to Samba shares after upgrading

#7 2011-09-21 18:17:25

Re: Can't connect to Samba shares after upgrading

Board footer