vendredi 22 mai 2009 19:29I 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.
Toutes les réponses
vendredi 22 mai 2009 20:09
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
vendredi 22 mai 2009 20:33
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.
vendredi 22 mai 2009 20:46
Is your vm connected through NAT?
Thanks, Rashmi U.R
vendredi 22 mai 2009 20:47Yes.
samedi 23 mai 2009 22:25
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.
mardi 26 mai 2009 14:53Hi 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 email@example.com
- Marqué comme réponse Nitin.GargModerator lundi 1 juin 2009 19:03
mercredi 27 mai 2009 15:03ok. capture sent. Let me know if you need more info.
jeudi 28 mai 2009 07:14
Thank you Craig and others who sent the capture to get this to closure. It was really helpful.
mardi 11 août 2009 22:41I'm getting the same error. And I'm not able to make a network between the virtual machine and host. Is your network fine?
vendredi 28 août 2009 13:53I'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.
mardi 3 novembre 2009 03:01i 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
vendredi 29 janvier 2010 15:07Did this ever get resolved?I'm running into an issue where I have an XP host and VPC VM (Windows Server 2003) on a model machine. The VM on the model PC was set to Shared Networking (NAT). I created a Ghost image of the XP host, deployed to a classroom, renamed all XP hosts using Ghostwalker, and started the PCs. XP hosts are fine. However, the VPC VM's are reporting "Duplicate name" error, even though the VM's network settings are set to Shared Networking (NAT). We have plenty of other VMware-based VM's where NAT is set and do not have this duplicate name error issue.Could this have something to do with "Hardware-Enabled Virtualization" in the system's BIOS? Is there some other workaround/patch/VMC file modification/etc. that needs to be implemented?Any thoughts/suggestions would be great at this point.Kind Regards,Doug
vendredi 29 janvier 2010 18:08It's not related to Hardware enabled virtualization. This "bug" has been around in VPC for a long time, its related to VPC's NAT. It was fixed in previous versions, but since the new VPC is Virtual Server based it could have been reintroduced.
vendredi 29 janvier 2010 19:50Thanks for the response. I would rename the VPCs, except they're running SharePoint and SQL. I'm afraid that renaming the VPC computer name field will break some of those services.I would move this VM to a VMware environment, however the instructor insists on having the 'undo disk' feature of VPC.
vendredi 29 janvier 2010 21:45Renaming won't help...it doesn't really matter what the name is, the issue is with NAT. As long as all your names aren't actually the same, switching to the host NIC should resolve this issue.
mardi 7 février 2012 11:55
I am just now having a similar problem, and in my case the problem seems to be with the Group Name of Windows, even if the message says Duplicate Name.
I made some tests with my computer (that were all in the group called SPME, here). When I change the Group Name to anything (thus others here changed to "WORKGROUP"), the duplicate name message disappear. I changed one of the machines name, with the same SPME group, and the message appear again, even if you invent a whole new name for it.
So, you could try to change the Group Name and see what happens, maybe Microsoft people can help us more about the problem them.
Nobuyuki Yoshida (MisterVSE)
mardi 7 février 2012 18:29Hello, I just found what the problem were here, with my network. We have now a Linux server with shared file that can be viewed in our Windows machines, and the Shared name for this file is the same as the Group Name in our Windows (like, just "SPME"), and this seems to be causing a problem, because of the name. I tought, perhaps, if there is a machine with the same name as the Group names of other machines, can it happen with Windows Only network ?
jeudi 19 avril 2012 20:55
Just to let you know that I encountered exactly the same issue on Windows Server 2008 SP2 running in Oracle VirtualBox 4.1.12.
I've set up the client with 2 NIC's - one for NAT, one for local traffic only.
Renaming the host, workgroup, modifying the DNS settings, the order of the NIC's or any other steps didn't fix the issue.
I.e. until I modified the NATted adapter to use Bridging instead; this resolved my Issue.
I saw the same on Virtual PC, the 2007 version, I think.