Duplicate name exists on network

Discussion in 'Virtual PC' started by peter, Nov 21, 2003.

  1. peter

    peter Guest

    I created a MSVPC2004 2003 Server in a workgroup
    configuration and then distributed the .vhd to multiple
    physical host machines. Now I'm getting 'duplicate' name
    exists on the network errors.

    They do all have the same computer name but I thought that
    I could get around this by changing the workgroup name to
    be unique, making sure the MAC in the vmc file was unique
    and by setting up the network adapter for each instance as
    Shared Networking (NAT). Is there any other way around
    this to isolate each of the machines that are running the
    exact same image on the network?

    I would like to avoid changing the machine name on each
    instance as I have SQL, IIS and other services that are
    tied to that specific machine name. I also need access to
    network resource (internet, etc) so I didn't think the
    local loopback adapter would work.

    Any suggestions.
    peter, Nov 21, 2003
    1. Advertisements

  2. Hi,

    I did the same thing - installed Windows Server 2003 then installed
    everything I wanted (shared) on both machines, shut it down and copied the
    file. I expected it to error out (the machines are joined to a domain) so
    when I booted the second I logged on locally, changed the computer name and
    re-joined it.

    Of course, you're not running a domain, as per your post, so I suggest you
    look into image-preparation tools, such as Sysprep
    nol/windowsserver2003/proddocs/deployguide/acicd_sys_overview.asp), so that
    right before you copy the machine, you can have it set up to use different
    names, etc

    --Jonathan Maltz [Microsoft MVP - Windows Server]
    http://www.visualwin.com - A Windows Server 2003 visual, step-by-step
    tutorial site :)
    Only reply by newsgroup. Any emails I have not authorized are deleted
    before I see them.
    Jonathan Maltz [MS-MVP], Nov 21, 2003
    1. Advertisements

  3. peter

    SJ Guest

    taht was a known issue with Shared networking under 5.2. Not sure if
    it still exists under VPC2004, but it sure sounds like the same thing.
    SJ, Nov 21, 2003
  4. No, this is probably not an issue with shared networking. We removed the old
    SMBios redirector code that caused this problem in VPC 5.2.

    - Eric
    Eric Traut [MSFT], Nov 22, 2003
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.