Installed a security update for samba tonight via Opensuse updater.
Now, when trying to access my home network an authentication box pops up (never used to)
Asks me to enter authentication for my home network.
I enter my username and password and hit enter. After a few seconds the authentication box pops up again askingfor the same indicating I have entered the wrong username / password combination (which I know I have not).
Any help please??
hmmmmm . . . .
If I enter smb:/ into konqueror I get the message
Unable to find any workgroups in your local network. This might be caused by an enabled firewall.
What has this security update done to my network? 
Disabling firewall makes no difference.
here is my smb.conf which has not had any changes (at least that I can see)
[global]
workgroup = FARCUSNET
netbios name = markpc
name resolve order = bcast host lmhosts wins
map to guest = Bad User
local master = yes
preferred master = yes
os level = 65
printing = cups
printcap name = cups
printcap cache time = 750
cups options = raw
load printers = yes
use client driver = yes
server string = ""
usershare allow guests = Yes
usershare max shares = 100
usershare owner only = False
[printers]
comment = All Printers
path = /var/tmp
printable = Yes
create mask = 0700
guest ok = Yes
browseable = No
[documents]
comment = Documents on Mark
inherit acls = Yes
path = /home/farcus/Documents
read only = No
[downloads]
comment = Downloads on Mark
inherit acls = Yes
path = /home/farcus/Download
read only = No
[jtv]
comment = Japanese TV
inherit acls = Yes
path = /media/BUFFALO/JTV
read only = No
I have same problem!
I have rolled back the files that were updated in the samba security update and all is well again.
I think I’ll stay clear of this samba update until we get some info on exactly what happened there and how to fix it.
Prev versions of the files that were updated can be found on the Opensuse 11.2 DVD or in the OSS repo
Great you got it back to work again. Did either one of you file a bugreport?
My updater applet just now tells me there’s a new version of “cifs-mount” for Samba. Is that the file that caused the problems for you? (I didn’t install it yet).
Or could it be that this is the problem, see this thread for a behaviour that occurred following an update: [smb] Lost access to shared directory - openSUSE Forums](http://forums.opensuse.org/network-internet/435780-smb-lost-access-shared-directory.html)
Does that explain your problem?
yes, that is the file updater applet advised me of. However, after selecting to install this it seemed to update a number of samba related files as follows
samba-3.4.3-3.2.1
samba-client-3.4.3-3.2.1
cifs-mount-3.4.3-3.2.1
libsmbclient0-3.4.3-3.2.1
libwbclient0-3.4.3-3.2.1
libtalloc1-3.4.3-3.2.1
libtdb1-3.4.3-3.2.1
The other thread noted seems more than likely the same issue - however, no solutions there as yet either.
Are you using shares that include links in the filesystem on the server (wide links)?
I don’t think so. I’m not entirely sure what that even means.
You can see all my shares on the smb.conf above. That’s all there is.
added the updated files again.
ran
testparm -v | grep "wide links"
& reply came back “no”
so have added to smb.conf
wide links = Yes
but has made no difference.
Searching some other distros came across this
https://bugzilla.samba.org/show_bug.cgi?id=6880
this appears to be the problem - a bug introduced in samba 3.4.3 - the very one Opensuse have just added as an update.
There is a patch that has been added to 3.4.4 to fix the problem.
Shouldn’t Opensuse roll back this update, or better yet - update to 3.4.4??
On Fri March 26 2010 03:56 am, farcusnz wrote:
>
> added the updated files again.
>
> ran
>
> Code:
> --------------------
> testparm -v | grep “wide links”
> --------------------
>
>
> & reply came back “no”
>
> so have added to smb.conf
>
> Code:
> --------------------
> wide links = Yes
> --------------------
>
>
> but has made no difference.
>
> Searching some other distros came across this
> https://bugzilla.samba.org/show_bug.cgi?id=6880
>
> this appears to be the problem - a bug introduced in samba 3.4.3 - the
> very one Opensuse have just added as an update.
>
> There is a patch that has been added to 3.4.4 to fix the problem.
>
> Shouldn’t Opensuse roll back this update, or better yet - update to
> 3.4.4??
>
>
farcusnz;
The wide links parameter only allows (or denies) a windows client to follow in
sym links on the server. It has no effect on connecting to Windows shares
from Linux. However, when you tried to authenticate did you use a valid
windows user/password and specify the machine name. You might try to enter
the name in the format <MachineName><Username>. You may need to surround
the whole thing in quotes. For example if you have a Windows machine called
MYLAPTOP and a windows user called fred farcus try using either:
MYLAPTOP\fred farcus or
"MYLAPTOP\fred farcus"
quotes are needed from the command line in order for the name to parse
correctly, I’m not sure about the GUI.
Also try:
smbclient -L mylaptop -U"mylaptop\fred farcus"%bigsecret
where bigsecret is your Windows password (don’t miss the percent sign). This
should give a list of shares on “mylaptop” The command line form works fine
with Samba 3.4.7 on an old 10.2 server and with Samba 3.5.1 on new 11.2
server.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
Yes, I am absolutely certain this problem is not related to the widelinks issue & more to do with the bug introduced in samba 3.4.3 mentioned above.
While the windows client could access the shares on the linux computer, samba seemed to be crippled on the linux side - unable to access shares on the linux or windows computer.
Will be working for you on samba 3.4.7 because a patch was introduced to fix the issue on 3.4.4
On Fri March 26 2010 05:56 pm, farcusnz wrote:
<snip>
>
> Yes, I am absolutely certain this problem is not related to the
> widelinks issue & more to do with the ‘bug introduced in samba 3.4.3’
> (https://bugzilla.samba.org/show_bug.cgi?id=6880) mentioned above.
>
> While the windows client could access the shares on the linux computer,
> samba seemed to be crippled on the linux side - unable to access shares
> on the linux or windows computer.
> Will be working for you on samba 3.4.7 because a patch was introduced
> to fix the issue on 3.4.4
>
farcusnz;
Samba 3.5.1 is available now on the update repository. We are using this on
the 11.2 server.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
which update repo? Opensuse 11.2 Updates repo newest version is 3.4.3 just added a few days ago.
Are you using a factory repo?
On Fri March 26 2010 09:26 pm, farcusnz wrote:
>
> venzkep;2143360 Wrote:
>> On Fri March 26 2010 05:56 pm,
>> Samba 3.5.1 is available now on the update repository. We are using
>> this on
>> the 11.2 server.
>>
>>
>
> which update repo? Opensuse 11.2 Updates repo newest version is 3.4.3
> just added a few days ago.
> Are you using a factory repo?
>
farcusnz:
Look here:
http://download.opensuse.org/repositories/network:/samba:/
You will find binaries for 11.0;11.1 and 11.2 Different architectures are in
separate directories. The doc file is in the noarch directory.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
thanks. Samba 3.5.1 from the stable repo appears to provide a newer version of samba without the problems introduced in 3.4.3 in the Opensuse Update repo.
A good alternative to rolling back to 3.4.2.
I think the update repo maintainers should add 3.5.1 to their repo to replace that nasty surprise they sprung on us a few days ago.