Logon in Domain faild

[Thomas66]

Hi,
new here with a funny problem in VirtualBox.

I have a problem every morning loggin in a domain.
Host is WIn7 prof 64Bit. Guest is in Virtualbox 4.2.12 win XP SP3 32Bit.
I created the guest and added it to our domain. No problem
Now every morning the guest failed to log in the domain.
No domain found...
The host is in the domain with the same user as in the guest and loggin in with the host is no problem.
Nework in the guest is bridged.
Now I have to change the network to someone else as bridged. -> I say Internal.
Then after a while I change back to bridget and then I am able to log in the domain.
Also just waiting for some minutes to log in after booting the guest there is no domain found.
Thougt it is a time problem.
Anyone who had the same problem?

Happy to hear your suggestions.

Thomas

[Rootman]

Log in to a local account on the guest, say, administrator. Run ipconfig /all in a CMD Windows and check to see if it's getting an IP address. If it is then ping resources on your network, like your domain controller by IP and then by name. Also double check the HOST networking, make sure it is connected and not just running cached credentials. Have multiple NIC's? Are you binding the guest NIC to the right one? Do an IPCONFIG /RELEASE then an IPCONFIG /RENEW and see if it grabs an IP. Networking turned ON? DHCP Turned ON? TCP/IP configured? Client for MS Networks? NIC "connection" in the VB settings checked? happen to change the NIC type after installation and are the drivers loaded - check the Device Manager. Giving it enough time to get an IP? Some DHCP servers are slow, I've seen it take 30 seconds - typically only the first time has any delay though.

Beyond that please insure that the COMPUTER account is still valid, they CAN be disabled or deleted in AD, perhaps someone else "fixed" it for you? Or deleted an unknown account?

I've done just as you describe and have a number of Windows XP and Windows 7 and 8 hosts up and running fine. If you try and log on with a NON cached account while offline - which typically means one that has NOT been logged in to on THAT machine while connected to the LAN for more than 30 days you will get this error. You can log on with CACHED credentials on the PC and still not be on the network as long as the account was already logged into while the PC was fully connected to the network.

[noteirak]

Your issue is typicaly a guest OS issue, not a Virtualbox issue.

[Thomas66]

Hi Rootman,
will test it during the next days.
As the station is normaly in use, it will take while....
thanks
Thomas