Help: Matchname failed

[avalon60]

I have just upgraded my FreeNas 9.2.1.6 to FreeNAS 9.2.1.8, and on reboot all I am getting is this as an example:

lib/util_sock.c1199(get_remote_hostname)
Oct 18 12:28:14 freenas smbd[6284] matchname failed on 192.168.0.5

The number in square brackets changes by 1 at every try, and the ip address changes from 5 to 4 and back again.

The last ip address for my FreeNAS box was 192.168.0.28, so what is going on?

What can I do to tell freeNAS to look for the correct ip address?

Hardware:
Supermicro MBD-X9SCM-F-O Retail Motherboard (Intel C204 PCH Chipset, SATA, LAN, IPMI, Single Socket)
Intel Core i3 3220 Dual Core CPU 3.3GHz
16Gb kingston ECC Ram
x3 2TB Western Digital 7200rpm NAS drives in a raidz1 pool
x2 1TB Western Digital 5400rpm Green drives in a mirror-0 pool

Thanks

 

[avalon60]

Ok, a quick update here.

I connected a keyboard and pressed return, which briefly gave me a Console Setup menu, but then went back to looping what it was showing before. So I then pressed Return and Pause , which then held the Console Setup menu, and showed the correct ip address of 192.168.0.28.

So panic over, and out of interest why was it just looping? before and showing the said text or lines.

 

[joeschmuck]

This has been covered in many threads in the past. Do a Google Search for "freenas smbd matchname failed" and you will find the solution.

 

[avalon60]

This has been covered in many threads in the past. Do a Google Search for "freenas smbd matchname failed" and you will find the solution.

From 1 link, there was something about a disconnected laptop which had an ip address to which freeNAS was baulking about. The guy reconnected the laptop and that was it.

Now for me the 2 ip addresses which were repeatedly thrown up by freeNAS; I realised that they are the ip addresses of 2 ip cctv cameras I have, but the difference between my situation and the other one, is that the cameras have never been disconnected, although FreeNAS might disagree with me.

I will investigate further.

Just seen another post re similar sort of error?, and one reply said to turn off hostname lookups under services.
When I looked they were enabled or ticked, so I disabled/unticked that option.

 

[joeschmuck]

Just seen another post re similar sort of error?, and one reply said to turn off hostname lookups under services.

That is the fix. It's not what I'd call "ideal" but it does the trick.

 

[avalon60]

Great stuff! Thanks

 

[Chris Dawalt]

I was having the same problem, and this solution (uncheck the "hostname lookup" option in services- > CIFS) fixed it. Thank you!