I think I figured it out. With the "security = server" setting and Samba 3 the user connecting needs to have an account on the Samba machine to connect. Looking through the documentation I am guessing that the behavior change in Samba 3 (which eliminates the need to keep connections open to the PDC doing authentication) had a side effect of relying on there being a user account on the Samba machine. Changing the Samba machine to "security = share" (which I tried today after doing all the digging over the past few days) made everything work. The reason it only affected some workstations is that most users do not have user accounts on the Samba servers - but I do, and the light went on when I logged in as myself & things worked. Duh.

In the man page for smb.conf in Version 3 is the statement that "security = server" is equivalent to "security = user" from the client's POV. Under Samba 2.2 this was not the case.

Todd A. Jacobs wrote:

On Mon, Jan 17, 2005 at 02:52:25PM -0800, Ed Jaeger wrote:


As time went by things just worked through various updates - until I
updated from Samba 2.2 to Samba 3.0.  At this point SOME Windows


Samba 3 is a pretty significant rewrite. If I were you, I'd use SWAT to
review your configuration, as well as comparing it to the default
configuration which ships with your distro's current version. I'd also
revisit your lpd/cups configuration afterwards, to ensure that it's
compatible with the latest release of Samba.

Since I haven't had this particular problem myself, I can't offer any
better advice than that. But at least it's a place to start!


-- Ed Jaeger, President & CFO, Bohlender-Graebener Corporation [EMAIL PROTECTED] http://www.bgcorp.com ---

_______________________________________________
RLUG mailing list
[email protected]
http://lists.rlug.org/mailman/listinfo/rlug

Reply via email to