Tom Emerson wrote:
which version of samba? [just curious -- shouldn't matter, but later versions have "more features"...]
2.2.5-102
4 win98 boxes
any of them "NT" [and then, "workstation" vs. "server"?]
just four windows 98 boxes, sim, jules, mart, cecile
no wins server
trivial question: why not? [as in, "why not make the linux box the wins server?"] without a "wins" server, systems that do not "broadcast" the fact that they exist must be included in the "lmhosts" file of /every client/ that expects to "see" them "in the neighborhood" [this might give you an inkling as to what the problem may be, but read on...]
I used to have wins enabled, until I read in "teach yourself samba in 24 hours" that wins was only really necessary when samba was used with several networks: mine is a small home network, in the 192.168.0.x range, so Wins is not necessary. Removing it did not change anything, which kinda proves the point, I suppose.
[global]
workgroup = WORKGROUP server string = Vertigo Samba Server security = user local master = yes os level = 33 domain master = no preferred master = yes wins support = no
From the "man smb.conf" pages: <take a deep breath>
domain master (G)
Default: domain master = auto
local master (G)
Default: local master = yes
Actually, I used to have domain master = no Teach yoursef samba p 389: "the default value for this parameter is no" local master = yes Until one suse-lister advised me to change it to "no". Anyway, I've followed your advice, but I still can't see samba in NNeighborhood.
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 Ca nnot 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. 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.
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" Thanks for your help fx -- ______________________ Courtesy of SuSE Linux nibz.org