Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm running a lab environment on my W8 laptop, using Hyper-V. I've set up a virtual switch that's internal, but I would prefer to give the internal machines access to the internet.

Ok, why not an external switch then? Well, for starters I only have one NIC and I move my computer between different locations (home, work, etc) so I've DHCP configured on the NIC and I don't want DHCP in the lab environment.

Is there any smart way to get internet access to the virtual network? Bridging the virtual and physical NIC doesn't seem to work any good. I've thought about running a virtual router connected to both the internal switch and an external switch (both Hyper-V virtual switches of course). But Before trying that I figured it might be an easier way?

Since the physical machine runs Win 8 there's no Routing and Remote Access feature on the machine, like it would be on a Win server box.

Any ideas on how to solve this?

share|improve this question
up vote 2 down vote accepted

Shame on me, I just realized that Win 8 can do exactly what I want to do, all I had to do was to share my physical NIC with my internal vNIC and now my internal virtual machines have access to the outside World.

Hopefully this might help someone else.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.