OK. Further info. If I don't migrate the SID on a new user it allows access to the box. Now I've gotta figure out how to generate new SIDs for the users already moved across... And test to see if access still works when the SID isn't migrated across....
-----Original Message----- From: Matthew Western, IT Support, Lonsdale Sent: Thursday, 19 August 2004 11:05 AM To: [EMAIL PROTECTED] Subject: [Samba] Active Directory Migration Tools - breaks samba 2.x.x? Hi, We are migrating from an NT domain to a 2003 AD and using the migration tools to nicely move the users across. However, we have just realized that a user created manually can see a samba 2.0.6 server no worries, but a user that has been migrated using the Migration Tools gets an access denied. Anybody come across this one before? It's probably some bodj work around from microsoft that they've plonked in to make it work and samba playing by all the normal rules goes 'huh, that's now allowed'. I thought it might be the SID migration option that we have turned on so all the permissions come across nicely but the test user I migrated, with no SID mig, still did the same thing? Anybody had this and figured a fix? I know how to work around it, but each user migration suddenly becomes a headache if I can't use the migration tools..... Thanks Matthew -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba