LATRAS63@terra.es wrote:> Hello
> A really annoying question.
> I'm managing a high school network with two WinXP subnets (192.168.1.X
and 192.168.3.X).
> These subnets are linked by a SUSE 9.3 server with two network cards and a
Samba server (version 3.0.12-5 SUSE) acting as PDC.
> The /etc/smb/smb.conf has next lines:
> wins support = yes
> hosts allow = 192.168.3. 192.168.1. 127.0.0.1
> interfaces = 192.168.3.2/24 192.168.1.2/24
> Now, for the problem:
> In the morning first hour, the first user must log on at a 192.168.3.X
host. If I try first with a 192.168.1.X host, next message appears:
> --System cannot log you on because Domain xxxxx is not available---
> Next, I log on at a 192.168.3.X host without any problem, and everything
works OK in the two subnets for the rest of the day.
> Problem repeats netx day, and so on. I can't understand what's the
matter. It seems that 192.168.3. subnet acts as a "starter" for the
Samba server, but I don't know why.
> Please can anyone help me??
> Thanks in advance.
>
In netbios, there can only be one interface IP address for any netbios
name. Old MS problem, although I don't have any links.
I like to assign samba to only one of the interfaces and I assign the
same interface to the DNS name. Other interfaces get different DNS
names. This is useful in the kerberos world as well as paranoid ssh.
smb.conf
interfaces = 192.168.3.x, 127.0.0.1
The 127.0.01 address doesn't register in wins or broadcasts and solves
some broadcast issues, or at least it did a long time ago and I haven't
experimented lately.
Regards, Doug