Hi

On a full installation of W2k8 Enterprise I have Hyper-V (single physical
server).
Integration services are installed on all VMs.

All network-connections in the VMs have "limited or no connectivity" with an
IP of 169.x.x.x.
In case of normal connection, the VMs would obtain an IP from a DHCP Server
in the range of 192.168.x.x
The physical network adapter is on a brand new intel-mainboard (S5000XVN):
Intel Pro/1000 EB Network Connection with I/O Acceleration.



I chosed "external network type" in Virtual Network Manager and all VMs have
the VLAN ID 1.
What I discovered is, that the physical network adapter does not show the
point "VLAN ID" under Device-Manager/Network adapters/Intel
Nic/Properties/Advanced/Property.
Is this the reason, why my VMs have no connection?
Or what is the reason for this isolation of the VMs?

Thanks for your help.

Patrick

Do you have any DHCP server _on that VLAN_? If not, there's no way they'll
get an IP address, is there?

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Patrick D." <PatrickD@xxxxxx> wrote in message
news:793DB2CA-4CAB-4527-9904-F4016655DC8A@xxxxxx

> Hi
>
> On a full installation of W2k8 Enterprise I have Hyper-V (single physical
> server).
> Integration services are installed on all VMs.
>
> All network-connections in the VMs have "limited or no connectivity" with
> an
> IP of 169.x.x.x.
> In case of normal connection, the VMs would obtain an IP from a DHCP
> Server
> in the range of 192.168.x.x
> The physical network adapter is on a brand new intel-mainboard (S5000XVN):
> Intel Pro/1000 EB Network Connection with I/O Acceleration.
>
> I chosed "external network type" in Virtual Network Manager and all VMs
> have
> the VLAN ID 1.
> What I discovered is, that the physical network adapter does not show the
> point "VLAN ID" under Device-Manager/Network adapters/Intel
> Nic/Properties/Advanced/Property.
> Is this the reason, why my VMs have no connection?
> Or what is the reason for this isolation of the VMs?
>
> Thanks for your help.
>
> Patrick

Hi

does that mean, that with an "external network" an hyper-v solution on one
physical server can not communicate with a physical dhcp, which is not on
this physical machine?

Patrick

"Charlie Russel - MVP" wrote:

> Do you have any DHCP server _on that VLAN_? If not, there's no way they'll
> get an IP address, is there?
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
> "Patrick D." <PatrickD@xxxxxx> wrote in message
> news:793DB2CA-4CAB-4527-9904-F4016655DC8A@xxxxxx

> > Hi
> >
> > On a full installation of W2k8 Enterprise I have Hyper-V (single physical
> > server).
> > Integration services are installed on all VMs.
> >
> > All network-connections in the VMs have "limited or no connectivity" with
> > an
> > IP of 169.x.x.x.
> > In case of normal connection, the VMs would obtain an IP from a DHCP
> > Server
> > in the range of 192.168.x.x
> > The physical network adapter is on a brand new intel-mainboard (S5000XVN):
> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
> >
> > I chosed "external network type" in Virtual Network Manager and all VMs
> > have
> > the VLAN ID 1.
> > What I discovered is, that the physical network adapter does not show the
> > point "VLAN ID" under Device-Manager/Network adapters/Intel
> > Nic/Properties/Advanced/Property.
> > Is this the reason, why my VMs have no connection?
> > Or what is the reason for this isolation of the VMs?
> >
> > Thanks for your help.
> >
> > Patrick

>
>

No, it means that with an external network in hyper-v, the _physical_ nic
doesn't have an IP address or run TCP/IP at all. If you set your network to
be on a vlan, it doesn't communicate with other computers that aren't on
that vlan.

Hyper-V networking is very different from anything we've worked with
before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by configuring
without any vlan stuff, make sure you get everything working. If you need
DHCP to the computers that are on the vlan, you'll want to make sure you
have a DHCP server that will be on that same vlan.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Patrick D." <PatrickD@xxxxxx> wrote in message
news:35480BD0-DFAC-4DA4-8E7D-98539FC16D6D@xxxxxx

> Hi
>
> does that mean, that with an "external network" an hyper-v solution on one
> physical server can not communicate with a physical dhcp, which is not on
> this physical machine?
>
> Patrick
>
> "Charlie Russel - MVP" wrote:
>

