Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

samba weirdness

0 views
Skip to first unread message

YoYo

unread,
Jan 22, 1999, 3:00:00 AM1/22/99
to
I've been trying to get samba working on my home LAN with very limited
success. Last night, I finally got the password thing sorted out, and for
the first time I was able to see the Linux box in the 98 box's Network
Neigborhood. This morning, I tried it again, and I couldn't get anything.
In the intervening time, I didn't do anything to either box. I checked on
the Linux box and smbd and nmbd were both still running.

Any ideas?

--
----YoYo------...@tezcat.com------------and stuff------

"...and there are plenty of people joining in to help Tiger Woods
find his tee shot." -Mike Tirico

Brian L. Naylor

unread,
Jan 23, 1999, 3:00:00 AM1/23/99
to
And on 22 Jan 1999 07:28:29 -0600, the sage YoYo (yo...@huitzilo.tezcat.com)
did say:

>I've been trying to get samba working on my home LAN with very limited
>success. Last night, I finally got the password thing sorted out, and for
>the first time I was able to see the Linux box in the 98 box's Network
>Neigborhood. This morning, I tried it again, and I couldn't get anything.
>In the intervening time, I didn't do anything to either box. I checked on
>the Linux box and smbd and nmbd were both still running.
>
>Any ideas?

Yeah. I find that Windows boxes need to be told about the presence of
Samba servers on bootup. At work, booting my NT box, I generally need
to restart smbd and nmbd (they announce themselves on startup) to make
my Windows box aware of Samba's presence.

It's possible that without regular announcements, a 98 box might forget
about a particular server. (No, I wouldn't *expect* that, but it's
certainly possible, considering.. ;) Luckily, Samba provides a way out
of this box: "remote announce". Define this key phrase in your smb.conf
and point it at your local broadcast address, leave the boxes up overnight
again with no other changes, and see if that helps. (I'd be interested in
hearing your results, btw..)

Of course, if anyone has any better solutions I'd also be interested in
hearing them.

--
Brian Naylor <bria...@sackheads.org>
<david> HAHA I typed smitty kernel on my linux box... HHAHAHAHA god help me!

Peter da Silva

unread,
Jan 23, 1999, 3:00:00 AM1/23/99
to
I have found that Samba boxes don't reliably show up in your network
neighborhood unless you have a WINS server running. You can add the
names and IP addresses to the LMHOSTS file, though, and that seems
to do the trick.

10.0.0.1 unixbox #pre

The #pre forces it to be preloaded.

--
This is The Reverend Peter da Silva's Boring Sig File - there are no references
to Wolves, Kibo, Discordianism, or The Church of the Subgenius in this document

"If you don't have 64 bits, you're not playing with a full DEC."

YoYo

unread,
Jan 23, 1999, 3:00:00 AM1/23/99
to
Peter da Silva <pe...@taronga.com> wrote:

>I have found that Samba boxes don't reliably show up in your network
>neighborhood unless you have a WINS server running. You can add the
>names and IP addresses to the LMHOSTS file, though, and that seems
>to do the trick.
>
>10.0.0.1 unixbox #pre
>
>The #pre forces it to be preloaded.

Thanks.

Mark Baker

unread,
Jan 25, 1999, 3:00:00 AM1/25/99
to
In article <78d2e1$t...@bonkers.taronga.com>,

pe...@taronga.com (Peter da Silva) writes:
> I have found that Samba boxes don't reliably show up in your network
> neighborhood unless you have a WINS server running. You can add the
> names and IP addresses to the LMHOSTS file, though, and that seems
> to do the trick.

Yes, I found that problem too; I solved it by making samba a WINS server.

0 new messages