Samba questions

Jeroen Heijungs Jeroen.Heijungs at Het-Muziektheater.nl
Thu Mar 8 09:11:14 GMT 2001


Hi all,

I am rather new to Samba, and I have a few questions at the moment, perhaps
someone can throw some light on these matters.
My Samba version is 2.0.7, running on FreeBSD version 4.2-Stable, clients
are Win95.  The Samba machine has two Nic's, one in the 172.20 network, one
in the 172.22 network, no routing.

thanks very much in advance
Jeroen Heijungs
Het Muziektheater, Amsterdam

-----
First question is about the Socket options in SMB.CONF, Sambe is always
complaining about these:

* If I do set the following options in smb.conf, then I get the errors as
listed when a workstation logs in

   socket options = TCP_NODELAY SO_KEEPALIVE

   [2001/03/08 09:14:07, 0, effective(0, 0), real(0, 0)]
lib/util_sock.c:set_socket_options(154)
     Failed to set socket option SO_KEEPALIVE (Error Bad file descriptor)
   [2001/03/08 09:14:07, 0, effective(0, 0), real(0, 0)]
lib/util_sock.c:set_socket_options(154)
     Failed to set socket option TCP_NODELAY (Error Bad file descriptor)

* If I do NOT set the socket options in smb.conf, then I get exactly the
same errors when a workstation logs in

   [2001/03/08 09:25:25, 0, effective(0, 0), real(0, 0)]
lib/util_sock.c:set_socket_options(154)
     Failed to set socket option SO_KEEPALIVE (Error Bad file descriptor)
   [2001/03/08 09:25:25, 0, effective(0, 0), real(0, 0)]
lib/util_sock.c:set_socket_options(154)
     Failed to set socket option TCP_NODELAY (Error Bad file descriptor)

Why is this, have I done something wrong, or missed something?, and how
important is it exactly?

-----
Second question is about Samba not really responding as I would expect,
when there is a long time between logons (a few hours, it is a test
environment) you get an error message: (sorry the actuel message in in
Dutch, so I do not know if the translation is correct) "The supplied Domain
password is not correct, or the loginserver has enied access". I can try
this a few times and always the same message, so I cannot log in. When I
cancel the login, and afterwards do a login again everything works fine. I
do not change anything on the client or the server in between. 


Samba does write something in the logfiles (again socket's ??):
[2001/03/08 09:42:02, 0, effective(0, 0), real(0, 0)]
lib/util_sock.c:write_socket_data(543)
  write_socket_data: write failure. Error = Broken pipe
[2001/03/08 09:42:02, 0, effective(0, 0), real(0, 0)]
lib/util_sock.c:write_socket(569)
  write_socket: Error writing 4 bytes to socket 6: ERRNO = Broken pipe
[2001/03/08 09:42:02, 0, effective(0, 0), real(0, 0)]
lib/util_sock.c:send_smb(757)
  Error writing 4 bytes to client. -1. Exiting

-----
Third question also about advertising, but I am not sure how much of a
problem this is. In the log files I see a lot of messages like the following:
[2001/03/08 09:25:25, 1, effective(0, 0), real(0, 0)]
lib/util_sock.c:client_name(1010)
  Gethostbyaddr failed for 172.20.3.26
Is this really a problem or a sympton of something wrong?
I don't have WINS turned on, and do not use LMHOSTS.

-----
my SMB.CONF
[global]
   workgroup = LICHT
   netbios name = LICHTSERVER
   server string = TEST %L (Samba %v)
   domain logons = Yes
   name resolve order = bcast lmhosts host wins
   logon script = smblogin.bat
   interfaces = 172.22.1.1/16 172.20.1.14/16
   socket options = TCP_NODELAY SO_KEEPALIVE
   security = user
   min password length = 5
   unix password sync = Yes
   username map = /usr/local/etc/smbusers.map
   hosts allow = 172.22. 172.20.1.12 172.20.3.26
   log file = /var/log/log.%m
   max log size = 1024
   debug uid = Yes
   log level = 1
   load printers = No

[Lichtdata]
   path = /usr/export/samba/Lichtdata
   force group = usergroup
   write list = @usergroup

[netlogon]
   path = /usr/export/samba/netlogon
   write list = myuserid

[Install]
   path = /usr/export/samba/Install
   write list = myuserid
   read list = @usergroup






More information about the samba mailing list