From: "Christopher R. Hertel" <crh@ubiqx.mn.org>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: linux-cifs-client@lists.samba.org,
Steve French <smfrench@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-cifs-client] Re: SMB support still missing?
Date: Thu, 08 Feb 2007 18:29:38 -0600 [thread overview]
Message-ID: <45CBC072.90102@ubiqx.mn.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0702090101490.24888@yvahk01.tjqt.qr>
Jan Engelhardt wrote:
> Hi,
>
>
> I tried the various suggestions from the last mails, but nothing of
> that worked. --verbose did not return anything useful. It's the kernel
> module that returns -EHOSTDOWN.
>
> ...
>
> Eventually I found out that this one works:
>
> mount.cifs //cl0/c /mnt -o servernetbiosname=CL0
>
> So what did I change? Casing. Note that "CL0" is entirely uppercase.
> Although strange, it actually coincides with how LANMAN works.
> Everything is uppercased in lanman, hostnames, usernames, heck, even
> plaintext passwords (samba-smbd has a good time trying a ton of
> combinations in such setups).
>
> No other options like sec=none or thelike were needed. Login as
> anonymous worked directly.
>
>
> Please consider updating the cifs kernel module to account for the LM
> oddity of uppercasing things. (Then, smbfs can finally be ripped out I
> hope.)
...assuming that's really the problem.
It does seem to me that it is some sort of name resolution issue, but it may
have more to do with the multi-homed nature of your setup.
Did you try:
mount.cifs //CL0/c /mnt
?
If mount.cifs is not converting the case, that should fix the problem.
Curious to know...
Chris -)-----
--
"Implementing CIFS - the Common Internet FileSystem" ISBN: 013047116X
Samba Team -- http://www.samba.org/ -)----- Christopher R. Hertel
jCIFS Team -- http://jcifs.samba.org/ -)----- ubiqx development, uninq.
ubiqx Team -- http://www.ubiqx.org/ -)----- crh@ubiqx.mn.org
OnLineBook -- http://ubiqx.org/cifs/ -)----- crh@ubiqx.org
next prev parent reply other threads:[~2007-02-09 0:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 0:14 Jan Engelhardt
2007-02-09 0:29 ` Christopher R. Hertel [this message]
2007-02-09 0:31 ` Jan Engelhardt
2007-02-09 0:53 ` Christopher R. Hertel
2007-02-09 2:22 ` Jan Engelhardt
[not found] <OFCB86D528.05DE4D00-ON8725727D.000397BF-8625727D.0003B058@us.ibm.com>
2007-02-09 0:58 ` Christopher R. Hertel
2007-02-09 2:18 ` Jan Engelhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45CBC072.90102@ubiqx.mn.org \
--to=crh@ubiqx.mn.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smfrench@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®