<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 10/10/2015 05:19 AM, Hika van den
Hoven wrote:<br>
</div>
<blockquote cite="mid:1324613895.20151010141944@gmail.com"
type="cite">
<pre wrap="">If you don't run the wins server it will use the present msWindows
machines. Unless you have native msDS, browsing will use netbios as
served by every windows machine.
Wether you run the wins server is a setting in smb.conf
</pre>
</blockquote>
<br>
I finally had time to explore this problem -- the one where while I
could see other machines via IP addresses, I couldn't see them with
Samba.<br>
<br>
Today I did two things. I looked at the list of reserved IP
addresses in my router and saw that my desktop machine was not
listed. I added this machine to the list. I really don't think this
had anything to do with fixing my problem, but it's something I
needed to do anyway so other machines in the house can see the house
website. They weren't having any problems with it because the router
was always giving the machine the same IP address without being told
to. But now it's official.<br>
<br>
The second thing I did was to search for some background on Wins and
Samba. I found an O'Reilly publication, <i>Using Samba</i>, by
Robert Eckstein, David Collier-Brown, Peter Kelly. It is available
as an open book at: <br>
<br>
<a class="moz-txt-link-freetext" href="http://www.oreilly.com/openbook/samba/book/">http://www.oreilly.com/openbook/samba/book/</a> <br>
<br>
I read Chapter 7.3, Name Resolution with Samba, and now understand a
little more about WINS. <br>
<br>
Armed with all this new knowledge I started looking at my network
again and find that the simple threat of a little knowledge has
scared it back into operation. In other words, I don't know what I
did, if anything, but I can now see my network with Samba again.<br>
<br>
<pre class="moz-signature" cols="72">--
Regards,
Dick Steffens
</pre>
</body>
</html>