[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference ripper::samba

Title:Discussions about SAMBA
Moderator:GIDDAY::HIRSHMAN
Created:Fri Mar 24 1995
Last Modified:Sun May 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:8
Total number of notes:26

8.0. "NT security from SAMBA" by GALVIA::thebe.ilo.dec.com::rawlings () Tue Apr 29 1997 23:55

	Help!

	This is really busting my brain..

	I'm running Samba 1.9.16p10 on DUNIX V3.2D

	I have an NT Workstation V4.0

	I want to access a share on the DUNIX system
	from as 'E:' on the NT system.
	I'd like 'E:' to be available at NT boot time
	without my having to enter a username and password.
	(in fact it's worse thatn that, I have to disconnect
	 from E: and reconnect after each reboot of the NT
	 system)

	What I'm trying to do is to set up SAMBA to use 
	the NT 'domain' security to achieve this.

	Has anyone suceeded in doing anything like this?

	Care to share any startling insight I'm obviously
	missing???

		Thanks,
			Mark.
T.RTitleUserPersonal
Name
DateLines
8.1I don't think that its there yet....TWICK::PETTENGILLmulpFri May 02 1997 14:461
Check out the samba news group; see the archive on the samba web.
8.2CFSCTC::SMITHTom Smith MRO1-3/D12 dtn 297-4751Sun May 04 1997 12:0516
    See the man page for smb.conf and various things in the .../docs   
    directory. The default security model is share-level security
    ("security = share"), which seems to be the best choice if you have
    WfWG clients. You may be looking for either "security = user", which
    requires that your UNIX and PC user names and passwords be the same, or
    "security = server" and "password server = xxx", which does
    username/password authentication via another server (e.g., an NT domain
    controller).
    
    Note that there are some restrictions when using WfWG clients with
    "security = user" - for all practical purposes, you can only access
    your own shares, even if you know the password for another account.
    
    You may also want to update to 1.9.16p11.
    
    -Tom