Gabor Guzmics wrote: >>Do you have a chance to be able to recompile samba yourself. >> >>It turns out this is an upstream bug and Samba developers have >>notified us it is probably fixed now in upstream sources. >> >> >>This needs to use upstream's SAMBA_3_0 source tree in their SVN >>server. > > > should I wait for testing updates, or just compile samba myself (which i hope > isnt too complicated like... say... openoffice :D)... > > Of course, I could - however, using the binaries from debian testing release > indicates, that it should be fixed in the packages ;D > > since i do not use samba in professional ways, I also could downgrade to > 3.0.10 or something like that. > > so just for information: is this bug now open/ verified, or closed and wont be > updated til sarge? I'm a bit confused now! > > >>The smb.conf file is used extensively by both the client and server code. > > > good to know! > do I have any misconfiguration maybe? > I didnt alter much myself, only set to share security, I configured mostly > everything via apt or kde.
I have a standard smb configuration file. From a fresh installation. Can you try with that configuration ? (The shares you have can go into the smb.conf file that doesn't matter, but it has to do with the global options i think.) It seems that it only exist on WinXP with SP1, i did it here with WinXP SP2, but that one don't have any problems. (And badly enough, i don't have a WinXP SP1 machine) Downgrading isn't a big problem look at snapshots.debian.net there are all versions that were released. Please check also the other versions (3.0.11 and up). But according to the samba.org development this problem should be fixed in 3.0.14a and i see that the patch they made is applied to the one we have in testing. Regards, Matthijs Mohlmann
signature.asc
Description: OpenPGP digital signature
