Hi - Boy am I getting a headache trying to understand Samba! I am using SuSE11.0. It appears that there is some sort of conflict going on with the ports that Samba uses, and I for the life of me cannot make heads or tails out of how to diagnose the problem. The log file for log.smbd is showing the following error messages whenever I restart the two smbd and nmbd services (from within SWAT) - [2009/10/23 19:12:27, 2] lib/interface.c:add_interface(337) added interface eth1 ip=192.168.2.100 bcast=192.168.2.255 netmask=255.255.255.0 [2009/10/23 19:12:28, 2] lib/util_sock.c:open_socket_in(1267) bind failed on port 445 socket_addr = 0.0.0.0. Error = Address already in use [2009/10/23 19:12:28, 2] lib/util_sock.c:open_socket_in(1267) bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use [2009/10/23 19:12:28, 2] smbd/server.c:open_sockets_smbd(581) waiting for a connection
From what I have read on the internet, most suggestions imply that the samba servers are already running somehow and that some other instance of them has already attached to these two ports. That makes no sense to me because I am doing a restart on these servers which if common sense is right, that means the previous instances should be halted, detached from the ports and an new instance is started up... No??? I dunno and am quite confused if something else is happening...
Another suggestion I found said to do a netstat -ap and grep for the port numbers 139 and 445 but that showed nothing. I did a bit of further research and found a hint suggesting I grep for netbios instead. Ok, but I dunno why I would have to know some magical name but when I did I got the following - \tcp 0 0 *:netbios-ssn *:* LISTEN 3711/smbd udp 0 0 192.168.2.10:netbios-ns *:* 2710/nmbd udp 0 0 *:netbios-ns *:* 2710/nmbd udp 0 0 192.168.2.1:netbios-dgm *:* 2710/nmbd udp 0 0 *:netbios-dgm *:* 2710/nmbd Hump! that was informative!!! So on a hunch I decided to use SWAT and stop both the smbd and nmbd services then ran the netstat command again, and as I might expect nothing showed up. So why, when I start these two services up, do I get these error messages about the Address already in use and bind failed on port... ? Gosh one would think there would be a tool of some kind that would easily answer such a question - i.e. Why is a port already in use when it shouldn't be? But perhaps like so many other error messages I keep encountering, this is a bad error message or a red herring of some kind? Can some kind soul lead me out of this mess? Thanks and much appreciate any help offered... Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org