Problem with VMWare server: The IP was assigned to another card

Discussion in 'Virtualization' started by Dell mountainman, Feb 21, 2012.

  1. Dell mountainman

    Dell mountainman New Member

    9
    0
    13
    We are recently converted a Hyper V server to VMware server. We used the latest converter and imported it into vSphere Client which we have running on a single server with the free license at the moment.server virtualization

    When we booted the server, it's is on a vlan so we setup a new virtual switch and assigned a network card to it on vlan 20. Turned the network card on for the machine and can see it’s connected in the networking part of the vSphere client.

    We consoled to the server and found the network card was set to DHCP so I put the static IP back on. At which point the server said that the IP was assigned to another card the Hyper-V management card but that this was removed and did we want to move the IP address to the new card, Then we clicked yes! Only problem is we can't ping the server and the server can't ping anything else not even its default gateway. Has anyone got any ideas why this would happen its the first time we have converted a Hyper-V machine and we are stuck:cry:
     
  2. Adam Banner

    Adam Banner Poster Galore

     
  3. dales

    dales Gigabyte Poster

    1,960
    40
    97
    Hi,

    You'll want to follow this MS KB to show the hidden nics Device Manager Does Not Display Devices Not Currently Present in Windows 2000 once you can see them you can remove the hidden nics that have the same IP config info. Its a common problem and its best practice to do this on every p2v to remove old physical server hardware devices as they do occasionally cause conflicts.

    What sort of vnic have you installed in the vm is it an e1000, vmxnet2,3 or flexible if its vmxnet have you got the vmware tools installed. If you have then check that the vnic is connected to the vswitch and the vswitch is connected to a physical nic. You can check the vnic by right clicking the vm edit settings, highlighting the vnic and ensuring that connect at power on and connected checkboxes are checked.

    If all that is ok it might be worth removing the vnic and adding an e1000 as windows will have a driver for that so it might help diagnose the issue.
     
    Last edited: Feb 21, 2012
    Certifications: vExpert 2014, CCE-AD, CCP-AD, CCEE, CCAA XenApp, CCA Netscaler, XenApp 6.5, XenDesktop 5 & Xenserver 6,VCP3+5,VTSP,MCSA MCDST MCP A+ ITIL F
    WIP: Nothing
  4. zebulebu

    zebulebu Terabyte Poster

    3,748
    330
    187
    Dales is right - if you don't clear up stale hardware after a p2v you'll always have problems (especially with old graphics card drivers/management suites, power management software (APC powerchute etc), things like OpenManage/HP SIM and - as you're currently finding - old nics)

    It can be a real PITA doing this individually - try using this cracking little tool - Ghostbuster to clear it all out quickly in one fell swoop
     
    Certifications: A few
    WIP: None - f*** 'em
    dales likes this.
  5. dales

    dales Gigabyte Poster

    1,960
    40
    97
    Ooo hadn't spotted this tool yet nice find zeb cheers!
     
    Certifications: vExpert 2014, CCE-AD, CCP-AD, CCEE, CCAA XenApp, CCA Netscaler, XenApp 6.5, XenDesktop 5 & Xenserver 6,VCP3+5,VTSP,MCSA MCDST MCP A+ ITIL F
    WIP: Nothing

Share This Page

Loading...