A windows question: joining XP to a samba 3.0 domain - Lilux-help

8 Jul 2005

...
 On Tuesday 31 August 2004 08:03, Eric Dondelinger
wrote:
/ Hi, />/
/>/ On Mon, 30 Aug 2004, Henri Majerus wrote:
/>/ > On Mon, 2004-08-30 at 09:45, Alain Knaff wrote:
/>/ > > All went fine until the very end. After cloning our newly set up
/>/ > > client to the 9 others we noticed that we could no longer join the
/>/ > > domain:
/>/ >
/>/ > I presume your problem is only with the windows clones...
/>/ >
/>/ > In fact windows identifies windows 2000 and XP computers on a domain not
/>/ > only by name but also by SID. On cloned computers this is a problem!
/>/
/>/ Yup, that's plausible.
/>/
/>/ > I newer checked for a solution since I don't have the need for a domain
/>/ > but here one result of a google search:
/>/ >
/>/ > http://www.sysinternals.com/ntw2k/source/newsid.shtmls...
/>/
/>/ There is also some "sysprep" utility to use on the "master"
/>/ before cloning an MS Windows machine, which allows to remove
/>/ such specifics - no idea though how this gets (re)set after
/>/ cloning - I guess it's a case for RTFM'ing ;-)
/>/
/>/ Greets & hth, Eric
/>
...
 Thanks for your suggestions. What finally helped were
the following
two steps:

1. We checked "My Network Places" and it contained shortcuts to one (or more)
shares that were previously mounted. We deleted these
2. We put "map to guest = Never" into smb.conf (instead of "map to guest =
Bad
user")

After both changes, everything worked fine. Apparently, XP is very
liberal in what it considers a "connection". For instance, it includes
items such as shortcuts in "My Network Places", and possibly even
network printer definitions.

Probably change #2 worked because one of these hidden "connections"
was made using an non-existant username (which samba mapped to guest
before our change to smb.conf).

At the beginning of the LLL project we did use Newsid, but apparently
this is mostly needed for a workgroup configuration (rather than
domain), or at least it was at the time.

Alain 
Hi

In my case, solution was that I disconnect anonymously mapped shares. Right click
on "My Computer" and select "Disconnect Network Drive".

Jan