Hyper-V breaks DHCP - 1041

I've installed Hyper-V, and created a virtual network connection.
Everything is happy except DHCP - in that I can connect to the internet and
the internet can connect to me.

Looking at the log files, I have a 1041:
The DHCP service is not servicing any DHCPv4 clients because none of the
active network interfaces have statically configured IPv4 addresses, or
there are no active interfaces.

Opening up DHCP and looking under Add Remove Bindings - the list is empty
and I cannot add anything.

It seems that I cannot operate DHCP across a virtual connection that is
switched to a physical connection.

Help?

R

Where is the DHCP server? On the LAN? On the host? On a guest?

"Onetoomany" <someone@somewhere> wrote in message
news:(E-Mail Removed)...
> I've installed Hyper-V, and created a virtual network connection.
> Everything is happy except DHCP - in that I can connect to the internet
> and the internet can connect to me.
>
> Looking at the log files, I have a 1041:
> The DHCP service is not servicing any DHCPv4 clients because none of the
> active network interfaces have statically configured IPv4 addresses, or
> there are no active interfaces.
>
> Opening up DHCP and looking under Add Remove Bindings - the list is empty
> and I cannot add anything.
>
> It seems that I cannot operate DHCP across a virtual connection that is
> switched to a physical connection.
>
> Help?
>
> R

Should have explained my setup, which is a simple test network:
- Single 2008 server running core networking services (DNS, DHCP, AD) +
Hyper-V
- Single network card
I have a couple of DHCP clients sitting on the network. All works if I give
them a static IP... so DHCP seems to be the only problem.

R


"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> Where is the DHCP server? On the LAN? On the host? On a guest?
>
> "Onetoomany" <someone@somewhere> wrote in message
> news:(E-Mail Removed)...
>> I've installed Hyper-V, and created a virtual network connection.
>> Everything is happy except DHCP - in that I can connect to the internet
>> and the internet can connect to me.
>>
>> Looking at the log files, I have a 1041:
>> The DHCP service is not servicing any DHCPv4 clients because none of the
>> active network interfaces have statically configured IPv4 addresses, or
>> there are no active interfaces.
>>
>> Opening up DHCP and looking under Add Remove Bindings - the list is empty
>> and I cannot add anything.
>>
>> It seems that I cannot operate DHCP across a virtual connection that is
>> switched to a physical connection.
>>
>> Help?
>>
>> R
>

Installing Hyper-V makes major changes to the way the NIC in the host
machine works. Runnig DHCP on the host to service LAN machines wouldn't be a
great idea. See this article from Ben's blog.

http://blogs.msdn.com/virtual_pc_guy...h-hyper-v.aspx

"Onetoomany" <someone@somewhere> wrote in message
news:%(E-Mail Removed)...
> Should have explained my setup, which is a simple test network:
> - Single 2008 server running core networking services (DNS, DHCP, AD) +
> Hyper-V
> - Single network card
> I have a couple of DHCP clients sitting on the network. All works if I
> give them a static IP... so DHCP seems to be the only problem.
>
> R
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:(E-Mail Removed)...
>> Where is the DHCP server? On the LAN? On the host? On a guest?
>>
>> "Onetoomany" <someone@somewhere> wrote in message
>> news:(E-Mail Removed)...
>>> I've installed Hyper-V, and created a virtual network connection.
>>> Everything is happy except DHCP - in that I can connect to the internet
>>> and the internet can connect to me.
>>>
>>> Looking at the log files, I have a 1041:
>>> The DHCP service is not servicing any DHCPv4 clients because none of the
>>> active network interfaces have statically configured IPv4 addresses, or
>>> there are no active interfaces.
>>>
>>> Opening up DHCP and looking under Add Remove Bindings - the list is
>>> empty and I cannot add anything.
>>>
>>> It seems that I cannot operate DHCP across a virtual connection that is
>>> switched to a physical connection.
>>>
>>> Help?
>>>
>>> R
>>
>

