Julian: The patch I submitted fixed my problem (see #13 above).
Unfortunately I don't have time tonight to try to reproduce the
situation, and indeed I may not be able to (I'm not sure I have access
to the server anymore). But I can definitely confirm that it was still
fixed in LinuxMint 13 (Ubuntu
I submitted the bug and patch to Samba at:
https://bugzilla.samba.org/show_bug.cgi?id=8055.
** Bug watch added: Samba Bugzilla #8055
https://bugzilla.samba.org/show_bug.cgi?id=8055
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to sam
Here's the patch. I made it on the v3-4-test branch of the Samba git
repository. It seems to also patch the current stable 3.5.8 version. I
hope this helps.
** Patch added:
"0001-Fix-for-servers-that-don-t-put-a-path-separator-at-t.patch"
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/7
My fix for my issue works. As I said, I can't test it against other
servers. Let me know how we should guide this through the Samba team.
Thanks for your help so far!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
http
James: I downloaded the source for Samba 3.5.8, built it, and confirmed
that it had the same problem. So I've been tracing the code. What I see
is that in the function cli_dfs_get_referal in libsmb/clidfs.c two
components of the path are returned: one that doesn't end in a \, and
the other that doe
Sorry for the extra post. VPN's working again. Here's the output of the
smbclient -L command:
Domain=[my-domain] OS=[EMC-SNAS:T5.6.50.2] Server=[my-server]
Sharename Type Comment
- ---
my-share Disk DFS01 root share
Is it a regression ?
Did this use to work properly with a previous release ?
Not as far as I know.
What version of samba packages are used ?
Please give the output of:
dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep
samba
libsmbclient 2:3.4.7~dfsg-1ubuntu3.5 samba inst
James, will do. I may get to it tonight Pacific Time or at the latest
over the weekend.
I've traced the code enough to feel confident that my problem is NOT
related to the authentication issue I mentioned in my original bug
description. I'm currently looking at a path that seems to lose a \
somewh
Does Nautilus use smbclient (or the client library) for sure? Is it
possible that the issue is in the way Nautilus uses smbclient? I'm
prepared to work with someone to find a solution e.g. testing, providing
more info on my situation. We can work bottom up or top down, whichever
you prefer. Just le
