Gerry Tomlinson schrieb: > I'm trying VirtualBox for the first time with V1.4. > > I'm having problems with both windows and linux hosts in getting my XP > SP2 guests to operate correctly with Windows Active Directory. I'm > using host networking. > > If I try to RIS build I get the usual > "Press F12 for network service boot message" - press it, then a get a > message saying "OS Chooser V5.2", there's a delay, then a blank blue > screen.
That's strange. We've successfully installed Windows guests using RIS. Though this is not regularly tested - and unfortunately I have no time to test this in the near future. > If I install XP from CD, all goes fine until I've manually joined the > system to the domain. This works - I can then log in to the domain, but > early in the event log after booting I see: > > "Event 1054 > > Windows cannot obtain the domain controller name for your computer > network. (An unexpected network error occurred. ). Group Policy > processing aborted." > > I've tried various remedies including setting the local policy > > Computer Configuration\Administrative Templates\System\Logon\ - Always > wait for the network at computer startup and logon > > This does sometimes seem to make a difference, and once a system has > had policy applied, it continues to be ok on subsequent reboots. Does the problem occur on fresh boots (when the VM is just started)? Or only on reboots? It could be an issue with the network link being reported as "down" for slightly too long. Maybe VirtualBox boots the guest OS too fast in some sense. Also a packet dump of the traffic on the bridge (with as little host or other VM traffic as possible) could help tracking this down. If you don't have ethereal or wireshark installed you could also use the built-in packet sniffer (see VBoxManage in the manual). -- Dr. Klaus Espenlaub innotek GmbH, http://www.innotek.de _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
