[Samba] problem authenticating win xp machine

[Bart Bekker]

Right. I have here a virgin XP pc working flawless with samba 2.2.6.
Currently I want to upgrade to samba 3.0.0.
If you can tell me what patches you suspect of being the cause, please 
tell me, I have an unused XP machine to play with here and I will tell 
you the results (for samba 2.2.6).

 Bart

Ed Holden wrote:

> There definitely is something odd with XP.  I was able to join an XP 
> client to my organization's Samba 2.2.x domain, but had problems 
> thereafter.  The signorseal patch was installed, and I tried other 
> tweaks as well.  I suspect that installing Service Pack 1 or a patch 
> might have "broken" it - have you tried this on an unpatched XP 
> installation?  Dangerous as this is, I'd be interested to know if 
> anyone has compared using virgin XP with patched XP on a Samba domain.
>
> Ultimately I fixed this problem by upgrading the XP client to Windows 
> 2000.  Hate to say it, but if you find yourself investing a lot of 
> time in tweaking XP your best option might be a rollback, since 2000 
> seems to cause the least problems, but supports basically the same 
> software and hardware as XP.
>
> :: Ed Holden
> :: Administrator, Research Information Systems
> :: McLean Hospital
>
> George Farris wrote:
>
>> This seems quite common.  I have an associate that can join the machine
>> to the domain but can't login with XP.  Window 200 works fine and yes
>> all the registry patches are in.
>>
>> I suggest there might be something screwy with 3.0.0. and XP.
>>
>>
>> On Wed, 2003-11-12 at 05:52, kyle wrote:
>>
>>> On Wed, 12 Nov 2003 15:08:07 +0200
>>> Bart Bekker wrote:
>>>
>>>
>>>> Sounds like a typical misstake; did you apply the signorseal patch 
>>>> in the windows xp registry?
>>>>
>>>> from the how-to I quote:
>>>>
>>>> To join a Samba Domain, you will need to first make the following 
>>>> changes to your registry and reboot:
>>>>
>>>>    
>>>> [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parame
>>>>    ters]
>>>>
>>>>    "requiresignorseal"=dword:00000000
>>>>    "signsecurechannel"=dword:00000000
>>>
>>>
>>> yep, already did this... :-)
>>>
>>> I am successfully welcome on the domain when I change form workgroup
>>> (previous setting) to the domain Domaula (using the root account).
>>>
>>> The odd thing is I get this error :
>>>
>>> [2003/11/12 12:41:25, 2] auth/auth.c:check_ntlm_password(309)
>>>  check_ntlm_password:  Authentication for user [] -> [] FAILED with 
>>> error
>>> NT_STATUS_NO_SUCH_USER
>>>
>>> there should be an user name on "Authentication for user [FOO]", 
>>> shouldn't
>>> it? :-)
>>>
>>>
>>>
>>> (Bart, watch out that you answered me directly, and did not include the
>>> samba list :-) tnx! )
>>>
>>>
>>>
>>> -- 
>>> Window$ Macht Frei!
>>
>
>
>
> Any information, including protected health information (PHI), 
> transmitted
> in this email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential 
> and or
> exempt from disclosure under applicable Federal or State law. Any review,
> retransmission, dissemination or other use of or taking of any action in
> reliance upon, protected health information (PHI) by persons or 
> entities other
> than the intended recipient is prohibited. If you received this email 
> in error,
> please contact the sender and delete the material from any computer.