I put in the line for...

interfaces = 192.168.1.7/255.255.255.0

...and rebooted. But I still get this...

# smbclient -L localhost
added interface ip=192.168.1.7 bcast=192.168.1.255
  nmask=255.225.255.0
error connecting to 127.0.0.1:139 (Connection refused)
Connection to localhost failed
#

Which I expected since...

#ps -xa | grep nmbd
300 E0 S+ 0:00.0a grep nmbd
#

...showed nmbd not running.

But here is an interesting observation: the LED on the
Ethernet adaptor plug blinks when I try...

# smbclient -L STURNO2

...which is to the Win98, and which connects. But when
I try...

# smbclient -L localhost

...or even...

# smbclient -L STURNO1

...which is the name of the NetBSD local host, the
LED does NOT blink. Maybe only because NetBSD knows
that STURNO1 is localhost? and doesn't try to bcast
the ethernet? I can, however, ping all three: STURNO2,
STURNO1, and localhost.

Further, I can ping Solo which is a name for STURNO2 in
/etc/hosts. But I can't do this...

# smbclient -L Solo

...and get "Called name not present" for Solo.

Truly, I would like to try SWAT, but....

When I try SWAT on KDE 1.1.2 (version prior to those with 
Konqueror) which came with the Wasabi
four-CD set (as did this version of Samba) this 
happinens, I put...

http://localhost:901

...into KFM, and I get this KFM error...

Could not read
http:/localhost:901
File does not exist or access denied

...So I thought to maybe do pkg_add netscape,
but then it says I must do some Linux things
in the kernel. Apparently, some of the packages 
which came with my 1.5 NetBSD four-CD set from 
Wasabi are so ancient that nobody on this list
recommends I should use them. But alas, the
many recommendations on the net for NetBSD were
the vast collection of binary packages for Newbies
like me to just install with no fuss or muss. I
begin to doubt it, somewhat... Anyway, at present
unless I learn to compile from scratch, it looks
like I can't just do SWAT.

--
Gan Starling
Kalamazoo MI USA

---

To paraphrase Hitler... 
"Who remembers the Amalekites?"