I know these are outdated systems, but if you have to find an error you have to find an error.
Problem was the W7 client could not join the SAMBA domain. Samba acting as PDC. More detailed, I could map a network drive by IP address: \\192.168.110.117\share, but I could not use the NetBIOS name: \\SERVER1\share.
NetBIOS over IP was enabled in Windows. On the Samba server itself resolution was working:
Code:
nmblookup -U '192.168.110.117' -R 'SERVER1'
This worked also from another Linux host. But not in Windows. In Windows the diagnostic command is:
Code:
nbtstat -A 192.168.110.117
Which produced a 'server not found error'
It turned out that the Windows machines had 2 additional IP4 addresses. Both private: 192.168.14.104 and 192.168.120.104. The primary address was (manually set) 192.168.110.104. And the default gw 192.168.110.12.
Anyway, running tcpdump on the Samba server revealed that Samba always tried to answer to 192.168.14.104. No idea why this address was set as source address, but the Samba server could not reach 192.168.14.xxx
After removing the other IP addresses name resolution worked fine. Including joining the domain.
Very weird.
jlinkels
