Samba 2.0.7 problems (on RedHat 7.0)

[Dimitrie Paun]

> From: Urban Widmark [mailto:urban at teststation.com]
> 
> On Mon, 29 Oct 2001, Dimitrie Paun wrote:
> 
> > Linux version 2.2.16-22enterprise 
> (root at porky.devel.redhat.com) (gcc version
> > egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 SMP 
> Tue Aug 22 16:29:32
> > EDT 2000
> 
> 2.2.16 is old ...

I know, that's why I've upgraded to RedHat 7.2 yesterday:

Linux version 2.4.7-10enterprise (bhcompile at stripples.devel.redhat.com) (gcc
version 2.96 20000731 (Red Hat Linux 7.1 2.96-98)) #1 SMP Thu Sep 6 16:48:20
EDT 2001

However, it did not fix the problem:
smbfs: Unrecognized mount option noexec
smbfs: Unrecognized mount option noexec
smbfs: Unrecognized mount option noexec
smbfs: Unrecognized mount option noexec
smbfs: Unrecognized mount option noexec
smb_trans2_request: result=-104, setting invalid
smb_lookup: find //My Documents failed, error=-5
smb_lookup: find //My Documents failed, error=-5
smb_lookup: find //My Documents failed, error=-5
smb_lookup: find //My Documents failed, error=-5
smb_lookup: find //My Documents failed, error=-5
smbfs: Unrecognized mount option noexec
smb_trans2_request: result=-104, setting invalid
smb_lookup: find //My Documents failed, error=-5
smb_lookup: find //My Documents failed, error=-5
smb_lookup: find //My Documents failed, error=-5
smbfs: Unrecognized mount option noexec
smb_trans2_request: result=-104, setting invalid
smb_lookup: find //My Documents failed, error=-5
smb_lookup: find //My Documents failed, error=-5
smb_lookup: find //My Documents failed, error=-5
smbfs: Unrecognized mount option noexec
smb_trans2_request: result=-104, setting invalid
smb_lookup: find //My Documents failed, error=-5
smb_lookup: find //My Documents failed, error=-5
smb_lookup: find //My Documents failed, error=-5
smbfs: Unrecognized mount option noexec

BTW, RedHat 7.2 runs samba 2.2.1b:
[root at vangogh cellbucks]# rpm -q samba
samba-2.2.1a-4

I do not understand why it complains about the noexec option. Here is my
fstab:
[root at vangogh cellbucks]# cat /etc/fstab
LABEL=/                 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
/dev/cdrom              /mnt/cdrom              iso9660 noauto,owner,ro 0 0
/dev/fd0                /mnt/floppy             auto    noauto,owner    0 0
LABEL=/tmp              /tmp                    ext3    defaults        1 2
LABEL=/usr              /usr                    ext3    defaults        1 2
LABEL=/var              /var                    ext3    defaults        1 2
none                    /proc                   proc    defaults        0 0
none                    /dev/shm                tmpfs   defaults        0 0
none                    /dev/pts                devpts  gid=5,mode=620  0 0
/dev/sda8               swap                    swap    defaults        0 0
/dev/sda2               /home                   ext3    defaults        1 2
//intranet/DBS_D        /mnt/intranet           smbfs
user,username=cellbucksdev,password=in4mation           0 0

> > smb_trans2_request: result=-32, setting invalid
> > smb_lookup: find //My Documents failed, error=-5
> > smb_lookup: find //My Documents failed, error=-5
> 
> ... and these are known effects of bugs in 2.2.16 (and samba 2.0.x).
> 2.4.x should be a lot better (as should samba 2.2.x).
> 
> -5 is -EIO, and you get that when a connection is down.

Thanks. It seems that it occurs after smb_trans2_request reports an error,
which makes sense. What is 

smb_trans2_request: result=-104, setting invalid

telling us? That the remote system disconnected? (if I understood correctly
from some posts on the net). If so, can it be the Win2K autodisconnect
feature at work here?

Thanks,
Dimi.