Am So, den 04.07.2004 schrieb Matt Hansen um 3:34: Hi Matt! > Recently, I altered my Samba config to correctly listen only on the > internal interface (Samba is on the gateway so computer is multi-homed) > using 'interfaces' and 'bind interfaces only' param's. After restarting You still need to block access from outside as this settings only affect TCP, not UDP. Your interfaces setting includes the "127.0.0.1/8" net? > the daemons, the following logs have been consistently appearing every 5 > mins since: > > *Attempting to become domain master browser on workgroup SIMBA, subnet > UNICAST_SUBNET. > *become_domain_master_browser_wins: querying WINS server from IP > 127.0.0.1 for domain master browser name SIMBA<1b> on workgroup SIMBA > * There is already a domain master browser at IP 210.49.xx.xx for > workgroup SIMBA registered on subnet UNICAST_SUBNET. > *Samba name server AMAZON is now a local master browser for workgroup > SIMBA on subnet 192.168.1.1 SIMBA is your workgroup name and AMAZON the netbios name of your samba server? IP 210.49.xx.xx is within your own network? Do you really need a domain master browser setting as "# Domain Master specifies Samba to be the Domain Master Browser. This # allows Samba to collate browse lists between subnets. Don't use this # if you already have a Windows NT domain controller doing this job" Do you need a WINS server running too? What do you have set for WINS in the smb.conf? > And a minute later this, but I think this is caused by the above > problem: > *Doing a node status request to the domain master browser for workgroup > SIMBA at IP 210.49.xx.xx failed. Cannot sync browser lists. > > So it seems there's no problem becoming the LMB (local master) on the > correct internal interface (192.168.1.1) but every attempt to become the > DMB fails with the above errors. I tried ifdown'ing eth0 and restarting > samba but that didn't help. Google had almost nothing on this particular > error. I thought there would be a timeout for the current domain master > and a new election would see that samba is now listening on a new IP > address for the WINS server but this hasn't seemed to happen yet (I've > left it a few days to test). > > Anyone have any ideas? If above annotations are not helpful you may provide us with the output for the [global] section of a "testparm" run. "testparm" may also print you out some other useful information. > Regards, > Matt Alexander -- Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 Fedora GNU/Linux Core 2 (Tettnang) on Athlon CPU kernel 2.6.6-1.435.2.3 Serendipity 19:20:58 up 52 min, 8 average: 0.37, 0.20, 0.26
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
