Mark Minasi's Tech Forum
Register Calendar Latest Topics Chat
 
 
 


Reply
  Author   Comment  
pmarsh

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 59
Reply with quote  #1 
I can't remember does the parents physical NIC have to be assigned a static IP on the same subnet as the child machine or can you just leave the parent set as dynamic even tough it never gets dhcp?

 
0
Wes

Senior Member
Registered:
Posts: 205
Reply with quote  #2 
The two aren't related...  Can you tell us a little bit more about the configuration?  Sounds like you might only have one nic in this system?  You'd certainly want your host to have an ip for management, regardless of whether it's statically assigned or obtained via dhcp...  If you have more than one nic and one (or more) have been set up as *dedicated* hyper-v switch(es), then you wouldn't (can't actually) assign an ip of any sort...
0
pmarsh

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 59
Reply with quote  #3 
Host has 4 physical NIC, it hosts a few things.  Not the easiest thing to explain so here goes.

Main NIC Static 192.168.0.0
DMZ Static 192.168.1.0
Old subnet Dynamic from 192.168.0.0
>> The NIC in question is set for DHCP and is not receiving anything because there is no DHCP server on this network so it's got a default MS IP 169. address.

Virtual Switch Manager is all configured and things are happy happy.

The question is regarding ">>The NIC in question".  This VM is a multi-homed machine.

NIC-1 is DHCP from 192.168.0.0
NIC-2 is static to an external IP, the Ethernet is plugged directly into >>The NIC in question port.

Here is the question.  On the VM side NIC-2 has all it's static info and can successfully communicate on that network but when you look at the same NIC on the host again it's set for DHCP.  This has been working but when I look at it I question it.

Maybe I've over thinking this but shouldn't it be set and configured for static or maybe it doesn't matter as long as the virtual NIC's are configured correctly.

Geezer I hope that makes sense
     




0
Wes

Senior Member
Registered:
Posts: 205
Reply with quote  #4 
Sorry, not really clear yet :-)
What are the roles of the 4 nics?

Is one of them dedicated to being the host's management nic?  I assume that's what you mean by "main nic" - if so, having it set for dhcp on a network with no dhcp server must make it difficult to connect to and manage it?

Next, it sounds like the "nic in question" is only intended for VM traffic.  Is that the case, or is it also getting an ip assigned on the host (and maybe THIS is how you're managing the server?)?

On your hyper-v switch properties, if you have the box checked for "allow management OS to use this adapter" (don't quote me on the exact wording) then the physical nic connection will feed both the host OS and any VMs connected to that vswitch.  If you uncheck that box, the nic won't be accessible by the host at all (ip settings won't be accessible as ipv4/ipv6 will be unbound from the adapter).

What of the other two nics?  A little more background about what subnet does what (if you have more than one) might help...
0
wobble_wobble

Avatar / Picture

Associate Troublemaker Apprentice
Registered:
Posts: 803
Reply with quote  #5 

The only NIC's than need an IP address are the ones you address traffic to or from the host on.
So the management NIC, the IP address you RDP to, monitor with tools, push/ pull backups from should have an IP address, (Static/ DHCP reservation...)
This/ these NIC/ NIC's should not be used for guest traffic.

The other NIC's can be blank and get APIPA address or you can assign them an IP if you so wish. 1.1.1.1 to 1.1.1.3 could be the addresses! (or any other IP you wish)
Remember that the guests use these NICs to get to the outside world, the the Host NIC has no relevance to the traffic. (hence using a routable IP address means the host can't talk out to a C&C Server, but Wireshark/ Netmon will show some real weird traffic sometimes!)

So you have 4 NIC's on the host:
NIC 1 - Main NIC Static 192.168.0.0   
NIC 2 - DMZ Static 192.168.1.0
NIC 3 - Old subnet Dynamic from 192.168.0.0
NIC 4 - The NIC in question is set for DHCP (so not getting an IP as expected) 

Is this right?

I will say I hope there is something protecting NIC 4 - a firewall with some ports needed forwarded/ and that the the VM is a firewall [heavily locked down VM] and patched!


__________________
Have you tried turning it off and walking away? The next person can fix it!

New to the forum? Read this
0
Wes

Senior Member
Registered:
Posts: 205
Reply with quote  #6 
Paul and I connected via SfB and sorted it out - unchecking the box to share the vswitches with the management OS on all the virtual switches cleaned it up.
0
pmarsh

Avatar / Picture

New Friend (or an Old Friend who Built a New Account)
Registered:
Posts: 59
Reply with quote  #7 
Can't thank Wes enough.  He schooled me and I'm very appreciative.


Thank You Wes.  You rock! 
0
Wes

Senior Member
Registered:
Posts: 205
Reply with quote  #8 
Not at all!  Server was in good shape - just one little check box.
0
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.