Red Hat Bugzilla – Bug 452284
samba sharing problem - Matchname failed
Last modified: 2010-05-10 13:46:55 EDT
A Windows 98 machine can not access samba shares after the samba server was
upgraded to F9. It worked OK before the upgrade.
The samba logs say:
[2008/06/20 13:45:23, 0] lib/util_sock.c:matchname(1670)
matchname: host name/address mismatch: ::ffff:192.168.0.93 !=
[2008/06/20 13:45:23, 0] lib/util_sock.c:get_peer_name(1791)
Matchname failed on engraver.domain.avtechpulse.com ::ffff:192.168.0.93
The "::ffff:" may be the source of confusion. The DNS should be OK:
[root@server2 samba]# ping engraver
PING engraver.domain.avtechpulse.com (192.168.0.93) 56(84) bytes of data.
Similar issues reported here:
I removed the "allow hosts" clause from smb.conf to eliminate the ip-number
matching. That eliminated the above problem.
Then I found that current samba releases disable lanman authentication by
default. And they quietly delete the old lanman hashes from the user database. A
I had to add:
lanman auth = yes
client plaintext auth = yes # not sure if this is needed
client lanman auth = yes
AND reset the W98 user's password in Samba.
I think the original issue is still real (address matching failing). This
comment is to assist anyone else who has to support F9 + W98.
I have Fedora 10 (F10) and have used the above lanman auth config, but still receive the above errors in the samba log file.
What data do you need?
I see it on Rawhide 10.92 too, but access works. It's just the annoying
message in the logs in my case.
Mar 2 15:12:53 elanor smbd: [2009/03/02 15:12:53, 0] lib/util_sock.c:matchname(1749)
Mar 2 15:12:53 elanor smbd: matchname: host name/address mismatch: ::ffff:192.168.128.12 != shadow.zaitcev.lan
Mar 2 15:12:53 elanor smbd: [2009/03/02 15:12:53, 0] lib/util_sock.c:get_peer_name(1870)
Mar 2 15:12:53 elanor smbd: Matchname failed on shadow.zaitcev.lan ::ffff:192.168.128.12
[root@elanor master]# host shadow
shadow.zaitcev.lan has address 192.168.128.12
shadow.zaitcev.lan has IPv6 address fec0::1:0:0:c0a8:800c
[root@elanor master]# host 192.168.128.12
184.108.40.206.in-addr.arpa domain name pointer shadow.zaitcev.lan.
[root@elanor master]# grep auth /etc/samba/smb.conf
A useful workround if you're not actually using IPv6 is to disable it. I did this by creating a file in /etc/modprobe.d called disable-ipv6 (but you can call it whatever you want) with the contents:-
install ipv6 /bin/true
Reboot and check that ipv6 is no longer around by "/sbin/lsmod | grep ipv6".
You can then re-enable any "hosts allow" in the samba configuration, restart samba
and they should be honoured without any error messages.
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
Initial post has two separate issues
Win-98 issue has been dealt with
The spurious log messages is not a bug.
This is samba attempting a reverse lookup to help guard against man-in-the-middle attacks and the target DNS server not providing a suitable response to an IP V.6 request.
To test: dig -6 <hostname.hostdomain> and you should get back the IP v6 address.
Then: dig -x6 <ip-v6-address> and you won't get back the
If so, simply add an entry to the local /etc/hosts file
The spurious messages should then cease
The ::ffff: notation for the ipv4 to ipv6 address conversion..
Would this not denote a broken resolver?
::1 is the localhost loopback (pure IPv6)
formally, it can also be specified as:
::ffff:7e00:0001 (IPv4-to-IPv6 address)
The default /etc/hosts file only includes the ::1 address and not the formal ipv4-to-ipv6 loopback address.
... Sorry was rambling ... but in short:
Should the local resolver be able to identify the ::ffff:* addresses as ipv4-to-ipv6 addresses and perform an ipv4 query instead? (It may need to use an ipv6 to ipv4 translation system to get it...)
But it should be attempting the ipv4 query first..
my 2 cents on a CLOSED WONTFIX bug... as this stumped me for quite some time.. (as I'm not entering 2000+ hosts in my DNS server, nor my local hosts file...)
Interesting read if your interested in the 6to4 stuff...
Adding IPv6 addresses to /etc/hosts is in many cases not an acceptable workaround, e.g. when it comes to matching entries in netgroups. You are maintaining netgroups and hosts in DNS to get rid of local entries.
What happens: Samba does not recognize, that the IPv6 address is just the mapped IPv4 address (see wikipedia or whatever).
To really get around this problem without the need to patch samba, please see here: