[Samba] Anonymous access to samba server

Thu Mar 21 00:19:06 GMT 2002

Hi List

I've set up a samba server as file- and printserver.
I wan't it allow anonymous access to these to shares so you don't have
to log in with username and password.
Is that possible?

Jacob

> -----Original Message-----
> From: wolfgang.glas at ev-i.at [mailto:wolfgang.glas at ev-i.at]
> Sent: 21. marts 2002 09:12
> To: samba at samba.org
> Subject: [Samba] locking/seek Problems with SuSE-7.3 / samba-2.2.3a
> 
> 
> Dear samba team,
> 
>  This problem report is the same as outlined by Wolfgang Hertz in
> 
> http://lists.samba.org/pipermail/samba/2002-January/064507.html
> 
> His report has been left without reply, so I to post the 
> problem again 
> with a more detailed description of our configuration and what we've 
> already unsuccessfully tried to overcome the problem.
> 
> Our server is configured like follows:
> 
> IBM xSeries server using hardware raid (driver: aic7xxx)
> Netgear GA621 1Gbit fiberchannel network card (driver: ns83820)
> 
> SuSE-7.3
> kernel-2.4.16 (kernel upgrade from SuSE ftp server; default 
> kernel without 
> 64 GB memory support)
> PIII/1. 2 GHz/1GB physical memory
> lvm-1.0.1rc4
> samba-2.2.1a (using oplocks / kernel oplocks)
> 
> Recently switched to a self-compiled samba-2.2.3a.
> 
> The Clients are Windows/2000/Windows XP stations. All Clients are 
> connected via a 1GBit->8x100MBit/s switch, so we could 
> theoretically reach 
> full 100MBit/s for a single client.
> 
> Our shares are using ext3-filesystems, the home partition, which is 
> exported via samba has a size of 70GB and all problem 
> reported are prblems 
> with this share, because it makes over 90% of the samba usage.
> We have all the samba oplocks etc. switches set to their 
> default values.
> 
> Our log file look essentially like the following and we 
> experienced no 
> difference between samba-2.2.1a and samba-2.2.3a:
> 
> [2002/03/20 21:55:56, 0] 
> smbd/oplock_linux.c:linux_release_kernel_oplock(209)
>   release_kernel_oplock: Error when removing kernel oplock on file 
> feap/LD_Pruefung/Berichte/LD2/9543-LD2_T06_Anlage.fm, dev = 
> 3a05, inode = 
> 2883853, file_id = 824. Error was Bad file descriptor
> [2002/03/20 21:56:07, 0] 
> smbd/oplock_linux.c:linux_release_kernel_oplock(209)
>   release_kernel_oplock: Error when removing kernel oplock on file 
> feap/LD_Pruefung/Berichte/LD3/9543-LD3_T06_Anlage.fm, dev = 
> 3a05, inode = 
> 2031647, file_id = 879. Error was Bad file descriptor
> [2002/03/20 21:56:23, 0] 
> smbd/oplock_linux.c:linux_release_kernel_oplock(209)
>   release_kernel_oplock: Error when removing kernel oplock on file 
> feap/LD_Pruefung/Berichte/LD5/9543-LD5_T06_Anlage.fm, dev = 
> 3a05, inode = 
> 1982502, file_id = 934. Error was Bad file descriptor
> [2002/03/20 21:57:12, 0] 
> smbd/oplock_linux.c:linux_release_kernel_oplock(209)
>   release_kernel_oplock: Error when removing kernel oplock on file 
> SV/7000/7508-Prinz_Eugen_Bruecke/7508-SV-Stadt_Plan.fm, dev = 
> 3a05, inode 
> = 1114188, file_id = 954. Error was Bad file descriptor
> [2002/03/20 22:02:55, 0] 
> smbd/oplock_linux.c:linux_release_kernel_oplock(209)
>   release_kernel_oplock: Error when removing kernel oplock on file 
> feap/LD_Pruefung/Berichte/LD_Fotos_ps/9543-LD6_T06_Fotos-2_3.p
> s, dev = 
> 3a05, inode = 2687035, file_id = 1032. Error was Bad file descriptor
> [2002/03/20 23:08:31, 0] smbd/fileio.c:seek_file(53)
>   seek_file: sys_lseek failed. Error was Bad file descriptor
> [2002/03/20 23:08:31, 0] smbd/fileio.c:seek_file(53)
>   seek_file: sys_lseek failed. Error was Bad file descriptor
> [2002/03/20 23:08:31, 0] smbd/fileio.c:seek_file(53)
>   seek_file: sys_lseek failed. Error was Bad file descriptor
> [2002/03/20 23:08:31, 0] smbd/fileio.c:seek_file(53)
>   seek_file: sys_lseek failed. Error was Bad file descriptor
> 
> So, we have two problems:
> 
> The oplock break messages, which don't seem to hurt us, but 
> what really 
> bothers me is the lseek error,
> which occur somehow randomly and lets windows Application starve with 
> messages like 'The data in the file is corrupt' etc...
> 
> My user and I got the impression, that this error occurrs, 
> when loading a 
> file for the first time, so somehow this may be an oplock problem,
> i.e. the application tries to seek in a file during the file 
> is loaded 
> into the clients cache using the oplock mechanism......
> 
> So thanks for any comments or help,
> 
>     Regards,
> 
>      Wolfgang 
> 
> --
> Dr. Wolfgang Glas                        EV-i Informationstechnologie 
> GmbH.
> Geschäftsführer                          Sebastian-Kneipp-Weg 17
> Wolfgang.Glas at ev-i.at                    A-6020 Innsbruck/Austria
> phone: ++43-512-284883-2                 fax: ++43-512-281624-31
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba
> 