>> Do you have any DHCP server _on that VLAN_? If not, there's no way
>> they'll
>> get an IP address, is there?
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> news:793DB2CA-4CAB-4527-9904-F4016655DC8A@xxxxxx

>> > Hi
>> >
>> > On a full installation of W2k8 Enterprise I have Hyper-V (single
>> > physical
>> > server).
>> > Integration services are installed on all VMs.
>> >
>> > All network-connections in the VMs have "limited or no connectivity"
>> > with
>> > an
>> > IP of 169.x.x.x.
>> > In case of normal connection, the VMs would obtain an IP from a DHCP
>> > Server
>> > in the range of 192.168.x.x
>> > The physical network adapter is on a brand new intel-mainboard
>> > (S5000XVN):
>> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
>> >
>> > I chosed "external network type" in Virtual Network Manager and all VMs
>> > have
>> > the VLAN ID 1.
>> > What I discovered is, that the physical network adapter does not show
>> > the
>> > point "VLAN ID" under Device-Manager/Network adapters/Intel
>> > Nic/Properties/Advanced/Property.
>> > Is this the reason, why my VMs have no connection?
>> > Or what is the reason for this isolation of the VMs?
>> >
>> > Thanks for your help.
>> >
>> > Patrick

>>
>>

Hi Charlie

well, then I should go away from this test-solution, with external dhcp. The
final configuration will have a SBS 2008 (with dhcp) virtually on the same
vlan like all other servers.
Will this virtual SBS 2008 be able to give an IP to physical clients in the
same domain?

Patrick

"Charlie Russel - MVP" wrote:

> No, it means that with an external network in hyper-v, the _physical_ nic
> doesn't have an IP address or run TCP/IP at all. If you set your network to
> be on a vlan, it doesn't communicate with other computers that aren't on
> that vlan.
>
> Hyper-V networking is very different from anything we've worked with
> before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by configuring
> without any vlan stuff, make sure you get everything working. If you need
> DHCP to the computers that are on the vlan, you'll want to make sure you
> have a DHCP server that will be on that same vlan.
>
> --
> Charlie.
> http://msmvps.com/blogs/xperts64
> http://mvp.support.microsoft.com/profile/charlie.russel
>
> "Patrick D." <PatrickD@xxxxxx> wrote in message
> news:35480BD0-DFAC-4DA4-8E7D-98539FC16D6D@xxxxxx

> > Hi
> >
> > does that mean, that with an "external network" an hyper-v solution on one
> > physical server can not communicate with a physical dhcp, which is not on
> > this physical machine?
> >
> > Patrick
> >
> > "Charlie Russel - MVP" wrote:
> >

> >> Do you have any DHCP server _on that VLAN_? If not, there's no way
> >> they'll
> >> get an IP address, is there?
> >>
> >> --
> >> Charlie.
> >> http://msmvps.com/blogs/xperts64
> >> http://mvp.support.microsoft.com/profile/charlie.russel
> >>
> >> "Patrick D." <PatrickD@xxxxxx> wrote in message
> >> news:793DB2CA-4CAB-4527-9904-F4016655DC8A@xxxxxx
> >> > Hi
> >> >
> >> > On a full installation of W2k8 Enterprise I have Hyper-V (single
> >> > physical
> >> > server).
> >> > Integration services are installed on all VMs.
> >> >
> >> > All network-connections in the VMs have "limited or no connectivity"
> >> > with
> >> > an
> >> > IP of 169.x.x.x.
> >> > In case of normal connection, the VMs would obtain an IP from a DHCP
> >> > Server
> >> > in the range of 192.168.x.x
> >> > The physical network adapter is on a brand new intel-mainboard
> >> > (S5000XVN):
> >> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
> >> >
> >> > I chosed "external network type" in Virtual Network Manager and all VMs
> >> > have
> >> > the VLAN ID 1.
> >> > What I discovered is, that the physical network adapter does not show
> >> > the
> >> > point "VLAN ID" under Device-Manager/Network adapters/Intel
> >> > Nic/Properties/Advanced/Property.
> >> > Is this the reason, why my VMs have no connection?
> >> > Or what is the reason for this isolation of the VMs?
> >> >
> >> > Thanks for your help.
> >> >
> >> > Patrick
> >>
> >>

>
>

Of course. But in that case I would not put it on an external network. I
would run the SBS domain on a private virtual network. You can then use DHCP
on this network and not interfere with the DHCP service on the physical LAN.


