![]() ![]() Since it works fine when the system boots, I've ruled out problems with network switches or configuration problems with the install setup on the windows image. I can ping the ghost console server and the ghost console server can ping my client and connect to the client via the windows domain. ghost conosle doesn't see the system listed. If I boot the windows drive from vmware, the ghost client shows a red x and says looking for ghost server. If I boot the windows drive naitivly from grub, ghost client starts up and the ghost console sees the system as connect. Ideally, we would like to have ghost work wether it's booted locally off the disk or via vmware so that we can push software and what not in either mode (or kick off vmware in linux to push an install to the windows disk without having to reboot) however, the mac address is different since I'm running a bridged network when booting via vmware I don't know if that matters, but I thought it may apply some how. ![]() wether the windows os boots from grub or from vmware, the system comes up with the same computer name and same ip. I can also boot the windows drive via vmware server 1.0.3 in linux. I can boot either linux or windows from grub when I power on the system. I've got a setup where by I have a hard drive in my system with debian etch 64bit linux and a hard drive with windows xp. I've seen some others with this issue, but still need some help. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |