Yeah ... one would think the presence of two virtual adapters would work. One adapter is defined in VirtualBox as NAT and defined in Windows 7 as using DHCP in order to communicate to the world at large through the cable modem. The other adapter is defined as intnet and correspondingly has a static IP address of the private subnet.

So much for theory. Just couldn't get that to work. Using ipconfig /all I could see the adapter to the private subnet saying DHCP was disabled ... yet it seemed to pickup the IP , gateway and DNS addresses from my ISP. Weird, huh?!

In my investigation, I learned that VirtualBox has a built-in DHCP service. And it occurred to me that perhaps my ISP and VirtualBox used the same subnet by coincidence. (Not likely, but possible... maybe... well not really, but... ) The service is off by default, and the problem didn't go away when I explicitly disabled it.

Doesn't matter. I'm a happy camper with things as they are. It is easy enough to switch between private and the ISP's subnets.

Hi there. I encountered this problem last week. It turns out that the problem is caused by the host CPU's ability to accommodate 64 bit virtual machines. Specifically a CPU's lack of support for 'VT' mode. I was trying to get a Svr 2008 x64 VM up and running using VMWare Player, encountered this problem and was surprised to find that that my Intel Core 2 Quad Q8200 CPU didn't have this functionality. VMWare Player's error message was fairly useful in this case.

Will use the 32 bit version of Server 2008 instead!

I'm not a complete dummy when it comes to network configuration, but I'm not looking forward to configuring these VMs to be segregated from my host PC and other devices getting their IP addresses from my router.

I know where you are coming from. I too am required to use Server 2008, and not Server 20089 R2 or the new Server 2012 (both of which are 64-bit only).

I ought to be able to buy a new Intel Vx machine soon. I've had a lot of time to think about it, and I'll probably have Server 2008 R2 (or 2012) as my virtual machine host. I'm not decided whether to continue using a dual-boot approach -- i.e. one OS for my personal PC, and one OS for my lab. For sure I'll be loading it with a lot of RAM 12-16Gb, and a SSD.

I think some of my lab internal network issues will go away by having Server 2008 R2 as my host vm. Honestly though, I have not thought about it much. Having an internal-only network works fine for most purposes. I think I read somewhere that VMWare's network architecture was more robust than that of Virtual Box. I'll probably look at that when I get closer to buying the new PC.

Dual booting into an install of Server 2008 is a good idea. You can then use the x64 version if you wanted.

I sometimes find that I get carried away or distracted when tinkering with my VMs from within my day-to-day workstation OS, so the above would provide a more cleaner lab environment I suppose. I may consider it...

It sounds like you have a nice machine planned.

I'm using duel boot now: Windows Vista Home Premium for my personal use; and Windows 7 Ultimate (32-bit) for a lab. I wanted a lab environment that I felt I could trash and not worry about the consequences. That was the original idea, anyway.

Turns out my Vista environment was not as safe and protected as I thought. Good thing I still had recent backups -- Carbonite and a hard drive that I had replaced and not reinstalled/reused. To this day I am not 100% sure what caused the loss of the Vista partition, but I think I may have mistakenly thought I was doing a clean install of Win7 on a VHD when I was actually targeting my Vista partition late one night. Virtual machine or not, I'm a lot more careful now.

Using VHDs is becoming second nature to me now, and I may opt to use only VHDs in my next PC. Might make things more safe too -- hey! haven't we been there before?!

The move to a new PC is one of necessity. I'm at a point where I need to lab an enterprise-like environment. Windows Server now only comes in a 64-bit flavor, and to run as a guest vm I need to have hardware virtualization functionality in the motherboard. Need a new power supply (now only 350 W) too, not to mention my graphics card is in need of being replaced. And an SSD drive should help. So as you see, I'm outgrowing the current setup and need something new.

Interesting... well at least the silver lining to those kinds of mistake is that you learn from them! Good that you had backups.

My only exposure to VHDs so far is via straight virtualisation. I'm sure that when I get to that module in the course I'll understand better how the use of them has been integrated into W7.

