Bug 2197 - Migration NT4 / W2K3 AD with SAMBA 3 Member Server
Summary: Migration NT4 / W2K3 AD with SAMBA 3 Member Server
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: winbind (show other bugs)
Version: 3.0.9
Hardware: x86 Linux
: P3 regression
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-29 04:11 UTC by Menendez Eric
Modified: 2005-09-29 09:00 UTC (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Menendez Eric 2004-12-29 04:12:00 UTC 
I configured a FileServer SAMBA 3.0.10 (Winbindd+ACL) on a Fedora CORE 2, as 
Server member of a domain NT4 (Fr Enterprise Edition).  

I realized an Active model Directory under W2k3 (UK Std Edition) in order to 
carry out a progressive migration of NT towards AD W2K3.  

All the prérequis were respected, passage in native method of the KDC to use 
ADMT V2, migration of the User/group/passwd of the DomNT4 with sIDHistory, 
towards domADW2K3.  

At the time of the migration of the posts user (Nt,w2k & Xp Fr.) towards the 
new domADW2K3, the acces to the resources of the SAMBA Server is refused ?  

Scenario: 
The User 'domNT/UserA' have right acces to //samba/repA share.
If this same User opens a session on 'domADW2K3/UserA', acces deny 
on //samba/repA.  

I Think that Samba Server does not do the link sIDHistory between 'domNT/UserA' 
and 'domADW2K3/UserA'?

I tested with Rpm SAMBA 3.0.3, 3.0.7, 3.0.9 and 3.0.10: Non determined problem

Maybe have you an idea ?
Comment 1 Gerald (Jerry) Carter (dead mail address) 2005-09-29 09:00:51 UTC 
please retest against 3.0.20