3.0.4 Can't connect to domain issue

[pwstory]

All, I've been using VB since 1.6. I have recently built several test VM's by building an initial XP VM and then cloning it to the other 2 VM's. I use the same network setup on all three as only 1 would be active at any given time. This worked really well with VB 3.0.2.

After installing VB 3.0.4 I began to get logon messages indicate that Windows could not connect to the domain. The only way around this is to rejoin the domain. The frustrating machine is everytime I switch to a different VM I have to do it again. It isn't a case of just once as I had hoped.

Example I rejoining the domain on VM1 and reboot to make sure it works. It does; it connects fine. I start VM2 and do the same thing because it can't connect to the domain. Same process as before and I'm up and running. I then close down VM2 and launch VM1 again. I'm met with the Windows cannot connect to the domain box again.

I thought going back to 3.0.2 would fix the problem; unfortunately, it did not.

Has anybody got a fix for this. It is very frustrating, and makes testing a cumbersome task.

Thanks for any help in advance

[vbox4me2]

Did you sysprep all VM's prior to adding them to the domain? you have to do this in order for the SID to be unique, right now it sounds like they are all the same hence the domain seeing tripple. 3.02 might have blocked some parts that 3.04 doesn't.

[pwstory]

Thanks for the reply.

No I didn't know I need to do that. Is it something I can do after the fact? It is odd that if 3.0.2 was ignoring it it no longer ignores it. I've downgraded and still have the same problem.


Thanks

[vbox4me2]

Read up on it a bit: http://www.google.nl/search?hl=nl&sourc ... main&meta=