Samba Upgrade Issue

[Chris Morton]

Rick Stevens wrote:

> Chris Morton wrote:
>
>>>>>> I solved both problems earlier today.
>>>>>>
>>>>>> I use my Samba as a PDC, so I already have "security=user".  The 
>>>>>> problem was with this line in the [homes] share:
>>>>>>
>>>>>> "valid users = %S"
>>>>>>
>>>>>> Apparently, this is not permitted in Samba 3.x.  Commenting it 
>>>>>> out solved that problem.
>>>>>
>>>>>
>>>>> Hmmm.  Interesting.  Did testparm kick the line out?
>>>>
>>>>
>>>> Nope.
>>>
>>>
>>> Hmmm.  Then it's still valid.  Do the Windows users have a Linux
>>> account or mapped via a usermap.cfg file?  They don't have an 
>>> individual 
>>
>>
>> All users have a Linux account.
>>
>>>
>>> [username] service associated, do they? 
>>
>>
>> No.
>
>
> After doing a bit of reading, I find in the release notes:
>
> Changes in Behavior
> -------------------
>
> The following issues are known changes in behavior between Samba 2.2 and
> Samba 3.0 that may affect certain installations of Samba.
>
>   1)  When operating as a member of a Windows domain, Samba 2.2 would
>       map any users authenticated by the remote DC to the 'guest account'
>       if a uid could not be obtained via the getpwnam() call.  Samba 3.0
>       rejects the connection as NT_STATUS_LOGON_FAILURE.  There is no
>       current work around to re-establish the 2.2 behavior.
>
> Could that have been what was going on?

I don't think so, because there's no remote DC, just the SAMBA machine 
which is a PDC.  Both clients are Win98SE.