2

My FreeNAS box has been acting weird for a while. My log file is filled with the following:

Mar 21 06:57:46 freenas smbd[79405]:   STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: 192.168.0.249 != (NULL)

Mar 21 06:57:46 freenas smbd[79405]: [2015/03/21 06:57:46.036921,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)

I cannot recall for how long this has been the way, but I thought I fixed it a couple of days ago and forgot to check my logs. Obviously I hadn't fixed it.

The issue revolves around host name lookup, which can be disabled via the FreeNAS interface for CIFS. Disabling this solves the issue described above but does not solve the original question: "Why haven't this appeared for as long as I've been running the share?". I have not changed my settings regarding DNS on my LAN but this issue first occurred only a couple of weeks ago.

Improve this question
2
  • What did you do for fixing it? Commented Mar 21, 2015 at 7:11
  • I haven't, I'm here looking for an answer. Commented Mar 21, 2015 at 7:25

1 Answer 1

Reset to default
2

The errors regarding hostname lookups means you do not have DNS configured for your LAN. To get rid of these messages you have to uncheck Hostname lookups on the CIFS settings.

Improve this answer
5
  • Thank you for your response. I did find this idea on FreeNAS's bug site as well but have yet to confirm it. However, this has not been issue before and I have no idea why it has stopped working. Do you know of a way one can dive further into this? Commented Mar 21, 2015 at 8:08
  • I think if you leave it like this, it won't be a problem. Totally benign. Commented Mar 21, 2015 at 8:10
  • 1
    Well, that might be the case, but it doesn't explain why it stopped working all of a sudden. :( Commented Mar 21, 2015 at 8:10
  • You have to provide more info or edit your question. Commented Mar 21, 2015 at 8:13
  • This just hit me. "benign" is relative, it caused permanent high CPU load when any client was connected. High being > 50%. DNS names from my local DNS server are working perfectly (nslookup was doing fine), though disabling hostname lookup did fix it... eventually after restarting the SMB client. SMB+FreeNAS ... Commented Jun 6, 2017 at 17:57

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.