windows nt domain is not available for ~2min at startup

[isrc]

Hi folks,
I've setup virtualbox on windows xp hosts which are part of a windows nt domain (the PDC is a FreeBSD/Samba box) and i'm experiencing a weird issue. After powering up the computer, our users must wait 2min before being able to log in with their domain accoung credentials. The error message from windows said that the "<our_domain_name> is not availabe" ! Of course, 2 minutes later, one can successfully log in to the domain.
I've experienced the same issue with vmware server and i guess that it must be related to the virtual network interface created by virtualbox at installation time.
I'm wondering if some of you are experiencing the same issue please and how you fixed it eventually ?

Thanks !

[vbox4me2]

This usually happens with NAT, using Bridge it works immediatly (for me). But with a Bridge each Guest uses its own IP which might cause a problem on some smart routers.

[isrc]

actually the issue isn't with the guest but with the host !? I mean i have this problem as soon as i install virtualbox (without even creating a guest) and it only happens after (re)booting windows xp.
I have a pretty standard samba configuration (witout a wins server) and i thought that others would have run into this...

Thanks.

[vbox4me2]

Ah, that might be a conflicting issue with the Bridge driver on the Host, once thats installed you must rejoin the Host into the domain.

[isrc]

Hi,
thanks for all your help so far ! Will try your trick but i still don't get why some minute laters, one can log into the host whith his domain credential ? There must be something with the bridged network interface. But for sure, the host is still part of the domain...it's just that the login is a bit delayed (~2 min)

Thanks.

[vbox4me2]

The bridging is not 100% watertight, the DC is getting some conflicting responses, for each response it needs to go thru the entire DC, take 10 responses and you'll be waiting awhile, rejoining usually fixes this.

[isrc]

The think is that those clients (this is actually a computer lab) was deployed by a ghost-like system and then joined to the domain. So the virtualbox installation was already done before joining the client :-/