"Patrick D." <PatrickD@xxxxxx> wrote in message
news:E9AE8922-C5D1-4D91-9851-F4191C2E3CFE@xxxxxx

> Hi Charlie
>
> well, then I should go away from this test-solution, with external dhcp.
> The
> final configuration will have a SBS 2008 (with dhcp) virtually on the same
> vlan like all other servers.
> Will this virtual SBS 2008 be able to give an IP to physical clients in
> the
> same domain?
>
> Patrick
>
> "Charlie Russel - MVP" wrote:
>

>> No, it means that with an external network in hyper-v, the _physical_ nic
>> doesn't have an IP address or run TCP/IP at all. If you set your network
>> to
>> be on a vlan, it doesn't communicate with other computers that aren't on
>> that vlan.
>>
>> Hyper-V networking is very different from anything we've worked with
>> before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by
>> configuring
>> without any vlan stuff, make sure you get everything working. If you need
>> DHCP to the computers that are on the vlan, you'll want to make sure you
>> have a DHCP server that will be on that same vlan.
>>
>> --
>> Charlie.
>> http://msmvps.com/blogs/xperts64
>> http://mvp.support.microsoft.com/profile/charlie.russel
>>
>> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> news:35480BD0-DFAC-4DA4-8E7D-98539FC16D6D@xxxxxx

>> > Hi
>> >
>> > does that mean, that with an "external network" an hyper-v solution on
>> > one
>> > physical server can not communicate with a physical dhcp, which is not
>> > on
>> > this physical machine?
>> >
>> > Patrick
>> >
>> > "Charlie Russel - MVP" wrote:
>> >
>> >> Do you have any DHCP server _on that VLAN_? If not, there's no way
>> >> they'll
>> >> get an IP address, is there?
>> >>
>> >> --
>> >> Charlie.
>> >> http://msmvps.com/blogs/xperts64
>> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >>
>> >> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> >> news:793DB2CA-4CAB-4527-9904-F4016655DC8A@xxxxxx
>> >> > Hi
>> >> >
>> >> > On a full installation of W2k8 Enterprise I have Hyper-V (single
>> >> > physical
>> >> > server).
>> >> > Integration services are installed on all VMs.
>> >> >
>> >> > All network-connections in the VMs have "limited or no connectivity"
>> >> > with
>> >> > an
>> >> > IP of 169.x.x.x.
>> >> > In case of normal connection, the VMs would obtain an IP from a DHCP
>> >> > Server
>> >> > in the range of 192.168.x.x
>> >> > The physical network adapter is on a brand new intel-mainboard
>> >> > (S5000XVN):
>> >> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
>> >> >
>> >> > I chosed "external network type" in Virtual Network Manager and all
>> >> > VMs
>> >> > have
>> >> > the VLAN ID 1.
>> >> > What I discovered is, that the physical network adapter does not
>> >> > show
>> >> > the
>> >> > point "VLAN ID" under Device-Manager/Network adapters/Intel
>> >> > Nic/Properties/Advanced/Property.
>> >> > Is this the reason, why my VMs have no connection?
>> >> > Or what is the reason for this isolation of the VMs?
>> >> >
>> >> > Thanks for your help.
>> >> >
>> >> > Patrick
>> >>
>> >>

>>
>>

Hi

my final solution will only have one dhcp. The sbs 2008 virtualized. Can I
still put the single physical server hyper-v solution on a external network
in this case?

Patrick

"Bill Grant" wrote:

> Of course. But in that case I would not put it on an external network. I
> would run the SBS domain on a private virtual network. You can then use DHCP
> on this network and not interfere with the DHCP service on the physical LAN.
>
>
> "Patrick D." <PatrickD@xxxxxx> wrote in message
> news:E9AE8922-C5D1-4D91-9851-F4191C2E3CFE@xxxxxx

> > Hi Charlie
> >
> > well, then I should go away from this test-solution, with external dhcp.
> > The
> > final configuration will have a SBS 2008 (with dhcp) virtually on the same
> > vlan like all other servers.
> > Will this virtual SBS 2008 be able to give an IP to physical clients in
> > the
> > same domain?
> >
> > Patrick
> >
> > "Charlie Russel - MVP" wrote:
> >

