Hi All, I am new to the job of System Administrator and even newer to SAMBA. I have managed to set up SAMBA on Solaris so that from a Windows 95 machine I can map a drive to a point on the Unix machine. This works fine. What I am stuck at is an issue of security. I have been asked to work out how to limit the users that can access the mapped drive. ie., if someone walks into the office they cannot sit down and see all the files on our Unix machine. So, what I need to do is somehow look at the Windows username and password and if it is a known user, then allow the drive to be mapped but if it is not, don't allow it. I don't know how to read the Windows password. I did try using the name.map file : unixname = windowsname but it didn't work as I expected it to. Could anyone help me out with how I would go about this please? Thank you for any help you can offer. Julie Moore jmoore@kpmg.com.au
> Date: Tue, 28 Apr 1998 15:53:19 -0500 > From: Don_A_Nguyen@aimfunds.com (Don A Nguyen) > To: samba@samba.anu.edu.au > Subject: Win95 and samba-1.9.18p3 > Message-ID: <54642fc0@aimfunds.com> > > 0M8R4KGxGuEAAAAAAAAAAAAAAAAAAAAAPgADAP7/CQAGAAAAAAAAAAAAAAABAAAACgAAAAAA > AAAAEAAACwAAAAEAAAD+////AAAAAAkAAAD/////////////////////////////////////<snip>> AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA > AAAAAA=I think the problem might be in your mailer application. :-) Brett Brett Worth - Ph: +61 6 241 5633 Fx: 241 3733 - Canberra Australia
Why would a windows95 box not be able to see a Samba file server?
> -----Original Message----- > From: Erich Kolb [mailto:ekolb@randbreceivables.com] > > Why would a windows95 box not be able to see a Samba file server?Are you covering its eyes? In all seriousness, this question is far too open-ended. I assume you don't want a list of reasons...right?! There's probably a million reasons why a windows 95 box would not be able to "see" a Samba file server. Work your way up the layers. Can you ping this machine? (Make sure you use its network address, eliminate name resolution as a possible point of failure). It's very possible that your problem is not related to samba at all. Once you're certain that IP traffic can travel between these two computers, start to check samba's logs while you're trying to access a share on the samba server. Are you just browsing for the computer, and it doesn't show up in the heirarchy? Have you tried typing in the UNC path to the machine (e.g. "\\netbios-name\share-name") in the shell you're using? -Brian