smbd[16093]: matchname failed on 192.168

Status
Not open for further replies.

Christian_128

Dabbler
Joined
Jan 13, 2015
Messages
43
Hi
I know is not the first tread on this forum about the error : matchname failed on X.X.X.X

Until many month I try when I have loose time, to resolve this "problem" on my freenas box, each 10 second:
"smbd[16095]: matchname failed on 192.168"
I try to found solution on this forum, and on the web with my "friend"google. Each time I found the same resolution :
"Disable host name lookup in cifs should do the trick. " and
" Figured it out. Services>CIFS>CIFS Settings. Uncheck the Hostnames Lookup box. "


After make this chamgement on my box, I have other message each 10 second :
"connectionsreceive_smb_raw_talloc failed for client ipv4"

In the past I found solution, editing manually a file, and the message stop. the only thing is, I not keep this solution on my note and I not found them again:(. I read in other post that is not a good idea to edit manually smb.conf


Today I decide to post this kind of problem on the forum, because I not found a solution for stop messages in my system.

this is waht I have , modiffication on CIFS service and message associate on the system:
FreeNAS-9.3-STABLE-201511040813 ( with all update)
Platform Intel(R) Xeon(R) CPU L5420 @ 2.50GHz
Memory 32741MB
-=-=-=-=-=-=-=-=-=-
normal config of the system
upload_2015-12-4_15-8-34.png


Dec 4 14:01:07 Serveur1 smbd[16093]: matchname failed on 192.168.1.51
Dec 4 14:01:17 Serveur1 smbd[16094]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 192.168.1.51 != (NULL)
Dec 4 14:01:17 Serveur1 smbd[16094]: [2015/12/04 14:01:17.243951, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Dec 4 14:01:17 Serveur1 smbd[16094]: matchname failed on 192.168.1.51

-=-=-=-=-=-
I remove Hostnames Lookups :
upload_2015-12-4_15-9-36.png


Dec 4 14:10:09 Serveur1 smbd[17427]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsreceive_smb_raw_talloc failed for client ipv4:192.168.1.51:59628 read error = NT_STATUS_CONNECTION_RESET.
Dec 4 14:10:19 Serveur1 smbd[17443]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsreceive_smb_raw_talloc failed for client ipv4:192.168.1.51:59629 read error = NT_STATUS_CONNECTION_RESET.
Dec 4 14:10:29 Serveur1 smbd[17474]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsreceive_smb_raw_talloc failed for client ipv4:192.168.1.51:59630 read error = NT_STATUS_CONNECTION_RESET.

-=-=-=-=-=-
I remove all querry
upload_2015-12-4_15-10-30.png


Dec 4 14:12:20 Serveur1 smbd[17972]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsreceive_smb_raw_talloc failed for client ipv4:192.168.1.51:59643 read error = NT_STATUS_CONNECTION_RESET.
Dec 4 14:12:30 Serveur1 smbd[17976]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsreceive_smb_raw_talloc failed for client ipv4:192.168.1.51:59644 read error = NT_STATUS_CONNECTION_RESET.

-=-=--=-=-=-=-=-=-=-=-=-=

If some one have solution for me, and I thik for many other people too, let me know, it will help me for keep the message system clean.


Regards
Chrsitian :)
 

solarisguy

Guru
Joined
Apr 4, 2014
Messages
1,125
Not an answer yet, a question... To those who know FreeBSD:

if all DHCP clients have reserved addresses, would the problem go away if all machines were listed in /etc/hosts ?
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
Not an answer yet, a question... To those who know FreeBSD:

if all DHCP clients have reserved addresses, would the problem go away if all machines were listed in /etc/hosts ?

I believe that would work. If you're doing that it'd probably be a good idea to go ahead and make an lmhosts file as well. Alternatively, you could run DNS on your local network.
 

Christian_128

Dabbler
Joined
Jan 13, 2015
Messages
43
I make changement on hosts file, after when I check the system messages, I have same message at each 10 sec what I have before, when I uncheck the hostnames lookups

-=-=-=-=-=-=-
the message :

Dec 5 10:39:04 Serveur1 smbd[86636]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsreceive_smb_raw_talloc failed for client ipv4:192.168.1.51:53231 read error = NT_STATUS_CONNECTION_RESET.
Dec 5 10:39:14 Serveur1 smbd[86640]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsreceive_smb_raw_talloc failed for client ipv4:192.168.1.51:53232 read error = NT_STATUS_CONNECTION_RESET.

-=-=-=-=-=-=-

May be the solution is add a DNS server, but add another box (computer) not sure, is the service will existe on my freenas, sure I will use it.

I will continue to search. . .

Thank's :)

Chrsitian
 

anodos

Sambassador
iXsystems
Joined
Mar 6, 2014
Messages
9,554
I make changement on hosts file, after when I check the system messages, I have same message at each 10 sec what I have before, when I uncheck the hostnames lookups

-=-=-=-=-=-=-
the message :

Dec 5 10:39:04 Serveur1 smbd[86636]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsreceive_smb_raw_talloc failed for client ipv4:192.168.1.51:53231 read error = NT_STATUS_CONNECTION_RESET.
Dec 5 10:39:14 Serveur1 smbd[86640]: STATUS=daemon 'smbd' finished starting up and ready to serve connectionsreceive_smb_raw_talloc failed for client ipv4:192.168.1.51:53232 read error = NT_STATUS_CONNECTION_RESET.

-=-=-=-=-=-=-

May be the solution is add a DNS server, but add another box (computer) not sure, is the service will existe on my freenas, sure I will use it.

I will continue to search. . .

Thank's :)

Chrsitian
That error message is unrelated to host name lookups. Please post more complete excerpt of contents of /var/log/samba4/log.smbd.
 

Christian_128

Dabbler
Joined
Jan 13, 2015
Messages
43
When I saw the modiffication on hosts file give to me the same message than before, I delete the line.
Anodos, you ask me to post the log.smbd, but before I add line on hosts file.

I copy the log.smbd file and I joint them, compress in .zip file

I not post the file in text, because is to large and many many repeted line, during this time the activity on the server from unser is nothing, nobody use the server.
 

Attachments

  • log.zip
    1.3 MB · Views: 303
Status
Not open for further replies.
Top