Sign in
Microsoft.com
 
Windows Client TechCenter
 
 
 
Windows Client TechCenter > Windows 7 Forums > Windows 7 Virtualization > In XP Mode, am often getting "A duplicate name exists on the network" system error.
Ask a questionAsk a question
Search Forums:
 

AnswerIn XP Mode, am often getting "A duplicate name exists on the network" system error.

  • Friday, May 22, 2009 7:29 PMCraig Maudlin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I got a "Windows - System" Error dialog saying "A duplicate name exists on the network" the first time XP mode launched. Ever since, it *almost* always occurs when the virtual machine starts up (occasionally, it does not). This is on a 32-bit Windows 7 RC installation.

    Will send more info, if that might be useful.
     

Answers

  • Tuesday, May 26, 2009 2:53 PMShweta Bansal [MSFT] Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hi Craig,

    We are tracking this issue but we do not have enough data for this. Let me know if it will be poosible for you to set up a network capture for the VM when you get the popup for duplicate name.  In order to obtain the capture do the following:

    1.       Install Netmon inside the VM.  You can get it from http://www.microsoft.com/Downloads/details.aspx?FamilyID=f4db40af-1e08-4a21-a26b-ec2f4dc4190d&displaylang=en.

    2.       Hibernate the VM.

    3.       Connect the VM NIC to “not connected” from VM network settings.

    4.       Start the VM.

    5.       Start netmon and create a new capture. Start the capture on the VM NIC (Intel 1140 Based PCI Fast Ethernet Adapter)

    6.       From VM Network Settings (while the capture in the VM is running), connect the VM to NAT.

    7.       Once the popup comes inside the VM, Stop the capture and save to the disk.

     

    Please send the capture to wcvdata@microsoft.com

     

All Replies

  • Friday, May 22, 2009 8:09 PMRashmi U RMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Hi,

    This happens if there is another machine with the same computername on the network. Change the virtual machine's computer name, and see if this error occurs again on restart.

    Thanks, Rashmi U.R
     
  • Friday, May 22, 2009 8:33 PMCraig Maudlin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    My host machine is not on a network. I'm using a modem card and DUN to access the internet.

    I went to System in Control Panel and when I attempt to change the Computer name I get: "The following error occurred validating the name "VXP1".

    "You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again."

    I've tried three times with what I think are unique names and got this error each time.

     
  • Friday, May 22, 2009 8:46 PMRashmi U RMSFTUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Is your vm connected through NAT?

    Thanks, Rashmi U.R
     
  • Friday, May 22, 2009 8:47 PMCraig Maudlin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    Yes.
     
  • Saturday, May 23, 2009 10:25 PMCraig Maudlin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    I was able to change the computer name of the virtual machine after booting with the number of network adapters set to zero. Then I shut down, set the number of adapters back to 1, selected NAT, booted up and got the "Duplicate Name" error message again.

    I should also note that the first thing I did after installing this Virtual PC beta was launch an existing VM that had originally been created by Virtual PC 2007 when this host machine was running Vista.

    That VM (named "vm2") was originally XP Pro and was brought up to SP3 level via Windows Update. It was later run (and shut down) by Virtual PC 2007 when this host machine was running Windows 7 build 7000.

    Then Windows 7 build 7100 was installed on this host machine, the Virtual PC beta was installed and vm2 was run as a test. This test appeared to work fine. In particular there was no "Duplicate Name" error message.

    After that first boot of vm2, I installed the XP Mode beta. It was when this VM first booted that I got the initial "Duplicate Name" error message.

    Interestingly, I just ran vm2 again and it now gets a "Duplicate Name" error and won't allow me to change the computer name.

    Perhaps vm2's twisted linage is the source of the problem.

     
  • Tuesday, May 26, 2009 2:53 PMShweta Bansal [MSFT] Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    Sign In to Vote
    0
    Sign In to Vote
    Hi Craig,

    We are tracking this issue but we do not have enough data for this. Let me know if it will be poosible for you to set up a network capture for the VM when you get the popup for duplicate name.  In order to obtain the capture do the following:

    1.       Install Netmon inside the VM.  You can get it from http://www.microsoft.com/Downloads/details.aspx?FamilyID=f4db40af-1e08-4a21-a26b-ec2f4dc4190d&displaylang=en.

    2.       Hibernate the VM.

    3.       Connect the VM NIC to “not connected” from VM network settings.

    4.       Start the VM.

    5.       Start netmon and create a new capture. Start the capture on the VM NIC (Intel 1140 Based PCI Fast Ethernet Adapter)

    6.       From VM Network Settings (while the capture in the VM is running), connect the VM to NAT.

    7.       Once the popup comes inside the VM, Stop the capture and save to the disk.

     

    Please send the capture to wcvdata@microsoft.com

     
  • Wednesday, May 27, 2009 3:03 PMCraig Maudlin Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    ok. capture sent. Let me know if you need more info.
     
  • Thursday, May 28, 2009 7:14 AMShweta Bansal [MSFT] Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Thank you Craig and others who sent the capture to get this to closure. It was really helpful.

    Regards,
    Shweta

     
  • Tuesday, August 11, 2009 10:41 PMRenanWOI Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I'm getting the same error. And I'm not able to make a network between the virtual machine and host. Is your network fine?
     
  • Friday, August 28, 2009 1:53 PMMFerdinand Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    I'm seeing the same issue trying to access my XP shares using \\localhost.  Is this related, and do you have more info on a fix or corrective action?  It is specific to several XP virtual machines on our network.  The only significant element I can identify is that our DHCP is handled by our router appliances, not a dhcp server.  
     
  • Tuesday, November 03, 2009 3:01 AMAngel_wan Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote
    i supoose you may set the same name between computer name and register name in your computer, so you would better to check it out,  if so, change it, then can fix it. i just try it right now.
    hopefully can help for you also