LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   samba problem after recent upgrade (https://www.linuxquestions.org/questions/slackware-14/samba-problem-after-recent-upgrade-555606/)

rignes 05-21-2007 01:54 PM

samba problem after recent upgrade
 
I've applied the latest updates to Slackware 11.0 which includes a security update from Samba 3.0.24 to 3.0.25. After this update I am suddenly unable to access Samba shares that are located on my reiserfs partition, however, the one I have my music on is FAT32 and is accessible fine from my Windows boxes. Before I go to much farther here is my smb.conf:

Code:

[global]
        workgroup = MYDOMAIN
        security = SHARE
        printing = cups
        printcap name = cups
        short preserve case = yes
        preserve case = yes

[printers]
        comment = All Printers
        path = /var/spool/samba
        guest ok = Yes
        printable = Yes
        use client driver = Yes
        browseable = No

[music]
        comment = Music Collection
        path = /mnt/music
        read only = No
        guest ok = Yes

[data]
        comment = Data Drive
        path = /export/samba/data
        read only = No
        volume = Sample-Data-Drive
        guest ok = Yes

[winxp]
        comment = Windows XP
        path = /mnt/winxp
        read only = Yes
        guest ok = Yes

[homes]
        read only = No
        browseable = No

So, the share I am having issues with is the data share. All the other shares work fine as far as I can tell from my Windows systems. homes and data are on reiserfs and music is on FAT32. Winxp is NTFS. It's possible that permissions are causing the issue with the data share but it doesn't make any sense as I've been using the permissions with Samba 3.0.24 perfectly fine for a long while. The only change that I've made is to upgrade to the 3.0.25 package in the 11.0 tree (dated May 14th in the changelog I think). As soon as I rolled back to 3.0.24 things started working normally again.

So, the question after all of this is, does anyone know what changed in 3.0.25 from 3.0.24 that may have caused this?

Thanks,

rworkman 05-21-2007 02:06 PM

I'm not aware of what changed to break this, but you are not the first report I've seen that the 3.0.24 --> 3.0.25 upgrade broke samba. Either way, it seems to be something that will require an update from the samba guys. If you're using it on a trusted LAN, then just roll back to 3.0.24 - that's the simplest solution for now.

rignes 05-21-2007 02:47 PM

Yeah, I rolled back and it's working fine again. Still, I'm very interested in knowing what the difference is between the two. My issue is basically solved (thanks). Even so, if anyone knows what the difference is between 3.0.24 and 3.0.25 that causes this I'd be interested in knowing.

Thanks again.

Woodsman 05-21-2007 08:16 PM

Where is the previous 3.0.24 package found online? All of the mirrors now have only the 3.0.25 package.

Alien_Hominid 05-22-2007 01:15 AM

http://slackware.kobra.lt/slackware-...ches/packages/

pbhj 05-22-2007 07:19 AM

I had a similar problem, my share (on Slack to WinXP) was down.

What got me was that the NAT was also not working.

In the end it turned out to be a lack of executable flag on /etc/rc.d/rc.inet2 . How that happened I don't know, it possibly wasn't the samba update as I tend to do a few updates together and then boot up again the next day.

So, rc.inet2 brings up DNS and ip_forward-ing. So despite spending hours (literally!) trying to get samba up it turned out to just be a little "x" flag. Gah!

HTH.

davidsrsb 05-23-2007 05:07 AM

The latest Ubuntu Samba package was very quickly replaced with a recompile. It looks like something about the 3.0.25 version is touchy

rignes 05-23-2007 06:50 AM

Interesting...

I'll just have to wait until Pat released another 3.0.25 package and see what happens. I think I'll shoot him a quick E-mail just letting him know what happened.

Thanks for the input. ;)

Alien_Hominid 05-23-2007 01:57 PM

http://www.frsirt.com/english/advisories/2007/1805 - it would be better to get it quicker.

Changeling 05-23-2007 02:09 PM

I've had a similar problem with my NAT. I found out you can just manually mount the shares, where as before it did it automatically. I'm using smb4k, by the way.

davidsrsb 05-25-2007 05:48 AM

3.0.25a came out very quickly, it would appear that 3.0.25 was broken

hsrthe4th 05-28-2007 08:45 PM

I am using the current channel and i tried the 3.0.25a version. Same problem.
As soon as i rolled back to 3.0.24 no problems.

Even stranger, my wife using windows xp home can get to all of my reiserfs shares.
*shrugs*

rworkman 05-28-2007 09:07 PM

Yep, there's still issues with 3.0.25a... :/

rignes 05-29-2007 08:42 AM

Really? I'm using 3.0.25a now w/o any issue. What sort of problems are you having?

rworkman 05-29-2007 08:55 AM

I personally am not having any issues with it - even 3.0.25 never gave me any trouble. However, I'm aware of at least two *reliable* reports that some shares do not show up with 3.0.25a. The solution/workaround at this time is to specify the share via its ip address as opposed to name.


All times are GMT -5. The time now is 03:59 AM.