Vista - Networking issues with Hyper-V

Good morning, Please read before just assuming RTFB, I spent considerable
time last night reading through (about 8 pages) of the networking topics
here, couldn't find an answer to my problem, I'm sure though that it is
something rather simple that has escaped my attention as I am new to the VLAN
thing (Yes I read the article on Virtual Guys website)

That being Said...

Dell R710 4 NIC Ports
Hyper-V Server 2008 R2
Windows EBS 2008

I can network between the Virtual PCs, I can join the Hyper-V management to
the domain. Outside of that, I cannot get into, or out of the "box".
NIC 1 is a T1 Router, and I tried following the suggestion of "Installing
Windows EBS on virtual machines" (cc947757) Pg. 2 I don't quite understand
the way that I am supposed to setup the Nic that connects to the internet on
the security server, our Block is .81/24 (.81 is router, and 83-86 as usable
IPs) which I have setup on physical nic through hyper-v. EBS SS I assigned
..84 with a gateway of .86.

I also cannot connect through internal, i can only connect through nic that
just sits there for management.

As far as the VLANs, (I am sure i did something wrong here)
my internal lan I set VLAN id checkbox, and set all to "2" and my external
lan I set vlan checkbox and set all to "3"

I would greatly appreciate any feedback (Except to tell me that I am being
thick)

Regards,

"MasterSheex" <MasterSheex@newsgroup> wrote in message
news:1AD40211-21A0-4BAE-8EDD-62B9A154F55F@newsgroupI have had a look at that article and I am not surprised that you are
confused.

Regarding VLANs, you can ignore them unless your physical LAN is using
them. They can only be used on virtual networks which connect to a physical
network which has VLANs configured.

How many NICs do you have in the physical computer? As long as you have
at least two, reserve one for management. (This is for remote management of
Hyper-V. Nothing to do with EBS management).

Create an external virtual network linked to a NIC in the host which can
access the Internet. This is the network to which you connect the external
or public NIC of your security server. (Internet Virtual Network in the
diagram). The public NIC will be in the same IP subnet as your physical
router and will use the physical router as its gateway.

You only need to use an internal virtual network if the client machines
are physical machines. (This is the third NIC and third network in the
diagram). If you are simply testing the setup I would create a private
virtual network (not linked to any physical NIC) to act as your private LAN.
You can install a client OS in another vm on this network for testing. When
you create your DC, link it to this network and give it a static IP in its
own IP subnet. (192.168.1.1 in the diagram).

The machines on this private network can only access the Internet
through the security server. The security server has its public NIC linked
to the Internet through the public virtual network. Its private NIC in
linked to the private virtual network and it is the default gateway for this
network (not required if the clients use proxy server).

You say that you cannot connect to anything but the host and the Hyper-V
console. That is as it should be. As far as you EBS setup is concerned, you
are an interloper from the Internet and you should not be able to access
anything. To be inside the network you need to connect to the vm from the
Hyper-V console, or allow remote access through the security server.

Ok, I did a little poking around, and it seems that if I follow the drawing
and your suggestions, I can get the virtual networks to work nicely if I
install Windows 2008 Server Standard and add Hyper-V role (Beta), I can
create VMs and they can network and everything seems to work fine. It appears
that I only have an issue with Hyper-V Server 2008 R2, It almost looks like
the Hyper-V firewall is blocking everything, but even if I turn it off, it
still does.

As far as the VLans my network does not use them, and on the above scenario,
I didn't use them. But when I tried (and I reinstalled Hyper-v 3 times now)
It seemed that I had to use the VLAN to get any communication.

"Bill Grant" wrote:

There was a change to the way virtual networks are created between 2008
and 2008 R2. I found that it made things simpler, not more complicated.

Did you accept the offer to reserve one NIC for administration? (This is
the recommended config). If you do, you cannot connect directly to machines
on the private virtual network (as explained earlier). I suspect that with
2008 you are running admin on a NIC which also connects to the private
virtual network. This is not recommended and effectively bypasses your
security server!


"MasterSheex" <MasterSheex@newsgroup> wrote in message
news:0C20085B-1E9E-4D3A-BB87-3B1268AEC01A@newsgroup