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] 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, |
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.
|
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. |
Where is the previous 3.0.24 package found online? All of the mirrors now have only the 3.0.25 package.
|
|
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. |
The latest Ubuntu Samba package was very quickly replaced with a recompile. It looks like something about the 3.0.25 version is touchy
|
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. ;) |
http://www.frsirt.com/english/advisories/2007/1805 - it would be better to get it quicker.
|
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.
|
3.0.25a came out very quickly, it would appear that 3.0.25 was broken
|
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* |
Yep, there's still issues with 3.0.25a... :/
|
Really? I'm using 3.0.25a now w/o any issue. What sort of problems are you having?
|
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.
|
I'm having some issues as well. I'm using Samba as a domain controller. I've found when users login that they get an error that there settings won't be copied because it can't find the profile share. The solution for this is merely to restart the computer.
I also have random instances of people unable to access their mapped drives. The solution for this is to dissconnect the drive and re-map it. This is rather sloppy when you have multiple users though. Hope this helps someone. |
All times are GMT -5. The time now is 07:30 AM. |