mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexej Davidov <alexej.davidov@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: smbfs errors
Date: Wed, 8 Sep 2004 18:29:04 +0200	[thread overview]
Message-ID: <200409081829.04807.alexej.davidov@gmx.net> (raw)

Hello,

I can't mount shares of some servers since I use kernel 2.6.x. As it works 
with smbclient and also with smbmount on kernel 2.4.x, I assume the problem 
lies within smbfs.

Kernel version: 2.6.8.1
Samba version: 3.0.4
Dist: Debian unstable

I get errors when I try to mount a share from OS/2 4.0:

1) smbmount
everything's fine

2) cd into the mounted dir
smbfs output:
  smb_setup_bcc: Packet too large 4257>4096
  smb_add_request: request [f7298e80, mid=0] timed out! 

3) ls in the mounted dir
smbfs output:
  smb_receive_header: short packet: 0
  smb_add_request: request [f7353e80, mid=1] timed out!
Then ls says: ls: .: Input/output error

4) cd ..
smbfs output:
  smb_get_length: Invalid NBT packet, code 39
  smb_add_request: request [f736be80, mid=2] timed out!

5) umount
everything's fine


Also, it's not possible to mount a share from a server running Samba 3.0.6 on 
Suse with kernel 2.4.21. I get ``smb_add_request: request[xxxxxxx, mid=x] 
timed out!'' all the time, and this time also already when when I try to 
mount.

I can mount shares, however, from other systems, namely all Windows versions 
and OS/2 3.0

If it is of any help, I could also supply samba logs and tcpdump dumps.

Btw: I tried to enable SMBFS_DEBUG and SMBFS_DEBUG_VERBOSE in smbfs' Makefile, 
but that didn't change anything.

Thanks in advance
Alexej

Please cc to my address, as I'm not subscribed to this list.

                 reply	other threads:[~2004-09-08 16:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200409081829.04807.alexej.davidov@gmx.net \
    --to=alexej.davidov@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

all inboxes | Powered by JetHome®