I'm sure this issue have been discussed in this list far too many times
already... But I've been unable to find it, so...
My network is splitted in two subnets; one with public IP and one with private
IP. The ones with a private IP are masqueraded on a Linux server, also running
Samba and acting as a DNS. The two subnets are connected to the same hub, which
in turn are connected to _one_ NIC on the Samba server. On that server
there's two interfaces eth0 with the alias eth0:0.
How in earth can I get Samba to understand that it has to take care of NetBIOS
names on _BOTH_ those interfaces?!
This is the config:
192.168.1.0/24 <-> 195.67.88.224/28 <-> HUB -> firewall ->
router
Samba/DNS/WINS on 192.168.1.1 & 195.67.88.230. smb.conf is wins enabled, has
all the interfaces connected to it and is preferred master. With nmblookup
I'm unable to find any NetBIOS name on the private network, while it works
fine on the public. It is possible to connect with a UNC name to computers on
both the subnets from the server with smbclient, tough, by some reason. Neither
of the clients can talk across subnets, but they can talk to the server. So the
conclusion must be that the server is refusing to pass requests/broadcasts
through.
What should I do? Is it some issue with having the same network card on two
subnets and IP-aliases? Is it some routing problem? route shows this:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
195.67.88.230 0.0.0.0 255.255.255.255 UH 0 0 0 eth0
195.67.88.224 0.0.0.0 255.255.255.240 U 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 195.67.88.225 0.0.0.0 UG 0 0 0 eth0
Interface doesn't have a "eth0:0" in it as you can see... If it
would make any difference. WINS is configured to the same server, with
private/public IP, on all clients, so I would think that at least browsing
should work... But it doesn't.
So what are the steps to take to make Samba work over two subnets?
Would love some help!
---
Johan Bj?rk