HP3000-L Archives

February 1997, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Michael L Gueterman <[log in to unmask]>
Reply To:
Michael L Gueterman <[log in to unmask]>
Date:
Thu, 6 Feb 1997 15:41:38 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
  I just made an interesting discovery (at least it was to me).
I've been using Samba without defining an interfaces parameter
in the smb.conf file (I only have the single interface in my 928).
This works fine, no problems.  I hadn't been able to get the nmbd
server to correctly identify itself to the Windows 95 and NT 4.0
PC's that are on the same LAN as it though.  It DID correctly
find all of the other hosts on the network, and build the
/usr/local/samba/var/locks/browse.dat file (it was defaulting
to be a WINS server).  After some poking around, I noticed that
the the broadcast address being used was correct, but the
subnet mask was defaulting to a standard class C address space
of 255.255.255.0.  My network is subnetted (is that a real word?)
to a 64 IP portion of the Class C between 64 and 127 so the subnet
mask should have been 255.255.255.192.  This was not being
picked up from the systems config (I did verify that it was set
correctly in NMMGR).  So I added the 'interfaces' parameter
and now my 3000 shows up correctly in the 'Network Neighborhood'
and from a NET VIEW via the command line.
  Just another tidbit I thought people might like to know about.

Regards,
Michael L Gueterman
Easy Does It Technologies
email: [log in to unmask]
http://www.editcorp.com
voice: (509) 943-5108
fax:   (509) 946-1170

ATOM RSS1 RSS2