Samba or Wins issue: netbios aliases, not accessible by hostname

pingu · 11-02-2005, 08:54 AM

I have a samba-server, fc4, with 2 nics = two networks.
I want to have different configs for those 2 networks.
One problem is that I can't connect to Linux-boxes using hostname, next problem is that samba doesn't use both netbios aliases. These problems could be related, but I don't know.

Facts:
2 AD-domains, 250 + 80 computers. DHCP, DNS and WINS -servers are outside our domains. Linux-clients can browse network, Internet, connect & map network-shares etc. But no computer can reach any Linux by name - be it hostname or FQDN. Connecting with IP works.

Samba-server: Static IP's (tried DHCP, no difference) eth1 with DHCP_HOSTNAME=ugglan and eth0 with DHCP_HOSTNAME=uven

smb.conf has

Code:

hosts allow = 172.16.1.1/24 10.0.4.1/23 127.
interfaces = 172.16.1.0/24 10.0.4.0/23 127.0.0.1
netbios aliases = uven ugglan
include = /etc/samba/smb.conf.%L

I have two config files: smb.conf.UGGLAN & smb.conf.UVEN (with lowercase it didn't work at all).
If I disable that "include = /etc/samba/smb.conf.%L" I can connect from my workstation (Linux - I added the sambaservers IP to /etc/hosts to be able to check samba-config).
With "include = ..." enabled I can't connect.
Testparm on server only mentions

Code:

hosts allow = 10.0.4.1/23, 127.
include = /etc/samba/smb.conf.UGGLAN

From a Windows-computer:

Code:

C:\ nslookup killbill
Server: dc.skolnet.se
Adress: 172.30.1.3
Namn: killbill.skolan.se

172.30.1.3 = dc.skolnet.se = DNS, DHCP & WINS

(killbill is my Linux workstation, same result using FQDN and same result with sambaservers hostname.)
It can't be a DNS-problem since every name except internal networks Linux's works fine.
Then what can it be - if I at least knew if it's samba, WINS, AD?

gbb123 · 05-02-2008, 01:51 PM

Hello,

I am having the exact same issue you are having with some windows box's not being able to resolve the hostname of my linux(Samba) box properly.

I work at a computer recycling company so we get allot of computer that come through here that I load windows xp and 2k on. Most can resolve the hostname properly however there are some that cannot for some reason. The ones that cannot resolve the hostname properly can still access the linux samba shares through it's IP address. Is this actually some sort of nic issue?