name mismatch errors

Status
Not open for further replies.

nogi

Explorer
Joined
Jul 5, 2011
Messages
74
Firstly, my setup:
Build FreeNAS-9.2.1.2-RELEASE-x64 (002022c)
Platform AMD Turion(tm) II Neo N40L Dual-Core Processor
Memory 8170MB


It's a HP Microserver N54L. Since upgrading to 9.2.x, I've been getting the following errors:
Mar 15 10:37:08 KANDOR smbd[36802]: [2014/03/15 10:37:08.292122, 0] ../source3/lib/util_sock.c:941(matchname) Mar 15 10:37:08 KANDOR smbd[36802]: matchname: host name/name mismatch: 192.168.1.100 != (NULL) Mar 15 10:37:08 KANDOR smbd[36802]: [2014/03/15 10:37:08.292344, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname) Mar 15 10:37:08 KANDOR smbd[36802]: matchname failed on 192.168.1.100 Mar 15 10:38:07 KANDOR smbd[36826]: [2014/03/15 10:38:07.469772, 0] ../source3/lib/util_sock.c:941(matchname) Mar 15 10:38:07 KANDOR smbd[36826]: matchname: host name/name mismatch: 192.168.1.100 != (NULL) Mar 15 10:38:07 KANDOR smbd[36826]: [2014/03/15 10:38:07.470035, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname) Mar 15 10:38:07 KANDOR smbd[36826]: matchname failed on 192.168.1.100 Mar 15 10:38:07 KANDOR smbd[36827]: [2014/03/15 10:38:07.530617, 0] ../source3/lib/util_sock.c:941(matchname) Mar 15 10:38:07 KANDOR smbd[36827]: matchname: host name/name mismatch: 192.168.1.100 != (NULL) Mar 15 10:38:07 KANDOR smbd[36827]: [2014/03/15 10:38:07.530845, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname) Mar 15 10:38:07 KANDOR smbd[36827]: matchname failed on 192.168.1.100 Mar 15 10:38:08 KANDOR smbd[36828]: [2014/03/15 10:38:08.330822, 0] ../source3/lib/util_sock.c:941(matchname) Mar 15 10:38:08 KANDOR smbd[36829]: [2014/03/15 10:38:08.331019, 0] ../source3/lib/util_sock.c:941(matchname) Mar 15 10:38:08 KANDOR smbd[36829]: matchname: host name/name mismatch: 192.168.1.100 != (NULL) Mar 15 10:38:08 KANDOR smbd[36829]: [2014/03/15 10:38:08.331243, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname) Mar 15 10:38:08 KANDOR smbd[36829]: matchname failed on 192.168.1.100 Mar 15 10:38:08 KANDOR smbd[36828]: matchname: host name/name mismatch: 192.168.1.100 != (NULL) Mar 15 10:38:08 KANDOR smbd[36828]: [2014/03/15 10:38:08.331698, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname) Mar 15 10:38:08 KANDOR smbd[36828]: matchname failed on 192.168.1.100 Mar 15 10:38:08 KANDOR smbd[36830]: [2014/03/15 10:38:08.353991, 0] ../source3/lib/util_sock.c:941(matchname) Mar 15 10:38:08 KANDOR smbd[36831]: [2014/03/15 10:38:08.354264, 0] ../source3/lib/util_sock.c:941(matchname) Mar 15 10:38:08 KANDOR smbd[36830]: matchname: host name/name mismatch: 192.168.1.100 != (NULL) Mar 15 10:38:08 KANDOR smbd[36830]: [2014/03/15 10:38:08.354392, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname) Mar 15 10:38:08 KANDOR smbd[36830]: matchname failed on 192.168.1.100 Mar 15 10:38:08 KANDOR smbd[36831]: matchname: host name/name mismatch: 192.168.1.100 != (NULL) Mar 15 10:38:08 KANDOR smbd[36832]: [2014/03/15 10:38:08.354957, 0] ../source3/lib/util_sock.c:941(matchname) Mar 15 10:38:08 KANDOR smbd[36831]: [2014/03/15 10:38:08.355036, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname) Mar 15 10:38:08 KANDOR smbd[36831]: matchname failed on 192.168.1.100 Mar 15 10:38:08 KANDOR smbd[36832]: matchname: host name/name mismatch: 192.168.1.100 != (NULL) Mar 15 10:38:08 KANDOR smbd[36832]: [2014/03/15 10:38:08.355494, 0] ../source3/lib/util_sock.c:1199(get_remote_hostname) Mar 15 10:38:08 KANDOR smbd[36832]: matchname failed on 192.168.1.100
Happens with any IP that connects to the server. Googling seems to indicate that it's nothing to worry about but how do I go about fixing what it's complaining about?
 

GrumpyVet

Cadet
Joined
Mar 27, 2014
Messages
1
I'm getting the same problem, just with slightly different IPs (192.168.1.9X where X is 2, 3, or 4) reported on the console, and the webGUI reporting an alert saying " WARNING: The WebGUI Address could not bind to 192.168.1.93; using wildcard"

I'm afraid I'm an interested novice at this trying this out to repurpose an old Athlon XP 3200+ with 2Gb RAM and two 1Tb SATA-1 disks, so I have to confess I don't know where to start - perhaps by setting a fixed IP in my router? but I thought I'd better search and ask first!
 
Status
Not open for further replies.
Top