Something else: if I stop smbd with rcsmb stop, it stops all right. But rcnmb stop, followed by rcnmb status shows it is still running. Why?
read that carefully again -- your first line says rc-S-mb stop works, but your second line says rc-N-mbd stop followed by status shows it running, so which is it? <S>mb or <N>mb?
vertigo:/home/fx # rcsmb status Checking for Samba classic SMB daemon running vertigo:/home/fx # rcsmb stop Shutting down Samba classic SMB daemon done vertigo:/home/fx # rcsmb status Checking for Samba classic SMB daemon unused vertigo:/home/fx # rcnmb status Checking for Samba classic NMB daemon running vertigo:/home/fx # rcnmb stop Shutting down Samba classic NMB daemon done vertigo:/home/fx # rcnmb status Checking for Samba classic NMB daemon running This was what I meant: even when I try to stop nmbd, it is still running. But killing the pid kills it all right.
You did open these to the "internal" network only, correct? It wouldn't do to open this to the "outside" -- after all, that is explicitly what the firewall should be protecting you from... :)
# Common: ssh smtp domain FW_SERVICES_INT_TCP="ssh smtp 9925 80 139" # Common: domain syslog FW_SERVICES_INT_UDP="137 138" # For VPN/Routing which END at the firewall!! FW_SERVICES_INT_IP="" Something else My nmb log reads: Failed to open nmb socket on interface 192.168.0.1 for port 137. Error was Cannot assign requested address [2003/01/06 14:32:57, 0] nmbd/nmbd.c:main(872) ERROR: Failed when creating subnet lists. Exiting. ~ But the computers on the network go from 192.168.0.99 to 192.168.0.95 There is no 192.168.0.1 on my network ! fxf -- ______________________ Courtesy of SuSE Linux nibz.org