On May 9, 2:45*am, "Onetoomany" <someone@somewhere> wrote:
> Should have explained my setup, which is a simple test network:
> - Single 2008 server running core networking services (DNS, DHCP, AD) +
> Hyper-V
> - Single network card
> I have a couple of DHCP clients sitting on the network. *All works if I give
> them a static IP... so DHCP seems to be the only problem.
>
> R
>
> "Bill Grant" <not.available@online> wrote in message
>
> news:(E-Mail Removed)...
>
>
>
> > * Where is the DHCP server? On the LAN? On the host? On a guest?
>
> > "Onetoomany" <someone@somewhere> wrote in message
> >news:(E-Mail Removed)...
> >> I've installed Hyper-V, and created a virtual network connection.
> >> Everything is happy except DHCP - in that I can connect to the internet
> >> and the internet can connect to me.
>
> >> Looking at the log files, I have a 1041:
> >> The DHCP service is not servicing any DHCPv4 clients because none of the
> >> active network interfaces have statically configured IPv4 addresses, or
> >> there are no active interfaces.
>
> >> Opening up DHCP and looking under Add Remove Bindings - the list is empty
> >> and I cannot add anything.
>
> >> It seems that I cannot operate DHCP across a virtual connection that is
> >> switched to a physical connection.
>
> >> Help?
>
> >> R- Hide quoted text -
>
> - Show quoted text -

This forum seems to have come up with a solution. This may be what is
affecting you.

http://forums.microsoft.com/TechNet/...2313&SiteID=17

Regards,
Matt

Here is the issue,

When you installed Hyper-V, you checked the check box where it listed
your NIC.

I would recommend using one NIC for HyperV and other one for your DHCP



Onetoomany;3721383 Wrote:
> I've installed Hyper-V, and created a virtual network connection.
> Everything is happy except DHCP - in that I can connect to the internet
> and
> the internet can connect to me.
>
> Looking at the log files, I have a 1041:
> The DHCP service is not servicing any DHCPv4 clients because none of
> the
> active network interfaces have statically configured IPv4 addresses,
> or
> there are no active interfaces.
>
> Opening up DHCP and looking under Add Remove Bindings - the list is
> empty
> and I cannot add anything.
>
> It seems that I cannot operate DHCP across a virtual connection that
> is
> switched to a physical connection.
>
> Help?
>
> R


--
dennyd
------------------------------------------------------------------------
dennyd's Profile: http://forums.techarena.in/member.php?userid=50495
View this thread: http://forums.techarena.in/showthread.php?t=964480

http://forums.techarena.in

Short Answer:
Buy another NIC and dedicate it to your Hyper-V tasks.
Long Answer:
Install a second physical NIC on your Hyper-V server and patch it into your network.
Open the Virtual Network Manager in the Hyper-V console and remove all virtual networks
Configure your secondary NIC with an available IP from you LAN and a subnet mask. Leave the gateway, DNS and WINS empty.
Open the Virtual Network Manager in the Hyper-V console and create a virtual network using the secondary NIC.
Open Add/Remove Bindings on the DHCP server and remove the checks from all bindings except for your NIC. You may get an ambiguous error about an incorrect parameter which you can ignore.
Restart the DHCP server and open Add/Remove Bindings to verify that the changes you made were saved.
If all went well you should now be able to get DHCP leases from the Hyper-V server’s server primary NIC and use the secondary NIC for Virtual Machine access.
*If you use the Windows firewall, disable it for this process and re-enable it when DHCP works with the Virtual NIC.
This worked for me and I hope it helps to get things working for you. - Jaxplanet

Thank you for the tip.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"Jaxplanet" wrote in message news:(E-Mail Removed)...
> Short Answer:
> Buy another NIC and dedicate it to your Hyper-V tasks.
> Long Answer:
> Install a second physical NIC on your Hyper-V server and patch it into
> your network.
> Open the Virtual Network Manager in the Hyper-V console and remove all
> virtual networks
> Configure your secondary NIC with an available IP from you LAN and a
> subnet mask. Leave the gateway, DNS and WINS empty.
> Open the Virtual Network Manager in the Hyper-V console and create a
> virtual network using the secondary NIC.
> Open Add/Remove Bindings on the DHCP server and remove the checks from all
> bindings except for your NIC. You may get an ambiguous error about an
> incorrect parameter which you can ignore.
> Restart the DHCP server and open Add/Remove Bindings to verify that the
> changes you made were saved.
> If all went well you should now be able to get DHCP leases from the
> Hyper-V server's server primary NIC and use the secondary NIC for Virtual
> Machine access.
> *If you use the Windows firewall, disable it for this process and
> re-enable it when DHCP works with the Virtual NIC.
> This worked for me and I hope it helps to get things working for you. -
> Jaxplanet
>