No, the SID (as I recall from my guilty little store of
NT data) is
generated off hardware to prevent someone from simply putting the name
of a
trusted host on an NT machine and entering it into the
NT domain. If the
SID doesn't match, the machine isn't granted entrance. Therefore, it
would
have to be have been assigned *before* it is connected
to the network,
and
according to our local MCSE, it's totally intrinsic
to the machine's
hardware.
Simple solution is to rename the machine, reboot then go the primary
domain
controller and delete the server then reenter it. go back to the first
and
change the domain and tada it's a domain member. If you want it to be
in a trusted do main thas easier. All this hinges off SID and more
importantly
that NT native networking is netbios(netbeui) even if your running TCP/IP
as it simple does netbios over that.
Windows networking is just *weird* :-P
Not really once you accept the fact that it's netbeui based from it's
legacy
of lanman and DOS. Thats where the domain sillyness comes from.
Until I sorted all that our I found NT to be very secure. ;)
I couldn't get anything to talk to anything even though they were
in the same IP adress range and all. Wierd, yes... very.
Allison