public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Paschka <monkey20181@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Problem with CIFS
Date: Tue, 17 Aug 2004 12:08:25 +0200	[thread overview]
Message-ID: <4121D919.1070205@gmx.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 972 bytes --]

I was trying to use CIFS, but it failed to mount my samba shares whereas 
mounting a share of a Win2K PC worked.

I dowloaded and compiled the newest samba-server, but that didn't help 
either so I investigated a bit.

After googling if someone else was experiencing this problem I became a 
bit iritated because I only found a handful results, none helped to 
solve this problem in any way.

So I narrowed the problem down myself.

In fs/cifs/cifssmb.c around line 238 the cifs modul expects a 16 Byte 
GUID, where samba only send 14 bytes consisting of some random numbers 
followed by my workgroupname: WG.
So I to set my workgroupname to something longer with enabled me to 
mount my share.

I am not sure what the right behaviour is (must cifs accept shorter 
seqenzes or must samba send some dummy bytes to fill up to 16 Bytes), 
but I think it should be possible to mount shares in workgroups which 
names are shorter the 4 Bytes.

Help would be appreciated
Daniel

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

             reply	other threads:[~2004-08-17 10:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-17 10:08 Daniel Paschka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-19  2:36 Problem with CIFS Steve French
2004-08-19 20:28 ` Jeremy Allison
     [not found] <20040818120033.9DD101638C1@lists.samba.org>
2004-08-19 10:09 ` Steve French (IBM LTC)

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=4121D919.1070205@gmx.net \
    --to=monkey20181@gmx.net \
    --cc=linux-kernel@vger.kernel.org \
    /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