On Sat, 14 Oct 2000, ktb wrote:

> Drew Hunt wrote:
> > 
> > I've scoured through the Samba HOWTO and guide and I just can't seem to find
> > a fix!  I want to run SMB from my linux box so I can access it on my win 98
> > host.  No matter what I try, though, I just can't get the win box to see the
> > linux box in the Network Neighborhood.  does anyone have any suggestions for
> > items I should be including in my smb.conf file?  What should I look for in
> > the network properties on the win box to ensure correct confirguration?
> > 
> 
> Here is an easy to follow guide -
> http://www.linux-mag.com/2000-04/newbies_01.html
> 

Have you started nmbd?  nmbd broadcasts your linux box's existence to the
Doze boxen, so it can be seen in Network Neighborhood.  The proper
settings in smb.conf will determine whether you can gain access to
anything on your linux box, but to do that, you have to see it first in
Network Neighborhood, right?   Starting smbd doesn't automagically start
nmbd, so you need to start it by hand too (you will want a script to start
both for regular operations).

Make only a couple of simple changes to the default smb.conf file at first
until you get that working.  Then you can add stuff.  What I like to
change first to just get things up and running:

workgroup = workgroupofmydozeboxen
security = user  (this should be already uncommented by default)

if you a trying from a Windows 98 (or more recent win95) or NT box, then
you want to uncomment the line:

encrypt passwords = yes

(If you have an older Win95 box from which you are testing, you will need
to leave this encrypt passwords line COMMENTED OUT, since they use plain
text/unencrypted passwords.   If you will be serving Doze boxen of both
flavors (some with encryption, some without) then you will have a little
more work to do (e.g. you could turn off password encryption on the 98
boxes), but that's way beyond the current advice on just getting up and
testing with one Windows client box.)

I also uncomment the following line:

unix password sync = Yes
        
(This will help to keep the smbpasswd file and the passwd (regular linux
passwd file) sychronized - same users, same passwords...

Then, create a test user account:

/usr/sbin/adduser someusername
passwd someusernamepassword

/usr/sbin/smbd
/usr/sbin/nmbd

(you can run testparm to test your smb.conf file if you wish, but it
shouldn't be necessary here yet).

Go to PC, restart and log in as the user you just created and log in with
the password you just created.

Now, go to Network Neighborhood.
You should see your Linux box there (in your existing pc workgroup).
Since we didnt' change the server name in smb.conf yet, the machine's
network neighborhood name will be it's tcp/ip hostname (full domain name
e.g.  joe.blow.foo.com).  That's ok for now, you will take care of little
details like that after you prove basic connectivity.

You should see a folder labeled with your login username.
Open it up.  This is your home directory folder for that user on the linux
box (e.g. /home/yourusername) and it is also the default user directory
that you can get to from a Windoze box if you are logged in as that user
under MS Windoze.

You should be able to read/write to/from this folder.  (You will see at
least one folder there already - "Desktop").

Now, you know that basic smb file service (in "user" share mode) is
working.

Now you can concentrate on getting things to work exactly the way you
want.  ("server" shares?  temp directory?  pcguest account?  lots of other
stuff).

If you make a change in smb.conf you have to restart smbd.
Since on my box, it's NOT in /etc/rc.d/init.d, I have to do this by hand.

List the two processes so you can kill them:

ps aux | grep smbd   and  ps aux | grep nmbd

Kill both of them:

kill -9 pid_of_smbd
kill -9 pid_of_nmbd

Restart both of them:

/usr/sbin/smbd
/usr/sbin/nmbd

Have fun!



-- 
***************************************************************************
Jerry Winegarden        OIT/Technical Support           Duke University
[EMAIL PROTECTED]            http://www-jerry.oit.duke.edu
***************************************************************************



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to