> >> No, it means that with an external network in hyper-v, the _physical_ nic
> >> doesn't have an IP address or run TCP/IP at all. If you set your network
> >> to
> >> be on a vlan, it doesn't communicate with other computers that aren't on
> >> that vlan.
> >>
> >> Hyper-V networking is very different from anything we've worked with
> >> before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by
> >> configuring
> >> without any vlan stuff, make sure you get everything working. If you need
> >> DHCP to the computers that are on the vlan, you'll want to make sure you
> >> have a DHCP server that will be on that same vlan.
> >>
> >> --
> >> Charlie.
> >> http://msmvps.com/blogs/xperts64
> >> http://mvp.support.microsoft.com/profile/charlie.russel
> >>
> >> "Patrick D." <PatrickD@xxxxxx> wrote in message
> >> news:35480BD0-DFAC-4DA4-8E7D-98539FC16D6D@xxxxxx
> >> > Hi
> >> >
> >> > does that mean, that with an "external network" an hyper-v solution on
> >> > one
> >> > physical server can not communicate with a physical dhcp, which is not
> >> > on
> >> > this physical machine?
> >> >
> >> > Patrick
> >> >
> >> > "Charlie Russel - MVP" wrote:
> >> >
> >> >> Do you have any DHCP server _on that VLAN_? If not, there's no way
> >> >> they'll
> >> >> get an IP address, is there?
> >> >>
> >> >> --
> >> >> Charlie.
> >> >> http://msmvps.com/blogs/xperts64
> >> >> http://mvp.support.microsoft.com/profile/charlie.russel
> >> >>
> >> >> "Patrick D." <PatrickD@xxxxxx> wrote in message
> >> >> news:793DB2CA-4CAB-4527-9904-F4016655DC8A@xxxxxx
> >> >> > Hi
> >> >> >
> >> >> > On a full installation of W2k8 Enterprise I have Hyper-V (single
> >> >> > physical
> >> >> > server).
> >> >> > Integration services are installed on all VMs.
> >> >> >
> >> >> > All network-connections in the VMs have "limited or no connectivity"
> >> >> > with
> >> >> > an
> >> >> > IP of 169.x.x.x.
> >> >> > In case of normal connection, the VMs would obtain an IP from a DHCP
> >> >> > Server
> >> >> > in the range of 192.168.x.x
> >> >> > The physical network adapter is on a brand new intel-mainboard
> >> >> > (S5000XVN):
> >> >> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
> >> >> >
> >> >> > I chosed "external network type" in Virtual Network Manager and all
> >> >> > VMs
> >> >> > have
> >> >> > the VLAN ID 1.
> >> >> > What I discovered is, that the physical network adapter does not
> >> >> > show
> >> >> > the
> >> >> > point "VLAN ID" under Device-Manager/Network adapters/Intel
> >> >> > Nic/Properties/Advanced/Property.
> >> >> > Is this the reason, why my VMs have no connection?
> >> >> > Or what is the reason for this isolation of the VMs?
> >> >> >
> >> >> > Thanks for your help.
> >> >> >
> >> >> > Patrick
> >> >>
> >> >>
> >>
> >>

>

As long as you realize that all machines on the physical network will see
the DHCP service running on the SBS server.

"Patrick D." <PatrickD@xxxxxx> wrote in message
news:6850A0D5-D8F8-4F24-A211-01B1126A7657@xxxxxx

> Hi
>
> my final solution will only have one dhcp. The sbs 2008 virtualized. Can I
> still put the single physical server hyper-v solution on a external
> network
> in this case?
>
> Patrick
>
> "Bill Grant" wrote:
>

>> Of course. But in that case I would not put it on an external network.
>> I
>> would run the SBS domain on a private virtual network. You can then use
>> DHCP
>> on this network and not interfere with the DHCP service on the physical
>> LAN.
>>
>>
>> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> news:E9AE8922-C5D1-4D91-9851-F4191C2E3CFE@xxxxxx

