samba - Apr 2000 - smbfs and i/o errors

Hi guys,

I hope I've reached the correct mailinglist. I'm experiencing a problem
with smbfs. You can mount shares, but after a while, the connection is
broken and all sorts of strange stuff happens. I've got a share called
/mnt/ntshare which remotely mounts an NT host:

[arnow@foo /mnt]$ ls
ls: ntshare: Input/output error
cdrom/  floppy/
[arnow@foo /mnt]$
[arnow@foo /mnt]$ dmesg | tail

smb_trans2_request: result=-32, setting invalid
smb_retry: new pid=360, generation=2
smb_trans2_request: result=-32, setting invalid
smb_retry: new pid=360, generation=3
smb_trans2_request: result=-32, setting invalid
smb_retry: new pid=360, generation=4
smb_trans2_request: result=-32, setting invalid
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3
smb_retry: signal failed, error=-3                            

Some stats on the Linux host:

Linux foo.euronet.nl 2.2.15-2.5.0 #1 Sat Feb 5 00:28:02 EST 2000 i686 unknown
(it's a standard RedHat install)

Some stats on the NT host:

NT 4.0 (build 1381) Service Pack6

And the smbmount manual page is for smbfs 2.0.6, 11th of November 1999,
which is the latest version as far as I have been able to find on
www.samba.org.

I've been reading the comp.protocols.smb newsgroup, and found someone that
asked the same question, but he received no reply.

I find it hard to believe that the package is so broken that it just
plainly doesn't work on a vanilla install. Is there something I'm doing
wrong? 

Thanks in advance for taking the time,



  Arno
-- 
EuroNet*Internet BV, http://www.euronet.nl/
Arno van Wouwe, IT department
Muiderstraat 1, Postbus 11095, 1001 GB Amsterdam
T:+31 20 5355262,F:+31 20 5355400, E: arno@nl.euro.net

Arno van Wouwe wrote:
|				 I'm experiencing a problem
| with smbfs. You can mount shares, but after a while, the connection is
| broken and all sorts of strange stuff happens. I've got a share called
| /mnt/ntshare which remotely mounts an NT host:

	For some reason, we've seen a lot of "Windows machine
	has disconnected" issues this year. The common case
	is a client conks out, but someone else reported a
	smbfs problem, too.
	
	These are always hard, as the Windows machines don't 
	always log usefull information: you might try turning
	Samba-side log level up to 3, but the best diagnostic
	is a packet-capture of the sequence that led to the 
	disconnect. If you can reproduce the problem, you might
	put a packet log up for ftp or http transfer...
	
--dave
--
David Collier-Brown in Boston
Phone: (781) 442-0734, Room BUR03-3632