*** This bug is a duplicate of bug 95452 ***
https://bugs.launchpad.net/bugs/95452
** Changed in: samba
Status: Unknown => Confirmed
--
samba 3.0.24 on feisty is broken - msdfs proxy option broken
https://bugs.launchpad.net/bugs/95460
You received this bug notification because you are
*** This bug is a duplicate of bug 95452 ***
https://bugs.launchpad.net/bugs/95452
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, this bug is a duplicate of bug 95452 and is
being marked as such. Feel free to submit any future bugs you may find.
Reopening as 3.0.26a has the same problem:
Define a share:
[tmp]
path = /tmp
$ smbclient //gutsy-server/tmp
Password:
Domain=[GUTSY-SERVER] OS=[Unix] Server=[Samba 3.0.26a]
smb: \>
Add msdfs proxy option:
[tmp]
path = /tmp
msdfs proxy = no
Restart samba.
$ smbclient //gutsy-server/tmp
Btw the msdfs proxy made absolutely no difference for me.
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubun
BAD realtek 8169 module
Hi Everyone, I hope this helps.
I had a similar problem on Feisty ( 2.6.20-15-generic and 2.6.20-16-generic)
with SAMBA going REALLY REALLY slow.
Tried alll sorts of smb.conf tweeks.. no luck.
However I noticed that SAMBA access would go fa
Thanks for your work Alexey!
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.c
Thanks taking the time to report this bug and helping to make Ubuntu
better. However, I am closing it because the bug has been fixed in the
latest development version of Ubuntu - the Gutsy Gibbon. The msdfs proxy
option has been fixed in 3.0.25.
** Changed in: samba (Ubuntu Feisty)
Importance:
The related kde bug is already mentioned in this thread/bug.
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.u
Take a look at
http://git.altlinux.ru/people/morozov/packages/?p=kdenetwork.git;a=commit;h=68a44da45c0820965b0929159be00a176f11d253
The patch kdenetwork-3.5.7-alt-msdfsProxyType.patch solves the problem
(well, at least at first glance :-)). If the patch can be applied to
Ubuntu kdenetwork package,
I simply upgraded from Edgy to Feisty and lost the functionality of
samba. And all I had was simple shares that were all public (security =
share).
Now, a lot of posts mentioned that removing "msdfs proxy = no" from
smb.conf did the trick. In my case, however, there was no "msdfs proxy =
no" in my
Sorry for the exclusion, pclinuxos ships samba vers. 3.0.23b.
@fbusse I still think it is a mix of both, Kubuntus interpretation of kde and
samba (shiped with kubuntu 7.04 as of today 3.0.4)
As stated it worked in edgy and it works in pclinuxos 2007. So I think
this is a kubuntu issue.
--
samba
Chris, I admit that I would stop insisting, too, were I kinda sure this
erraneous behaviour would not be generated again because KDE was fixed.
But as far as I have followed the discussion, the initial action in fact
was a change in samba, making it more sensitive to an obvious
misconfiguration wh
I must correct myself. As soon, as you are using "security options" i.e. hosts
allow, the3 msdfs proxy is used again...
sorry for my misleading success-story abov...
[stuff]
path = /path/stuff/
case sensitive = no
strict locking = no
msdfs proxy = no
hosts allow = 192.168.1.0/24
--
samba 3.0.2
Finally, I can confirm, that kcontrol has been updated here, and new shares do
only get the following:
[stuff]
path = /path/stuff/
guest ok = yes
That issue is resolved for me. Can someone else test it also?
As always, it needs some time, but bugs are still fixed a lot faster in the
organic comm
As in every bug, it's most important to specify versions of the
applications. As we are discussing this bug in a (k)ubuntu forum, we
have no clue what version of samba and kde pclinuxos2007 ships.
For your information, Edgy doens't suffer from this bug and ships with
samba 3.0.22 and kde 3.5.5.
-
I am not so sure it is strictly a kde issue. I just did a test install
of pclinuxos 2007 and all the kde ->samba configuration tools are
behaving as they should. So maybe it is a kubuntu->kde issue.
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug no
You're right, KDE should be blamed for misconfiguring samba.
But samba should kindfully ignore OBVIOUS misconfiguration!
(Or would "no" ever be judged a valid network path to a CIFS share?)
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug notificat
Just to keep pooring info in this bug. This is the related KDE bug:
http://bugs.kde.org/show_bug.cgi?id=137577
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
Error still persists in today's upgrade to samba_3.0.24-2ubuntu1.2.
(Temporaryly inserted the "msdfs proxy" line for testing purpose.)
Would be interesting to know if anybody from the samba team only
recognized this bug: Still not assigned to nobody, importance still
"undedided", status on "needs
In the interest of getting the status moved up from "needs info", I just want
to add that I ran into this exact problem too. I have a mythtv server/file
server that I've samba'ed with other windoze and linux systems in my home.
Everything was fine until I upgraded from edgy to feisty, when I sta
I'm pretty disheartened that this bug is still characterized "needs
info" on the top. To synthesize the comments (and my own experiences):
1. Samba as released on Feisty doesn't play nicely with the values
"msdfs proxy = yes" or "msdfs proxy = no" in smb.conf. Boolean values
appear to be illegal f
Confirmed. Problem persists (I was so hoping, that the samba upgrade was
in order to fix this annoyance). Anyway, maybe the problem should be
solved on the configuration-creating side (KDE configuration tools
o.e.)?
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You rec
For good order: I noticed Samba (and friends) 3.0.24-2ubuntu1.1 slipping
into Feisty yesterday (coming from 3.0.24-2ubuntu1) and can confirm that
the problem still exists in this update.
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug notification b
Bingo, I've been affected also (cost me some gray hair). I auto-upgraded
from edgy to feisty and am running into this exact problem. It's present
in Samba version 3.0.24-2ubuntu1.1. Commenting out line "msdfs proxy =
no" resolves the issue.
--
samba 3.0.24 on feisty is broken
https://bugs.launchp
The downgrade was a first test to see if I could pinpoint it to package
versions and provide a quick 'n dirty workaround.
It turns out this is true, but also that the 'msdfs proxy' line is the (my)
problem, so we could pretty safe say that Feisty's samba just doesn't
gracefully ignore the 'misco
Kalinda, did you look for a line "msdfs proxy = no" in your smb.conf,
removed it and did a "sudo /etc/init.d/samba restart" and your problem
remained? Then this might be a different issue.
Concerning downgrading, mrvanes said on 2007-03-24: "Downgrading samba,
samba-common, smbclient and libsmbcl
Er.. right... just adding something...
I have the same problem. In Edgy, when I installed, Samba immediately
saw my workgroup with just samba-common installed.. then I used the KDE
gui to share my files and everything worked like a snap.
This time, it sees nothing until I install Samba, at which
Hmm... maybe Mark Shuttleworth should hire more people at launchpad to address
those issues ;-) Seriously, this is my opinion. But then we end up having a
SuSE like distribution (which is not bad at all, but does not have the same
free-world feeling as ubuntu does atm).
It's true, as a linux-s
Chris, Ubuntu has come with a claim that was new to me (I'm no primer to
Linux, too) when looking on Linux, where I was used to it as Windoze
user for long: Simplicity to use. Period. Not only for some freaks but
for the typical user who just desperately believes he will really get
what he sees. An
Hey chris, thanks for the message. and I agree to a point. I just know a
lot of people that want to go on in life and like/love the
linux/kubuntu/ubuntu, etc environement. But why, if it works in beta (or
previous distro) doesn't it (the same config) work in the next one.
Samba is important (albigh
Trust me Fred, I am a 10-year linux user/admin. If you like to use
servers (like samba) you still do not get around doing stuff in
configuration files by hand and learn about it. It lies in the design of
linux. But that "hassle" comes with an advantage: It's far more secure
than if you just click-s
You are perfectly welcome for the comments and suggestions. The question
remains. How did this get past beta? I and many others posted comments,
questions and frustrations, here and on the forums (kbuntu for me) Please??
This is not as samll (we can forget about it for now, someone will solve it
Lithium: Thanks for your comments. I can understand your frustration,
but you can be assured that everybody here tries very hard to
participate in building a stable high-quality distribution. You are
invited to make suggestion how to fix this bug or provide solutions for
it if you like. In any case
** Changed in: samba (Ubuntu)
Assignee: Ralph Janke => (unassigned)
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
I'd like to know how this kind of problem made past beta and into the
release of Kubuntu...and how many weeks has it been since the release
with this problem STILL URESOLVED?!?! I know we're talking about open
source software here but I've installed 2 previous versions of Kubuntu
and never saw suc
I can duplicate where running the GUI config tools for SAMBA creates
"msdfs proxy = no". If I manually comment the line and restart the
server, I still can't connect. The Samba client doesn't work either. I
had both the client and server running smoothly on Edgy.
--
samba 3.0.24 on feisty is b
I can definitely confirm, that
msdfs proxy = no
ALREADY WAS in my smb.conf before (I have incr. backups for 6 months). So the
new samba server does not seem to like it. I never heard of this option before
and google for "msdfs proxy samba" does not come up with helpful stuff.
--
samba 3.0.24 o
I cannot confirm not having had this line before the upgrade (because I
have no backup from the Edgy files). The information that the line only
came with Feisty was a hint from a previous discussion after I noted
(from the file date) that something obviously had touched the smb.conf
during the upgr
That line was in my edgy smb.conf. but it worked there. In feisty i had
to uncomment it (thanks guys) but to get RW permissions i had to unmount
all shares, reboot, remount all shares wth RW and reboot. This is not
Samba, but something else. I did a fresh install on a virgin partiton
with a new use
Have you ever used the GUI in Edgy? Are you sure the msdfs line was not in your
Edgy configuration before upgrade?
Edgy's samba 3.0.22 not susceptible to this "msdfs proxy" bug. I know for sure,
because it is in my smb.conf as well and I have a working samba on my Edgy
laptop here.
--
samba 3.
This bug definitely is not related to samba configuration by some GUI,
only: I did not use any samba GUI, just upgraded from Edgy to Feisty and
got that "msdfs proxy = no" line in my smb.conf!
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug notifica
fbusse, the package is not unknown. At least I can prove that Konqueror (but
probably also kcontrol's) samba GUI adds this option.
And yes I agree that samba should gracefully ignore misconfigurations in
smb.conf. My point is that Feisty is a collection of tools that should work
together well wh
I had this problem as well. Commenting out the instances of "msdfs
proxy = no" worked for me. Thanks!
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
u
I think it indeed is the same problem an in 90950: The samba share
cannot be accessed from a windows machine either. (Checked from a
virtual machine.)
But I'm unsure if it is really samba that were to be blamed: The
smb.comf manpage
(http://de.samba.org/samba/docs/man/manpages-3/smb.conf.5.html) s
I don't know if it is just the gui. I copied my edgy smb.conf over to feisty
without touching the gui and had the same problem.
commenting out the msdfs line did the trick though.
--
samba 3.0.24 on feisty is broken
https://bugs.launchpad.net/bugs/95460
You received this bug notification because
Yes, the bug is still in the released version and it's even worse: it
doesn't matter what "msdfs proxy" is set to (yes/no), as long as the
variable is present, the problems persists. Only commenting out the line
resolves the problem. I can reproduce the gui's behaviour every time I
go into the "mor
Thanks for your bug report.
Since feisty is released now. Have you been able to test if your problem
is still current?
If not I would like to close this report.
If it is still current, is this the same problem as 90950?
Thanks
** Changed in: samba (Ubuntu)
Assignee: (unassigned) => txwiki
A fresh install and some debugging revealed the following:
The samba share gets broken after the 'advanced' interface in konqueror's
directory sharing properties has been used, and the reason is it adds:
case sensitive = no
strict locking = no
msdfs proxy = no
and a slash to the end of the path
Downgrading samba, samba-common, smbclient and libsmbclient to Edgy's
3.0.22-1ubuntu4.1 resolves the problem.
--
samba 3.0.24 on feisty is broken
https://launchpad.net/bugs/95460
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
49 matches
Mail list logo