>> > Hi Charlie
>> >
>> > well, then I should go away from this test-solution, with external
>> > dhcp.
>> > The
>> > final configuration will have a SBS 2008 (with dhcp) virtually on the
>> > same
>> > vlan like all other servers.
>> > Will this virtual SBS 2008 be able to give an IP to physical clients in
>> > the
>> > same domain?
>> >
>> > Patrick
>> >
>> > "Charlie Russel - MVP" wrote:
>> >
>> >> No, it means that with an external network in hyper-v, the _physical_
>> >> nic
>> >> doesn't have an IP address or run TCP/IP at all. If you set your
>> >> network
>> >> to
>> >> be on a vlan, it doesn't communicate with other computers that aren't
>> >> on
>> >> that vlan.
>> >>
>> >> Hyper-V networking is very different from anything we've worked with
>> >> before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by
>> >> configuring
>> >> without any vlan stuff, make sure you get everything working. If you
>> >> need
>> >> DHCP to the computers that are on the vlan, you'll want to make sure
>> >> you
>> >> have a DHCP server that will be on that same vlan.
>> >>
>> >> --
>> >> Charlie.
>> >> http://msmvps.com/blogs/xperts64
>> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >>
>> >> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> >> news:35480BD0-DFAC-4DA4-8E7D-98539FC16D6D@xxxxxx
>> >> > Hi
>> >> >
>> >> > does that mean, that with an "external network" an hyper-v solution
>> >> > on
>> >> > one
>> >> > physical server can not communicate with a physical dhcp, which is
>> >> > not
>> >> > on
>> >> > this physical machine?
>> >> >
>> >> > Patrick
>> >> >
>> >> > "Charlie Russel - MVP" wrote:
>> >> >
>> >> >> Do you have any DHCP server _on that VLAN_? If not, there's no way
>> >> >> they'll
>> >> >> get an IP address, is there?
>> >> >>
>> >> >> --
>> >> >> Charlie.
>> >> >> http://msmvps.com/blogs/xperts64
>> >> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >> >>
>> >> >> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> >> >> news:793DB2CA-4CAB-4527-9904-F4016655DC8A@xxxxxx
>> >> >> > Hi
>> >> >> >
>> >> >> > On a full installation of W2k8 Enterprise I have Hyper-V (single
>> >> >> > physical
>> >> >> > server).
>> >> >> > Integration services are installed on all VMs.
>> >> >> >
>> >> >> > All network-connections in the VMs have "limited or no
>> >> >> > connectivity"
>> >> >> > with
>> >> >> > an
>> >> >> > IP of 169.x.x.x.
>> >> >> > In case of normal connection, the VMs would obtain an IP from a
>> >> >> > DHCP
>> >> >> > Server
>> >> >> > in the range of 192.168.x.x
>> >> >> > The physical network adapter is on a brand new intel-mainboard
>> >> >> > (S5000XVN):
>> >> >> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
>> >> >> >
>> >> >> > I chosed "external network type" in Virtual Network Manager and
>> >> >> > all
>> >> >> > VMs
>> >> >> > have
>> >> >> > the VLAN ID 1.
>> >> >> > What I discovered is, that the physical network adapter does not
>> >> >> > show
>> >> >> > the
>> >> >> > point "VLAN ID" under Device-Manager/Network adapters/Intel
>> >> >> > Nic/Properties/Advanced/Property.
>> >> >> > Is this the reason, why my VMs have no connection?
>> >> >> > Or what is the reason for this isolation of the VMs?
>> >> >> >
>> >> >> > Thanks for your help.
>> >> >> >
>> >> >> > Patrick
>> >> >>
>> >> >>
>> >>
>> >>

>>

I think you'll want your host on a fixed IP, not relying on a DHCP server
running as a guest. Your host should have at least 2 NICs, one reserved for
itself; other(s) for the guest(s).

So, for example:

Edge device lan ip 192.168.0.1 (static)
Host nic one 192.168.0.2 (static)
Host nic two will "host" the hyper-v switch, it won't have an IP (as Charlie
explained), and will be an "external" network. You specify this NIC when you
create the network.
Your SBS guest will have a NIC, and will use the network above - fixed IP
192.168.0.3
SBS will provide DHCP for the 192.168.0.0 network.
Any other machines, physical, or virtual (if connected to the above
"external network") will be served by the SBS DHCP.

--
-----------------------------------------------
Les Connor [SBS MVP]

"Patrick D." <PatrickD@xxxxxx> wrote in message
news:6850A0D5-D8F8-4F24-A211-01B1126A7657@xxxxxx

> Hi
>
> my final solution will only have one dhcp. The sbs 2008 virtualized. Can I
> still put the single physical server hyper-v solution on a external
> network
> in this case?
>
> Patrick
>
> "Bill Grant" wrote:
>

