On Monday 06 January 2003 12:34 pm, FX Fraipont wrote:
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 !
As Homer S. would, say, "Doh!" Re-reading your original message [wherein you had your smb.conf file] I see: On Saturday 04 January 2003 3:54 am, FX Fraipont wrote:
[global] interfaces = 192.168.0.0/255.255.255.0
and referring to "man smb.conf", "interfaces" section: interfaces (G) This option allows you to override the default net work interfaces list that Samba will use for brows ing, name registration and other NBT traffic. By default Samba will query the kernel for the list of all active interfaces and use any interfaces except 127.0.0.1 that are broadcast capable. The option takes a list of interface strings. Each string can be in any of the following forms: · a network interface name (such as eth0). This may include shell-like wildcards so eth* will match any interface starting with the substring "eth" · an IP address. In this case the netmask is deter mined from the list of interfaces obtained from the kernel · an IP/mask pair. · a broadcast/mask pair. The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted dec imal form. The "IP" parameters above can either be a full dotted dec imal IP address or a hostname which will be looked up via the OS's normal hostname resolution mechanisms. For example, the following line: interfaces = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0 would configure three network interfaces corresponding to the eth0 device and IP addresses 192.168.2.10 and 192.168.3.10. The netmasks of the latter two interfaces would be set to 255.255.255.0. See also bind interfaces only. Default: all active interfaces except 127.0.0.1 that are broadcast capable You're telling samba to use "interface 192.168.0.0" [which is flat out invalid, btw, since nobody is allowed to use ".0" as their computer's node address; likewise .255 is a no-no] "perhaps" nmbd is "correcting" that for you by trying to use .1 instead of .0 [it could be a "common enough mistake..."] [checking my own file I see I've set mine to use the actual interface -- per the above, this really isn't neccessary, but I think "at one time" this computer was also "the firewall", so it had more than one IP address -- limiting Samba/nmbd to "just one interface" helps cut down potential "intrusion" points...] [you may take a discount on that check you were going to send me :) ]