msheppard
10-14-2009, 02:46 PM
So, let me begin by stating that I realize Windows Server 2008 is not yet officially supported.
That aside, I have a rather interesting problem which is far from what I expected when beginning this trial:
I have installed a copy of 32-bit Windows Server 2008 Standard onto an appliance, which seems to be working almost perfectly, with one exception. When I began my testing yesterday, I reached the step in the documentation which says,
"a. Click Start>Command prompt
b. Type ipconfig /all
c. Write down the IP address of the DHCP server..."
except that there was no DHCP server listed when I ran an ipconfig /all. Assuming that this was just a quirk of Windows 2008, I pulled the Server_Windows-1.0.x-1.msi from a different location and proceeded with the rest of the instructions as normal. I used the 2.0.2 version of the TurboGate drivers which installed without a hitch, as did the .msi, and when I check the Device Manager I see a full set of vNICs installed and reporting as operational. Yet, there is still no DHCP server listed in ipconfig /all and worse, there are no 10.x.x.x IP addresses on any of the interfaces.
The appliance is able to "start", meaning once I hit start the boot process begins and I can use the graphical console to sign in, but the process still times out and logs a:
"[233:error s:81]: srv1: VM 'vm.srv1.win08std32nohvTG_install.main.WIN08STD' failed to boot within boot timeout period."
presumably because the appliance is not able to communicate the fact that it has started to the grid controller. This is incredibly perplexing to me, and I have to believe that this is not a normal occurrence (of course I could be wrong). Any idea why this would be happening?
It should be noted that if I assign an IP address manually to any of the interfaces, they are able to pass traffic just fine (I was able to run Windows Updates, etc.); and in fact even without doing so all interfaces are reporting that they are receiving and sending packets.
Thanks in advance!
Matt
CariNet, Inc.
That aside, I have a rather interesting problem which is far from what I expected when beginning this trial:
I have installed a copy of 32-bit Windows Server 2008 Standard onto an appliance, which seems to be working almost perfectly, with one exception. When I began my testing yesterday, I reached the step in the documentation which says,
"a. Click Start>Command prompt
b. Type ipconfig /all
c. Write down the IP address of the DHCP server..."
except that there was no DHCP server listed when I ran an ipconfig /all. Assuming that this was just a quirk of Windows 2008, I pulled the Server_Windows-1.0.x-1.msi from a different location and proceeded with the rest of the instructions as normal. I used the 2.0.2 version of the TurboGate drivers which installed without a hitch, as did the .msi, and when I check the Device Manager I see a full set of vNICs installed and reporting as operational. Yet, there is still no DHCP server listed in ipconfig /all and worse, there are no 10.x.x.x IP addresses on any of the interfaces.
The appliance is able to "start", meaning once I hit start the boot process begins and I can use the graphical console to sign in, but the process still times out and logs a:
"[233:error s:81]: srv1: VM 'vm.srv1.win08std32nohvTG_install.main.WIN08STD' failed to boot within boot timeout period."
presumably because the appliance is not able to communicate the fact that it has started to the grid controller. This is incredibly perplexing to me, and I have to believe that this is not a normal occurrence (of course I could be wrong). Any idea why this would be happening?
It should be noted that if I assign an IP address manually to any of the interfaces, they are able to pass traffic just fine (I was able to run Windows Updates, etc.); and in fact even without doing so all interfaces are reporting that they are receiving and sending packets.
Thanks in advance!
Matt
CariNet, Inc.