SMB problem after upgrade from 8.3.1 to 9.1.1

[crisman]

Hi,

Today I've upgraded to the newest release of Freenas and everything looks working fine but I'm always having messages on the console like this one:

Sep 6 12:05:32 freenas smbd[2329]: [2013/09/06 12:05:32.297630, 0] lib/util_sock.c:1143(matchname)
Sep 6 12:05:32 freenas smbd[2329]: matchname: host name/address mismatch: 192.168.0.87 != lfranca-8sv85n1.lusotufo.pt
Sep 6 12:05:32 freenas smbd[2329]: [2013/09/06 12:05:32.297816, 0] lib/util_sock.c:1264(get_peer_name)
Sep 6 12:05:32 freenas smbd[2329]: Matchname failed on lfranca-8sv85n1.lusotufo.pt 192.168.0.87

Could someone tell me what is this?

Regards.

 

[Whattteva]

It's complaining that your hostname of lfranca-8sv85n1.lusctufo.pt does not resolve into 192.168.0.87.
It makes sense since it looks like lusotufo.pt is an actual valid domain name and obviously that would not be able to resolve into a private 192.168.x.x IP address.

It's just warning messages that probably would not affect daily operations, so I wouldn't be too worried.

 

[paleoN]

Could someone tell me what is this?

Fix your DNS, add the appropriate entry to Host name database, under Network → Global Configuration, or turn off Hostnames lookups, under Services → CIFS.

 

[ClayM]

Sorry for the thread necromancy, but after upgrading to 9.2.1, I'm getting this error as well - it's not matching on one of my jails. It's obviously not a big deal, but any ideas?

 

[cyberjock]

Necromancer!!!!!!! Kill him with fire!

Actually, there's a whole bunch of SMB problems with 9.2.1. There's a bug fix version due out when the bugs are worked out.

 

[Lusca]

Just got this :

Code:

Mar 16 13:15:00 freenas smbd[88710]: [2014/03/16 13:15:00.482580,  0] ../source3/lib/util_sock.c:941(matchname)
Mar 16 13:15:00 freenas smbd[88710]:  matchname: host name/name mismatch: 192.168.1.218 != (NULL)
Mar 16 13:15:00 freenas smbd[88710]: [2014/03/16 13:15:00.482785,  0] ../source3/lib/util_sock.c:1199(get_remote_hostname)
Mar 16 13:15:00 freenas smbd[88710]:  matchname failed on 192.168.1.218

today-. 218 is my computer .. I cant remember that i have entered that ip from anywhere.. certainly no the name of computer obviously... any tips where i should put it to get the error go away ?


cheers

 

[cyberjock]

any tips where i should put it to get the error go away ?

Did you read the post by paleoN that says "fix your DNS"? That means you need to fix your DNS(which isn't on FreeNAS most likely).

 

[Lusca]

yeah ok... added ip to my pc and the name to : hostname databse in the webgui..
guess that did the trick, tnx..
only this now, which i guess is ok:)

Code:

Mar 16 14:11:37 freenas notifier: Setting hostname: freenas.local.

 

[Rogla]

I'm late to the party here, just for the record....

I also got this issue. In my case there was already another Local Master on the network (domain) where I installed a new FeeNAS box.
Only one Local Master is allwed, else race conditions.
The Local Master option is enabeld by default in the CIFS service configuration in FreeNAS.
So after disabeling the Local Master in FreeNAS the nams was resolved by the original Local Master, no hostname DB in Freenas.

 

[hansmuff]

I'm late to the party here, just for the record....

I also got this issue. In my case there was already another Local Master on the network (domain) where I installed a new FeeNAS box.
Only one Local Master is allwed, else race conditions.
The Local Master option is enabeld by default in the CIFS service configuration in FreeNAS.
So after disabeling the Local Master in FreeNAS the nams was resolved by the original Local Master, no hostname DB in Freenas.

Just encountered this issue on my 9.3-stable install as well shortly after setting up my first CIFS share.
Your solution fixed it, and the documentation supports that I don't need it. Thanks!