[Samba] smbclient 3.2: smbc errno NT_STATUS_OK -> 22

As I was upgrading other things, the Debian package management system required me to upgrade Samba, from 3.0.24-6 to 3.2.0-4.

All the sudden it quit working, which means I can't run an smbget or smbclient will allow DIR and CD but not GET. Either way with the new version I get (debugging on at level 10)
smbc errno NT_STATUS_OK -> 22
followed by
Can't read 64000 bytes at offset 0, file smb://...
Am I the only person still downloading files from Win'98 shares?

I tried downloading & compiling the latest version from samba.org (3.2.2) and it seems to have the same difficulty. Then I downloaded and compiled the older version posted there (3.0.31) and that works, same as it used to. Also fortunately it seems I can use it without having to install it, so the package management system doesn't have to be out of sync with what's installed, nor do I have to downgrade.

Hopefully someone could point out a ./configure or runtime configuration step that I missed for interfacing with the Win98 shares, using samba 3.2, otherwise it seems like a bug from my perspective.

thanks
Collin Monahan



--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba

On Thu, Aug 21, 2008 at 08:41:38PM -0700, Collin Monahan wrote:
> As I was upgrading other things, the Debian package
> management system required me to upgrade Samba, from
> 3.0.24-6 to 3.2.0-4.
>
> All the sudden it quit working, which means I can't run an
> smbget or smbclient will allow DIR and CD but not GET.
> Either way with the new version I get (debugging on at
> level 10)
> smbc errno NT_STATUS_OK -> 22
> followed by
> Can't read 64000 bytes at offset 0, file smb://...
> Am I the only person still downloading files from Win'98 shares?
>
> I tried downloading & compiling the latest version from
> samba.org (3.2.2) and it seems to have the same
> difficulty. Then I downloaded and compiled the older
> version posted there (3.0.31) and that works, same as it
> used to. Also fortunately it seems I can use it without
> having to install it, so the package management system
> doesn't have to be out of sync with what's installed, nor
> do I have to downgrade.
>
> Hopefully someone could point out a ./configure or runtime
> configuration step that I missed for interfacing with the
> Win98 shares, using samba 3.2, otherwise it seems like a
> bug from my perspective.

This *could* be related to bug 5707. Can you please send me
a sniff of that?

tcpdump -i eth0 -n -s 1500 -w /tmp/sniff.cap

should do the trick, please send me /tmp/sniff.cap.

Thanks,

Volker

--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFIrm5IUzqjrWwMRl0RAjjuAJ9lafiXQ0ErYT5m91jvgg 3K9rEvgwCgmEf2
5174VAyRTJ8SBSKVxbfii8g=
=At43
-----END PGP SIGNATURE-----

On Fri, Aug 22, 2008 at 10:41 AM, Collin Monahan <cmonahan@yahoo.com> wrote:
> Hopefully someone could point out a ./configure or runtime configuration step that I missed
> for interfacing with the Win98 shares, using samba 3.2, otherwise it seems like a bug from
> my perspective.

May be it is due to encrypted password by default and later samba
version. Try to add below lines in smb.conf under global section

lanman auth = yes
client NTLMv2 auth = no
client plaintext auth = yes
client lanman auth = yes

It works for me.

Regards,
David
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba