[Samba] samba 3 - getting rid of some logfile errors

[J. Echter]

Am 07.08.2012 13:16, schrieb Moray Henderson:
>> From: J. Echter [mailto:j.echter at echter-kuechen-elektro.de]
>> Sent: 05 August 2012 20:30
>> Am 01.08.2012 09:17, schrieb Jürgen Echter:
>>> Hi,
>>>
>>> i have a lot of entries in my logs which i can't solve, but
>> everything
>>> works as expected.
>>>
>>> my setup:
>>>
>>> samba pdc - bacula
>>> samba bdc - mule
>>> Ubuntu 10.04-LTS Server
>>> samba 3.4.7
>>>
>>> log file entries:
>>>
>>> Aug  1 08:25:40 bacula smbd[23854]:   canonicalize_connect_path
>> failed
>>> for service alex, path /\\mule\alex
>>> Aug  1 08:25:41 bacula smbd[23854]: [2012/08/01 08:25:41,  0]
>>> smbd/service.c:988(make_connection_snum)
>>> Aug  1 08:25:41 bacula smbd[23854]:   canonicalize_connect_path
>> failed
>>> for service alex, path /\\mule\alex
>>> Aug  1 08:25:44 bacula smbd[24003]: [2012/08/01 08:25:44,  0]
>>> lib/util_sock.c:1498(get_peer_addr_internal)
>>> Aug  1 08:25:44 bacula smbd[24003]:   getpeername failed. Error was
>>> Transport endpoint is not connected
>>> Aug  1 08:25:44 bacula smbd[24003]: [2012/08/01 08:25:44,  0]
>>> lib/util_sock.c:743(write_data)
>>> Aug  1 08:25:44 bacula smbd[24003]: [2012/08/01 08:25:44,  0]
>>> lib/util_sock.c:1498(get_peer_addr_internal)
>>> Aug  1 08:25:44 bacula smbd[24003]:   getpeername failed. Error was
>>> Transport endpoint is not connected
>>> Aug  1 08:25:44 bacula smbd[24003]:   write_data: write failure in
>>> writing to client 0.0.0.0. Error Connection reset by peer Aug  1
>>> 08:25:44 bacula smbd[24003]: [2012/08/01 08:25:44,  0]
>>> smbd/process.c:62(srv_send_smb)
>>> Aug  1 08:25:44 bacula smbd[24003]:   Error writing 4 bytes to
>> client.
>>> -1. (Transport endpoint is not connected) Aug  1 08:26:07 bacula
>>> smbd[24002]: [2012/08/01 08:26:07,  0]
>>> lib/util_sock.c:539(read_fd_with_timeout)
>>> Aug  1 08:26:07 bacula smbd[24002]: [2012/08/01 08:26:07,  0]
>>> lib/util_sock.c:1498(get_peer_addr_internal)
>>> Aug  1 08:26:07 bacula smbd[24002]:   getpeername failed. Error was
>>> Transport endpoint is not connected
>>> Aug  1 08:26:07 bacula smbd[24002]:   read_fd_with_timeout: client
>>> 0.0.0.0 read error = Connection reset by peer.
>>>
>>> any hints how to resolve this?
>>>
>>> thanks
>>>
>>> juergen
>>>
>>>
>> Hi,
>>
>> i resolved this ones by setting smb ports = 139 in smb.conf
>>
>> but i still have this ones:
>>
>> Aug  5 20:55:18 bacula smbd[20419]: [2012/08/05 20:55:18,  0]
>> rpc_server/srv_netlog_nt.c:603(_netr_ServerAuthenticate3)
>> Aug  5 20:55:18 bacula smbd[20419]:   _netr_ServerAuthenticate3:
>> netlogon_creds_server_check failed. Rejecting auth request from client
>> SERVER machine account SERVER$
>>
>>
>> these are only from successfully joined windows 7 machines.
>>
>> the ldap entry, exported as ldif, looks like this for this account:
>>
>> uid=server$,ou=computers,dc=workgroup,dc=local
>> dn: uid=server$,ou=computers,dc=workgroup,dc=local
>> cn: server$
>> description: Computer
>> gecos: Computer
>> gidnumber: 515
>> homedirectory: /dev/null
>> loginshell: /bin/false
>> objectclass: posixAccount
>> objectclass: account
>> objectclass: sambaSamAccount
>> sambaacctflags: [W          ]
>> sambakickofftime: 2147483647
>> sambalogofftime: 2147483647
>> sambalogontime: 0
>> sambantpassword: 951640BFE27F4C16E7670E096C8121FA
>> sambaprimarygroupsid: S-1-5-21-3842863818-2180709222-141296495-515
>> sambapwdcanchange: 0
>> sambapwdlastset: 1344165203
>> sambapwdmustchange: 2147483647
>> sambasid: S-1-5-21-3842863818-2180709222-141296495-3458
>> uid: server$
>> uidnumber: 1229
>>
>> anyone with some hints? :)
>>
>> thanks
>>
>> juergen
> We use tdbsam rather than ldapsam, but get similar errors when the machine
> name is in lower case in the Linux password database and upper case in the
> Samba password database.  In our case changing the machine's Linux account
> name to upper case cleared several log file errors including
> netlogon_creds_server_check.
>
>
> Moray.
> “To err is human; to purr, feline.”
>
>
Hi Moray,

i just checked and there is no upper-/lowercase issues.

Only Win 7 boxes produce this message.

I have for example server2$ in my ldap and the machine is called SERVER2.

Thanks for helping

juergen.