Simplifying:
1) older smbfs/smbmount had a bug: they didn't support DFS (which Windows
clients do, and Linux cifs client does) which is a critical feature of the
protocol in multiple server environments
2) Windows does not support Unix Extensions
Samba server introduced a bug (long since
As usual in the Linux world we see a lot of dodging and ducking and
passing the buck and pretending that something other than Ubuntu is the
problem. The bug ticket has been marked as Invalid, and yet the
problem is clearly still here and has not been fixed.
If you try to use smbmount (ie-
Andrew: I'm no Ubuntu dev but I've been suffering this bug when first appeared
and the bug is clearly and without any doubt on the Samba server side. With
Samba server I don't mean upstream Samba code but the Samba server present for
example in Debian Etch (and other OS/devices too, like your
I can confirm having the same problem with an Apple Time Capsule. I do
not know how to get it to display files or prompt for authentication. I
only get a blank window with 0 items.
ii samba2:3.3.2-1ubuntu3
SMB/CIFS file, print, and login server for Unix
I'm running Samba on a Linksys/Cisco NSLU2 (the slug!) and started
having this problem after upgrading my client from 8.04 to 8.10. Just
wanted to report that the nodfs mount option took care of the problem
for me. Thanks everyone for all the work figuring this out!
--
Access to samba
I think it's related to the Samba version in use on Time Capsule:
# cat /proc/fs/cifs/DebugData
Display Internal CIFS Data Structures for Debugging
---
CIFS Version 1.54
Active VFS Requests: 0
Servers:
1) Name: 192.168.0.2 Domain: SM-HOME Uses: 1
i found that when i used the msdfs root = no option on my samba 3.0.24
server running debian etch, it caused my windows clients that have
shares mapped to network drives to stop working and i couldn't access
them by \\server\share. in order to get it working on my windows xp
computers, i had to
Marking verification-done following Vide/mipper/Tom reporting success.
** Tags added: verification-done
** Tags removed: verification-needed
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
https://bugs.launchpad.net/bugs/286828
You received this bug notification because
Symptom: When mounting remote CIFS shares from my Apple Time Capsule
(either by /etc/fstab or mount command) I would only see around 150 of
the 5000 directories in my Media folder.
Also, redirection from stdout to a file would work when the file was
created, but appending would not work.
so:
%
I was affected by this problem as well and I can confirm that using
2.6.27-11 and the nodfs mount option the problem is solved. I tested
this on x86 and x86_64.
I can add that with the -9 kernel the
/proc/fs/cifs/LinuxExtensionsEnabled workarond wasn't working anymore
(with previous revisions it
I can confirm the fix too. Doesn't work without nodfs, does with.
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
https://bugs.launchpad.net/bugs/286828
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in
After adding nodfs to my kernel at boot time did NOT change anything.
My MS Windows shares that use to mount automatically under 8.04 still do
not mount automatically after adding that option. Yet, after boot, I can
issue sudo mount /shares/windows_f and the share is mounted without
incident
Tom: nodfs is not a kernel boot parameter. It's a CIFS mount option,
you should add it to your /etc/fstab (only) for mounts targeting the
affected servers.
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
https://bugs.launchpad.net/bugs/286828
You received this bug
It did not work for me as a mount parameter.
To recap:
1) When both the client and server were Ubuntu 8.04 the boot-time CIFS
mounts on the client just worked. See my post above for fstab entries.
2) Upgraded client to 8.10, boot-time CIFS mounts stopped working,
although can still get to the
Thank you for the clarification, Thierry. I changed my fstab entry like
this:
//192.168.4.10/NetworkShare /shares/windows_f cifs
nodfs,auto,rw,credentials=/root/.creds,uid=ttwaro,gid=ttwaro 0 0
and rebooted. Still does NOT work. However, when manually running sudo
mount /shares/windows_f I now
On Tue, Dec 23, 2008 at 5:54 AM, Tom ttw...@gmail.com wrote:
After adding nodfs to my kernel at boot time did NOT change anything.
My MS Windows shares that use to mount automatically under 8.04 still do
not mount automatically after adding that option. Yet, after boot, I can
issue sudo mount
I have just upgraded to kernel 2.6.27-11-generic and running nodfs
as a mount option as previously posted. I no longer get the error
message but the mount still does not happen automatically during/after
boot. I still need to mount the share manually. This worked every time
in 8.04 and 7.10.
Steve:
I still wonder if it's a timing issue, i.e., if there was a subtle
change in services start order or else in the time it is taking
networking to completely come up? That could explain why (a) it worked
in 8.04 but not in 8.10, and (b) after the boot is complete and issuing
a mount command
I tried this but it didn't work. Isn't this for nfs fstype only? I have
CIFS. I could be misunderstanding something, though.
Vide wrote:
Tom, but your mount at bootime issue it's a completely different topic
(do you put the _netdev label in the fstab options? it's mandatory for
network
One more thing, this is on my laptop connecting wirelessly to the
shares. This worked perfectly EVERY time under 8.04 but never has worked
under 8.10. I'm sure it is a timing issue (waiting for the wireless
connection) but it had to do this under 8.04 too.
To reiterate:
* Window XP share
*
Could those affected by the bug test that mounting with the nodfs
mount option on the current kernel in intrepid-proposed works around the
issue ? Thanks.
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
https://bugs.launchpad.net/bugs/286828
You received this bug
Accepted into intrepid-proposed, please test and give feedback here.
Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken
@Skokie
Thanks very much for this tip. That's sorted me out nicely.
I've contacted D-Link regarding a firmware fix for this issue and
received the following reply:
A firmware is being develop, we don't have an ETA or upgrades that it
will have, i invite you to go to forums.dlink.com, you can
I can confirm that upgrading the server-side to Samba 3.2.5 fixed the
issue.
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
https://bugs.launchpad.net/bugs/286828
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba
Thank you to all who have taken the time to investigate! The DNS323
suffers from this server side DFS bug but it is possible to work around
it!!!
Connect to the DNS using the web GUI and goto tools-system.
In this page you can save the configuration to your workstation.
After saving edit the
So to summarize your summary,
if you don't have any control over the server - which was running fine
with the 8.04 client - you're stuffed! I don't understand how a bug in
the server is causing something that works under 8.04 to stop working
under 8.10, and I really can't understand why fixing
mipper:
This is a bug about servers claiming they support something that they don't. If
client stuff makes use of that something and trust servers to properly
implement what they claim they do, it doesn't work. It happens that the client
stuff in Intrepid takes advantage of those advanced
To follow up on mipper's point, here's what I don't understand:
1) My server is Ubuntu 8.04, currently patched.
2) I upgraded my workstation from 8.04 to 8.10 and lose the ability to
have my CIFS shares on the server mounted automatically at boot time as
they were right up until I upgraded.
3)
Thanks for the clarification, Thierry. I am, alas, in the last position, so
am very interested in knowing when the new kernel will be published. I
can't find any target dates on this bug report and it's the lack of any
visibility on when the fix might be released that's so frustrating. How
does
mipper:
According to the kernel team, the patch is still in the pipeline. It /should/
appear in the next kernel published in intrepid-proposed.
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken on 8.10
https://bugs.launchpad.net/bugs/286828
You received this bug notification because
Forgive my ignorance here, but I can see that there appears to have been
a fix committed for this bug, but I can't see when or how it's going to
be released. This is an absolute show stopper bug as far as I can see,
so how and when can I get a fix for it?
--
Access to samba 3.0.24-3.0.25 shares
Just to summarize again:
1) A few versions of Samba server had a bug parsing DFS paths (fixed
in Samba server 3.0.26). You can see which version of server you have
mounted to by doing cat /proc/fs/cifs/Debug
Data on the client). When the Linux CIFS client added support for
DFS last year, those
I just installed the new kernel (2.6.27-9-generic x86_64), but this fix
doesn't seem to have made it in there yet. nodfs seems to be an unknown
mount option for cifs.
Any indication as to which update will have this fix?
Thanks,
--
Access to samba 3.0.24-3.0.25 shares using CIFS is broken on
A warning about the msdfs root = no workaround: This broke some of the
drive mappings on Windows clients. Shares that are mapped via NET USE
(like in a logon script) don't seem to be affected - a name is a name -
but connections manually set up through the GUI seem to store some
additional
Another workaround: set msdfs root = no on affected shares or in the
[global] section of smb.conf. If you don't use DFS at all you can also
disable it completely with host msdfs = no.
This also made UNIX extensions finally work. Note that I had to remount
all shares to get things working. I don't
Can confirm the bug on 8.10 with a samba server on Debian etch.
Disabling DFS solves it.
Display Internal CIFS Data Structures for Debugging
---
CIFS Version 1.54
Active VFS Requests: 0
Servers:
1) Name: x.y.z.a Domain: EITELWEIN Mounts: 7 OS: Unix
SRU Justification
Impact: see bug description
Patch Description: add a nodfs mount options that forces a share to be used
with non DFS paths, even if the server claims, that it supports it.
Patch: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
37 matches
Mail list logo