[ale] samba question

[Dow Hurst]

Well, at first read it sounds like your user doesn't have a smbpasswd 
and smbuser identity on the Samba server.  You'll have to read the 
authentication section for background on the process, but to quickly fix 
just one user you will need these steps:

1.  Add the user as a smbuser and make him/her a password entry in 
smbpasswd.  On SuSE you can just run /usr/bin/smbadduser to create the 
user in smbpasswd file.  Mandrake may do things a bit different than SuSE.

2.  If he is a user on the Linux box then his Linux login and passwd and 
Samba login and passwd don't have to match unless you want him to be 
able to access his home directory and files.  Any shared files would 
need permissions and ownership such that the smbuser can access them.  
(I believe I have all this correct, but you might want to check the 
Samba doc)

3.  Make sure he uses the smbuser and smbpasswd you gave him/her when 
attempting to authenticate with the Samba server.

There is a whole bunch I don't know about Samba but the above ought to 
work just fine.  I am sure someone will correct me if I am wrong about 
something. ;-)
I was going to post the SuSE smb.conf from 8.2 or 8.1 to the list but I 
don't remember whether I did or not.  I'll see about doing it.  You 
might have lots of users so a central authentication scheme is what you 
really want.  Your Samba server ought to authenticate requests via a 
campus central server so you don't have to manage that stuff.
Dow


Robert E. Karaffa, II wrote:

>hi folks,
>    we use a mandrake 8.2 box as our file/web server.  it is behind the
>Emory U. firewall.  we turned off our ftp server at that address, and were
>only using AppleShareIP for file transfer (mostly because our labs were all
>Mac...however, that has recently changed.  we now have Windows boxes, and we
>need to provide SAMBA to our clients).
>    AppleShareIP (via netatalk) is functioning perfectly.  Yesterday, I
>activated SAMBA on the same server, tested it with my own and a couple of my
>clients login/passwords (from an on-campus IP), it seems to work...but I
>tested it from an OS X box.  Now, my clients are asking me to fix this
>problem, and I don't know how yet:
>
>  
>
>>Bob,
>>
>>Could you please give me some details on how to access my files if I use
>>Windows (XP/2000) from flowcore-ftp.rmy.emory.edu?
>>I found a computer with that name in My Network Places (I searched for it)
>>but when I try to map for it or open it it tells me that I do not have the
>>appropriate rights/permission and that the list of server for this workgroup
>>is not currently available.
>>    
>>
>
>I've been hacking at this on a Dell laptop (Win2k Pro) at home, connected
>through my firewall to the Emory network via VPN, and haven't been able to
>get it to work.  I can, however, connect my G4 OS X laptop to this server
>(from home, through my firewall, via VPN), and it works fine.  So, the
>problem is with Windows (yay!).  Anybody have any hints?  Care to walk me
>through setting it up via "My Network Places"?  I hate myself for asking on
>this list, because the problem is NOT with Linux (or OS X, for that matter),
>but a keyword search via google hasn't turned up squat (I DID find all kinds
>of info on how to connect a Linux box to a Win2k network!).
>
>-Bob K.
>  
>

-- 
__________________________________________________________
Dow Hurst                  Office: 770-499-3428
Systems Support Specialist    Fax: 770-423-6744
1000 Chastain Rd. Bldg. 12
Chemistry Department SC428  Email:   dhurst at kennesaw.edu
Kennesaw State University         Dow.Hurst at mindspring.com
Kennesaw, GA 30144
*****************************************************************
This message (including any attachments) contains confidential  *
information intended for a specific individual and purpose,     *
and is protected by law.  If you are not the intended recipient,*
you should delete this message and are hereby notified that     *
any disclosure, copying, or distribution of this message, or    *
the taking of any action based on it, is strictly prohibited.   *
*****************************************************************


_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale