On Sunday 05 January 2003 1:53 am, FX Fraipont wrote:
Tom Emerson wrote:
check the file /var/log/samba/
This will have lines in it indicating when a "browse master election" occurs. Your computer will try to become "the master", yet will abstain from attempting to be the "domain" master [actually, re-reading these two items myself helps makes sense to me -- at first it didn't...] Does it "win" these elections? This is my log.nmbd fil
[2003/01/04 14:16:41, 0] nmbd/nmbd.c:main(872) ERROR: Failed when creating sos nameserver version 2.2.5-SuSE started. Copyright Andrew Tridgell and the Samba Team 1994-2002 [2003/01/04 14:16:40, 0] nmbd/asyncdns.c:start_async_dns(148) started asyncdns process 1372 [2003/01/04 14:16:41, 0] lib/util_sock.c:open_socket_in(804) bind failed on port 137 socket_addr = 192.168.0.1. Error = Cannot assign requested address [2003/01/04 14:16:41, 0] nmbd/nmbd_subnetdb.c:make_subnet(139) nmbd_subnetdb:make_subnet() Failed to open nmb socket on interface 192.168.0.1 for port 137. Error was Cannot assign requested address ubnet lists. Exiting.
Bind failed on port 137? Something to do with SuSEfirewall2? I was advised yesterday to open ports 136 137 on my firewall, tried it, but that did not change a thing.
There are two primary ways you can "fail to get an address" 1) it's already in use -- make sure nmbd is NOT running and try the "netstat -a --tcp" command -- if the system shows it is "listening" on port 137, then "something else" has the port [track that down!] **potentially** this could be inetd/xinetd [that's its job: listen on several ports on behalf of various background/daemon type programs; when activity occurs, inetd spawns the appropriate daemon handler and passes the connection] if your system shows the port to be "in use", and investigation shows the owner to be "inetd", check the configuration file for nmb [and probably smb] You'll have to decide if you really want to continue using inetd to watch for and spawn these processes or if you want them to run "standalone". 2) your "nmdb" process is not running "as root" -- ports below 1024 are considered "privileged", which simply means that any process that tries to open such a port MUST be a superuser process -- this can either occur by having "root" explicitly run such a program, or by setting the program to be "suid" and making the owner of the program "root" [suid means set uid -- when started, the process changes from running as the user who initiated it to the "owner" of the file.]
How can I have all theses error messages and at the same time be able to mount shares from the win98 boxes? It does not make sense to me.
because "nmb(d)" doesn't transfer files -- smbd does. nmbd only manages the "names" found on the network [browsing & broadcasts]
After the system has been running for a while, what information appears in the /var/lib/samba/browse.dat file?
"WORKGROUP" c0001000 "VERTIGO" "WORKGROUP" "VERTIGO" 40049a23 "Samba 2.2.5" "WORKGROUP" "JULES" 40412003 "" "WORKGROUP" "MART" 40412003 "" "WORKGROUP"
From the looks of it, your computer has "seen" broadcasts from JULES and MART, but not CECILE or SIM. On the windows computer(s), you can check for much the same thing by using the DOS command "nmbstat" [I think -- look for exectuables ending with "stat" in the windows or windows/command directory]