Search results for query: *

I edited /etc/sysconfig/samba to include the -s option for both smbd and nmbd. I set their conf files to /etc/samba/smb.conf and /etc/samba/nmb.conf accordingly. Then I renamed smb.conf to both.conf. I made two new files: smb.conf and nmb.conf, and added the following ---to smb.conf...

You're probably right. I'm actually blocking the broadcasts with iptables for the short term. I just had an idea though. Could I have two separate configuration files? One, say, for smbd and another for nmbd? or even better what about using an includes file referenced by a variable...

Unfortunately, that would keep smbd from responding to direct access on eth0. 'interfaces' is currently set = to '127.0.0.1/8 192.168.0.2/24 172.16.87.105/20' That last one is what puts samba on eth0. SMBd must be on eth0 so that certain good hosts on that network can connect to the server...

I went ahead and restarted the whole smbd. No luck, it still was sending junk to that host. I tried to block it in iptables, and it got MAD. var/log/messages is getting entries from smbd about operation not permitted when it tries to transmit to 172.16.95.255!

hrm, its not working yet. I saved the change, ran testparm, then ran 'service smb reload' the reload went OK, but I'm still seeing the broadcasts in tcpdump. I can schedule a restart of smb for tonite, but is there a way to force this change to take effect without restarting samba completely...

My 'remote announce' was set to '192.168.0.255' originally (192.168.0.0/24 is the sub-net of eth1) At some point in trying to isolate this, I commented out the 'remote announce' line. Since you mentioned it, I looked it up in O’Reilly's 'Using Samba', which said: From this I assume 'remote...

I run a samba server on Fedora Core 5. This machine has two nics, one wan, one lan. I want smbd (port 139 and 445) to be available to hosts on both networks. I want nmbd broadcasts and announcements to only occur on eth1 (lan). I am trying to minimize traffic on eth0. My server keeps...