Okay, here's my final issue with this installation. I'm hoping someone can shed some light on it. The setup: Server: IBM AIX 5.2 Samba: 3.0.12 The problem: Samba is insisting on having an smbpasswd entry for all users, and it shouldn't (based on my past experiences). I'm setting up a VERY basic samba install. All it needs to do is enable unix shares to the windows folks. It's NOT a login server, nor a domain master, etc. It simply needs to answer requests for shares, and send them out. From my limited knowledge of this, the process is: Request comes in from Windows client (XP-Pro in this case). In this case, the Windows clients authenticate via an ADS. Samba receives the request, and checks the username, checking it against the unix passwds to find a match. If there is a matching unix ID, then samba will allow the access. This process has never required an smbpasswd file on any other system I've set it up on. Except this one. So my question is, where do I start looking for WHY it can't get the user id from Unix? I've cranked up the log levels, but I'm not seeing anything that helps. I'd be glad to send the logs along to anyone who wants to look that may be able to unravel this mystery. Thank you in advance! -ric
On Thu, Sep 29, 2005 at 10:38:55AM -0600, Ric Tibbetts wrote:> Okay, here's my final issue with this installation. I'm hoping > someone can shed some light on it. > > The setup: > > Server: IBM AIX 5.2 > Samba: 3.0.12 > > The problem: > Samba is insisting on having an smbpasswd entry for all users, and it > shouldn't (based on my past experiences). > > I'm setting up a VERY basic samba install. > All it needs to do is enable unix shares to the windows folks. It's > NOT a login server, nor a domain master, etc. > It simply needs to answer requests for shares, and send them out. > From my limited knowledge of this, the process is: > > Request comes in from Windows client (XP-Pro in this case). In this > case, the Windows clients authenticate via an ADS. > Samba receives the request, and checks the username, checking it > against the unix passwds to find a match. > If there is a matching unix ID, then samba will allow the access.That's not how Samba works. You need to authenticate the incoming password from the client. You can't do this against a UNIX password database, the hashes are incompatible.> This process has never required an smbpasswd file on any other system > I've set it up on. Except this one.I seriously doubt this. I *strongly* recommend you stop working on your computer and go away and read this : http://us2.samba.org/samba/docs/man/Samba-HOWTO-Collection/ This should help with some of the underlying concepts. Jeremy.
On Thu, Sep 29, 2005 at 02:45:59PM -0400, Gary Dale wrote:> A counter-argument is that if you've made it easy to set up servers (a > good thing), then people don't need to know the nitty-gritty details.I've never heard anyone say that before :-).> So far, I've received only a response asking for which exact version of > Samba I was running, but no clues as to how to track down the problem. I > appreciate the work the developers are doing, and I realize that > answering every question is impossible, but I really need some help here!Ok, this *really* sounds like a bug that got fixed for 3.0.20, that's why you haven't got much response. Can you send a debug level 100 of the password change failing and I'll take a look and let you know if that's the case. Jeremy.