[linux-cifs-client] mount.cifs share on OS/2 Warp 4 system

[Andreas Grosche]

Trying to get some progress on the long-standing issue of being unable to 
access shares on OS/2 Warp 4 hosts since Samba 3
(cf. https://bugzilla.samba.org/show_bug.cgi?id=1353), following discussion on 
#samba-technical (http://samba.sernet.de/irclog/2008/02/20080217-Sun.log) 
mount.cifs has been found to have the following issues:

It will try to access *SMBSERVER<20> (wildcard) rather than the actual server,
consequently reporting the non-existing host by that name to be down.

Only when specifying servernetbiosname=MYHOST will it actually establish a 
session.

In hindsight, this seems to be the same problem which had already surfaced
with Windows 98 Second Edition according to the following messages:
http://lists.samba.org/archive/linux-cifs-client/2007-September/002276.html
http://lists.samba.org/archive/linux-cifs-client/2007-September/002280.html

With this first issue out of the way, the message returned by mount.cifs 
changes from
mount error 112 = Host is down
to
mount error 95 = Operation not supported

Something else goes wrong at this point, but as the OS/2 share can actually
be accessed through smbclient, I would think this is a starting point for
further debugging based on the subsequent packet captures (not to be
disclosed in public but available to developers for analysis, of course).

In case "mount error 95" is due to a need to send unencrypted credentials, 
how should this be done as the version compiled from today's latest sources
mount.cifs version: 1.10-3.0.28
complains when specifying "-o sec=lanman"
(cf. http://www.nabble.com/Re:--2.6-patch--remove-smbfs-td15188851.html):
mount error 22 = Invalid argument
and all other options documented in the man page just show "mount error 95".

Greetinx/2 ;-)

Andreas Grosche