Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have installed Hyper V 3 Core. I created a windows server 2012 vm with a static IP address connected to an external vswitch which was binded to a separate physical NIC than what the management network is on.

When looking at the NICs with ipconfig /all on the core install it only shows the management network adapter now that I have an external vswitch bound to the other physical NIC.

However, the VM cannot get out. When I do a ping or trace route Everything seems to stop at a 169. address which I assume is the physical NIC the external vswitch is bound to. Any ideas on where I went wrong in my setup?

EDIT: I can't ping the gateway. It says no response from 169... It is like it is hitting the physical NIC for some reason. I compared the settings on this VM to one of my other physical machines and they are identical, aside from the IP address of course. Same Subnet the physical machine can communicate fine but the virtual on the same network can't.

Results from Route Print

    Interface List
 12...00 15 5d 64 f7 00 ......Microsoft Hyper-V Network Adapter
  1...........................Software Loopback Interface 1
 13...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0  136.142.100.225                c    261
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      169.254.0.0      255.255.0.0         On-link                 c    261
  169.254.233.254  255.255.255.255         On-link                 c    261
  169.254.255.255  255.255.255.255         On-link                 c    261
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link                 c    261
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link                 c    261
===========================================================================
Persistent Routes:
  Network Address          Netmask  Gateway Address  Metric
          0.0.0.0          0.0.0.0  136.142.100.225  Default
===========================================================================
share|improve this question
3  
We don't deal with unreleased code on serverfault. –  Chopper3 Jul 26 '12 at 13:36
1  
This is very close to RTM, and it's a relevant question to Hyper-V basic networking configuration. –  SpacemanSpiff Jul 26 '12 at 13:42
    
so within the guest vm can you ping its (the vm's) gateway address? –  tony roth Jul 26 '12 at 13:43
    
what is the output of route print? –  Goyuix Jul 26 '12 at 14:49
    
did you share the vm network with the host network? If so don't. –  tony roth Jul 26 '12 at 20:01
show 2 more comments

2 Answers 2

up vote 2 down vote accepted

After all this it turns out it was a duplicate network address. Previous versions of windows warned you this just accepts it and quietly assigns a 169 address as the preferred address even though it keeps your entry in the tcp/ip properties. I finally noticed a '(duplicate)' next to the static IP I assigned in IPconfig /all. Ahhhhhhh hours wasted. Thanks all for the suggestions

share|improve this answer
add comment

A 169.254.x.x address is an Automatic Private IP Address which Windows configures for itself when DHCP times out.

When you configure an External network in Hyper-V, there is no NAT or routing involved - the virtual guests appear to your network as devices in their own right. If you don't have a DHCP server on your network you will need to configure it with a valid static IP address for your subnet.

EDIT: as Tony Roth pointed out to me, I didn't read your question fully and you already have a static IP configured on the guest. Is the network definitely configured as an External and not a Private?

share|improve this answer
    
well he does mention this "2012 vm with a static IP address" –  tony roth Jul 26 '12 at 13:42
    
Very good point, I somehow completely missed that. –  Chris McKeown Jul 26 '12 at 13:43
    
If he's getting error related to 169.254/16 address, he doesn't have a static IP configured correctly. –  Chris S Jul 26 '12 at 13:45
    
Correct. I assigned the VM an IP on our subnet. It seems like the physical NIC is stuck in some kind of state where it doesn't show on the core install any longer but is not in a "passthrough mode" either. –  Xaxum Jul 26 '12 at 13:46
    
I have the IP Configured correctly on the VM. I have quadruple checked the settings. Not sure where to go from here. –  Xaxum Jul 26 '12 at 13:48
show 6 more comments

Your Answer

 
discard

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.