It sounds like they can be utilised almost as an alternative to physical disk partitions.

I understand your reasons for the workstation upgrade. Are you running purely trial versions?

Apart from the licensed Windows client software (duel boot, Vista and Win7), all my virtual guest machines are evaluation copies downloaded from Microsoft.

I intend to get a Microsoft technet subscription so that I can download all the newest Microsoft software. Sounds very cost-effective. I also read somewhere that there are no time limitations that one finds in evaluation versions of the software. It will give me access to SCCM, the latest Outlook and other server-side enterprise software to educate myself on.

For the moment, though, it is a "chicken or egg" situation. The most-current server-side microsoft software is 64-bit only, and I do not have the virtual-technology feature in my motherboard to take advantage of 64-bit virtual guest machines in OpenBox.

What I'm sure to end up doing is buying a second-hand, high-powered, game PC on eBay or Craigslist. I'll add or replace components, and buy some software (likely Server 2008 R2, and possibly VMWare). The cost savings will be used to pay for the Technet subscription and perhaps a second-hand laser printer.

I already own three Cisco switches and routers. If it is truly impossible to implement VPN within an OpenBox network environment, I could conceivably hook up my existing and future PC's through my own home-based real WAN network. Not intending to this, you hear. But it is conceivable.

@stellar_mass: What are you using to study for the 70-680? It is an understatement to say it is a difficult test. I used two textbooks, the Microsoft Academy online lab, and (later) my own lab. Had I not lab'ed and studied details about command-line programs through the internet, I would have surely failed it. Luckly, I sweaked by. I'm studying for the 70-685 right now.

Good stuff? I've not encountered OpenBox. A quick google indicates that it's a Linux-based window manager?

Well, I got the MCDST a year and a half ago, and before looking at some SQL Server certs I decided I'd try the 70-682 upgrade exam. I understand that the study material is the same as the 680 and 685 put together.

I recent bought a Technet subscription which included 1 choice of online training materials - I chose the 70-680 option. I also have access to some general W7 training resources through my employer's volume license agreement. So my plan is to go through these and the Prof's video course (have the MS Press Windows 7 Resource Kit for general reference), then try some practice exams. Depending on how I perform I'll then look at some course books and broach 685.

I'm not sure if having the MCDST will be an advantage or not... Certainly not going in to it expecting that to be the case.

My bad. I meant to say VirtualBox -- not OpenBox.

If you enjoy database subject matter, go for it! Succumbing to a passion is justification enough.

Tell me, @ stellar_mass, is the Technet training material worth the extra $$$? I remember looking at the 1-option plan and was asking myself that question.

My usual approach to training is to buy a couple recent books, and when some topic interests me I drill down to whatever the search engines point me toward. Oh yeah: lab it until you can do it by memory. Its the only way to really learn something -- which will be forgotten most probably over time. Not Alzheimers; just not using the knowledge and it and after a while it becomes fuzzy. My Japanese has gotten so bad. A (Japanese) relative wanted her 6 year-old daughter to say something in English to her "gaijin" grand-uncle (me). I stumbled terribly over my Japanese. Embarassing to know you are speaking weird Japanese all the while it coming from your mouth. Wife (also Japanese) is nudging me to join a local English-Japanese Toastmasters Club.

Well, I went for the cheapest TechNet option (Standard), which included one choice of 'e-learning collection'. It will only really be value for money if I make use of all the benefits I think!

I think your approach is a wise one. With the MCDST I had the benefit of having supported XP clients every day for 3-4 years. I was involved in rolling W7 out at the same organisation, but didn't stay long enough to get the same kind of exposure.

I know what you mean regarding forgetting info over time! You do often really need to be using it on a daily basis for it to remain there. I'm sure I remember only a small fraction of the degree I finished just over ten years ago.

I'm not surprised your Japanese is rusty - what a difficult language to learn. I am a bit of a Japanophile though I have to admit! You must get to enjoy some great food. Are we a bit off-topic now?