connectionsmatchname: host name/name mismatch:

Status
Not open for further replies.

ThePowerTool

Dabbler
Joined
Aug 31, 2012
Messages
31
FreeNAS-9.2.1.9-RELEASE-x86 (2bbba09)

I'm not sure if this is a FreeNAS issue, networking (dnsmasq), or configuration and am hoping someone can give me a few troubleshooting pointers.

From FreeNAS: /var/log/messages:
Code:
Oct 27 14:52:14 freenas smbd[60407]:  STATUS=daemon 'smbd' finished starting up and ready to serve connectionsmatchname: host name/name mismatch: Theater != Theater.local
Oct 27 14:52:14 freenas smbd[60407]: [2016/10/27 14:52:14.150478,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Oct 27 14:52:14 freenas smbd[60407]:  matchname failed on Theater


And from theater:
Code:
[user@Theater ~]$ host theater
theater has address 192.168.1.110
[user@Theater ~]$ host freenas
freenas has address 192.168.1.250


From another box on the same network:
Code:
[user@p7-1456c ~]$ host theater
theater has address 192.168.1.110
[user@p7-1456c ~]$ host freenas
freenas has address 192.168.1.250


Can anyone please give me a pointer on where to start troubleshooting? If other systems were resolving names to host.local (like FreeNAS) then I would start with my dnsmasq server--but that's not the case so I'm not sure where the troubleshooting process starts.

Thanks!
 

Sakuru

Guru
Joined
Nov 20, 2015
Messages
527
Are you unable to reach "freenas" from "Theater"? Or are you just curious about that error message?
 

ThePowerTool

Dabbler
Joined
Aug 31, 2012
Messages
31
Are you unable to reach "freenas" from "Theater"? Or are you just curious about that error message?

I have an infrequent, intermittant "hitching" problem with theater using a FreeNAS mounted drive via CIFS ("intermittant hitching" = "nightmare troubleshooting"). This is the only error I see as it's the most frequent and it's not limited to theater. It throws the same error for other systems, as well.

I've not been fast enough to actually try a ping during a hitch as I'm usually on the couch and well into a movie when it happens (and when I am prepared and check it continues before I can even try a ping or ls via the mounted directory).

That's why I'm starting with this error which I know will be difficult to troubleshoot which is why I'm hoping someone can provide a few tips.

Thank you very much for responding!
 
Status
Not open for further replies.
Top