OK, we have two (2) DCD's setup across the internet. Both are running
nmb-207.lrp to investigate samba vs. wins functionality. Both happen to
be ipsec gateways.
Both /etc/smb.conf files are setup identically, except for these:
trout
=====
hosts allow = 192.168.123. 192.168.1. 127.
interfaces = eth1 192.168.1.0/24
socket address = 192.168.123.254
workgroup = MDS
bluetrout
=========
hosts allow = 192.168.1. 192.168.123. 127.
interfaces = eth0 192.168.123.0/24
socket address = 192.168.1.254
workgroup = PLATINUM
trout starts up like this (/var/log/log.nmb):
started asyncdns process 17255
Attempting to become domain master browser on workgroup MDS, subnet
UNICAST_SUBNET.
querying WINS server at IP 192.168.123.254 for domain master browser
name MDS<1b> on workgroup MDS
Samba server TROUT is now a domain master browser for workgroup MDS on
subnet UNICAST_SUBNET
Attempting to become domain master browser on workgroup MDS on subnet
192.168.123.254
querying subnet 192.168.123.254 for domain master browser on workgroup
MDS
Samba server TROUT is now a domain master browser for workgroup MDS on
subnet 192.168.123.254
Samba name server TROUT is now a local master browser for workgroup
MDS on subnet 192.168.123.254
Then, it will sit like this for several hours, without anymore log
entries.
trout starts up like this (/var/log/log.nmb):
started asyncdns process 4370
Attempting to become domain master browser on workgroup PLATINUM,
subnet UNICAST_SUBNET.
querying WINS server at IP 192.168.1.254 for domain master browser
name PLATINUM<1b> on workgroup PLATINUM
Samba server BLUETROUT is now a domain master browser for workgroup
PLATINUM on subnet UNICAST_SUBNET
Attempting to become domain master browser on workgroup PLATINUM on
subnet 192.168.1.254
querying subnet 192.168.1.254 for domain master browser on workgroup
PLATINUM
There is already a domain master browser at IP 192.168.1.101 for
workgroup PLATINUM registered on subnet 192.168.1.254.
Samba name server BLUETROUT is now a local master browser for
workgroup PLATINUM on subnet 192.168.1.254
timeout connecting to 192.168.123.254:139
timeout connecting to 192.168.123.254:139
The timeout repeats every ~15 minutes. Notice, trout == 192.168.123.254
and bluetrout == 192.168.1.254 ; while 192.168.1.101 is a w2k domain
controller.
Is samba actually doing anything in these environments?
Why the incongruous errors on bluetrout only?
What else need we do?
What do you think?
--
Best Regards,
mds
mds resource
888.250.3987
Dare to fix things before they break . . .
Our capacity for understanding is inversely proportional to how much we
think we know. The more I know, the more I know I don't know . . .
_______________________________________________
Leaf-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/leaf-user