>> Of course. But in that case I would not put it on an external network.
>> I
>> would run the SBS domain on a private virtual network. You can then use
>> DHCP
>> on this network and not interfere with the DHCP service on the physical
>> LAN.
>>
>>
>> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> news:E9AE8922-C5D1-4D91-9851-F4191C2E3CFE@xxxxxx

>> > Hi Charlie
>> >
>> > well, then I should go away from this test-solution, with external
>> > dhcp.
>> > The
>> > final configuration will have a SBS 2008 (with dhcp) virtually on the
>> > same
>> > vlan like all other servers.
>> > Will this virtual SBS 2008 be able to give an IP to physical clients in
>> > the
>> > same domain?
>> >
>> > Patrick
>> >
>> > "Charlie Russel - MVP" wrote:
>> >
>> >> No, it means that with an external network in hyper-v, the _physical_
>> >> nic
>> >> doesn't have an IP address or run TCP/IP at all. If you set your
>> >> network
>> >> to
>> >> be on a vlan, it doesn't communicate with other computers that aren't
>> >> on
>> >> that vlan.
>> >>
>> >> Hyper-V networking is very different from anything we've worked with
>> >> before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by
>> >> configuring
>> >> without any vlan stuff, make sure you get everything working. If you
>> >> need
>> >> DHCP to the computers that are on the vlan, you'll want to make sure
>> >> you
>> >> have a DHCP server that will be on that same vlan.
>> >>
>> >> --
>> >> Charlie.
>> >> http://msmvps.com/blogs/xperts64
>> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >>
>> >> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> >> news:35480BD0-DFAC-4DA4-8E7D-98539FC16D6D@xxxxxx
>> >> > Hi
>> >> >
>> >> > does that mean, that with an "external network" an hyper-v solution
>> >> > on
>> >> > one
>> >> > physical server can not communicate with a physical dhcp, which is
>> >> > not
>> >> > on
>> >> > this physical machine?
>> >> >
>> >> > Patrick
>> >> >
>> >> > "Charlie Russel - MVP" wrote:
>> >> >
>> >> >> Do you have any DHCP server _on that VLAN_? If not, there's no way
>> >> >> they'll
>> >> >> get an IP address, is there?
>> >> >>
>> >> >> --
>> >> >> Charlie.
>> >> >> http://msmvps.com/blogs/xperts64
>> >> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >> >>
>> >> >> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> >> >> news:793DB2CA-4CAB-4527-9904-F4016655DC8A@xxxxxx
>> >> >> > Hi
>> >> >> >
>> >> >> > On a full installation of W2k8 Enterprise I have Hyper-V (single
>> >> >> > physical
>> >> >> > server).
>> >> >> > Integration services are installed on all VMs.
>> >> >> >
>> >> >> > All network-connections in the VMs have "limited or no
>> >> >> > connectivity"
>> >> >> > with
>> >> >> > an
>> >> >> > IP of 169.x.x.x.
>> >> >> > In case of normal connection, the VMs would obtain an IP from a
>> >> >> > DHCP
>> >> >> > Server
>> >> >> > in the range of 192.168.x.x
>> >> >> > The physical network adapter is on a brand new intel-mainboard
>> >> >> > (S5000XVN):
>> >> >> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
>> >> >> >
>> >> >> > I chosed "external network type" in Virtual Network Manager and
>> >> >> > all
>> >> >> > VMs
>> >> >> > have
>> >> >> > the VLAN ID 1.
>> >> >> > What I discovered is, that the physical network adapter does not
>> >> >> > show
>> >> >> > the
>> >> >> > point "VLAN ID" under Device-Manager/Network adapters/Intel
>> >> >> > Nic/Properties/Advanced/Property.
>> >> >> > Is this the reason, why my VMs have no connection?
>> >> >> > Or what is the reason for this isolation of the VMs?
>> >> >> >
>> >> >> > Thanks for your help.
>> >> >> >
>> >> >> > Patrick
>> >> >>
>> >> >>
>> >>
>> >>

>>

The parent (host) really should not use DHCP if your only DHCP server is on
a VM. Far better to simply give it a fixed IP address.

--
Charlie.
http://msmvps.com/blogs/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel

"Patrick D." <PatrickD@xxxxxx> wrote in message
news:6850A0D5-D8F8-4F24-A211-01B1126A7657@xxxxxx

> Hi
>
> my final solution will only have one dhcp. The sbs 2008 virtualized. Can I
> still put the single physical server hyper-v solution on a external
> network
> in this case?
>
> Patrick
>
> "Bill Grant" wrote:
>

>> Of course. But in that case I would not put it on an external network.
>> I
>> would run the SBS domain on a private virtual network. You can then use
>> DHCP
>> on this network and not interfere with the DHCP service on the physical
>> LAN.
>>
>>
>> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> news:E9AE8922-C5D1-4D91-9851-F4191C2E3CFE@xxxxxx

>> > Hi Charlie
>> >
>> > well, then I should go away from this test-solution, with external
>> > dhcp.
>> > The
>> > final configuration will have a SBS 2008 (with dhcp) virtually on the
>> > same
>> > vlan like all other servers.
>> > Will this virtual SBS 2008 be able to give an IP to physical clients in
>> > the
>> > same domain?
>> >
>> > Patrick
>> >
>> > "Charlie Russel - MVP" wrote:
>> >
>> >> No, it means that with an external network in hyper-v, the _physical_
>> >> nic
>> >> doesn't have an IP address or run TCP/IP at all. If you set your
>> >> network
>> >> to
>> >> be on a vlan, it doesn't communicate with other computers that aren't
>> >> on
>> >> that vlan.
>> >>
>> >> Hyper-V networking is very different from anything we've worked with
>> >> before - it's NOT a bridge, unlike VS or VMWare. I'd _start_ by
>> >> configuring
>> >> without any vlan stuff, make sure you get everything working. If you
>> >> need
>> >> DHCP to the computers that are on the vlan, you'll want to make sure
>> >> you
>> >> have a DHCP server that will be on that same vlan.
>> >>
>> >> --
>> >> Charlie.
>> >> http://msmvps.com/blogs/xperts64
>> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >>
>> >> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> >> news:35480BD0-DFAC-4DA4-8E7D-98539FC16D6D@xxxxxx
>> >> > Hi
>> >> >
>> >> > does that mean, that with an "external network" an hyper-v solution
>> >> > on
>> >> > one
>> >> > physical server can not communicate with a physical dhcp, which is
>> >> > not
>> >> > on
>> >> > this physical machine?
>> >> >
>> >> > Patrick
>> >> >
>> >> > "Charlie Russel - MVP" wrote:
>> >> >
>> >> >> Do you have any DHCP server _on that VLAN_? If not, there's no way
>> >> >> they'll
>> >> >> get an IP address, is there?
>> >> >>
>> >> >> --
>> >> >> Charlie.
>> >> >> http://msmvps.com/blogs/xperts64
>> >> >> http://mvp.support.microsoft.com/profile/charlie.russel
>> >> >>
>> >> >> "Patrick D." <PatrickD@xxxxxx> wrote in message
>> >> >> news:793DB2CA-4CAB-4527-9904-F4016655DC8A@xxxxxx
>> >> >> > Hi
>> >> >> >
>> >> >> > On a full installation of W2k8 Enterprise I have Hyper-V (single
>> >> >> > physical
>> >> >> > server).
>> >> >> > Integration services are installed on all VMs.
>> >> >> >
>> >> >> > All network-connections in the VMs have "limited or no
>> >> >> > connectivity"
>> >> >> > with
>> >> >> > an
>> >> >> > IP of 169.x.x.x.
>> >> >> > In case of normal connection, the VMs would obtain an IP from a
>> >> >> > DHCP
>> >> >> > Server
>> >> >> > in the range of 192.168.x.x
>> >> >> > The physical network adapter is on a brand new intel-mainboard
>> >> >> > (S5000XVN):
>> >> >> > Intel Pro/1000 EB Network Connection with I/O Acceleration.
>> >> >> >
>> >> >> > I chosed "external network type" in Virtual Network Manager and
>> >> >> > all
>> >> >> > VMs
>> >> >> > have
>> >> >> > the VLAN ID 1.
>> >> >> > What I discovered is, that the physical network adapter does not
>> >> >> > show
>> >> >> > the
>> >> >> > point "VLAN ID" under Device-Manager/Network adapters/Intel
>> >> >> > Nic/Properties/Advanced/Property.
>> >> >> > Is this the reason, why my VMs have no connection?
>> >> >> > Or what is the reason for this isolation of the VMs?
>> >> >> >
>> >> >> > Thanks for your help.
>> >> >> >
>> >> >> > Patrick
>> >> >>
>> >> >>
>> >>
>> >>

>>