How to avoid multiple VPCs copies in same network seing each other

Discussion in 'Virtual PC' started by Miguel, May 29, 2006.

  1. Miguel

    Miguel Guest

    I have to run some training and tests on products that run on top of
    Win2003/Exchange 2003. I want to have several copies of the same VPC running
    on separate host PCS that are connected in the same network and avoid
    conflicts of each one seeing each other. Let me explain in more detail.

    To avoid spending time the best way is to give each atendee a copy of my VPC
    running as a domain controller with Exchange already installed on it and do
    the installation of the add-on software and the rest of the training based on
    that image. I already installed Exchange and other software on the Win 2003
    DC and many of them are dependant on Domain or computer name, so I don't want
    to rename them. However all trainees host PCs will be in the same room,
    sharing the same physical network, and automatically getting IP
    addresses(since they and one of the applications require access to the
    internet).
    Is there are recommended configuration so all the copies of the same VPC
    domain controller can see the internet but they cannot see each other to
    avoid same computer name or domain controller conflicts?

    Thanks MFR.
     
    Miguel, May 29, 2006
    #1
    1. Advertisements

  2. Miguel

    Ken Schaefer Guest

    Use "Shared Networking"

    The VPCs will be able to see the Internet (using the host computer's IP
    address + NAT). The Host will not be able to see the VPC however.

    If you have multiple VPCs, add a second adapter (using "Local Only"
    networking) to allow the VPCs to communicate with each other

    Cheers
    Ken
     
    Ken Schaefer, May 29, 2006
    #2
    1. Advertisements

  3. Miguel

    Paul Adare Guest

    microsoft.public.virtualpc news group, =?Utf-8?B?TWlndWVs?=
    You also need to keep in mind the licensing requirements here. You'll
    need to purchase a VPC license, a Windows Server 2003 licenses, an
    Exchange licenses, and a license for the "add-on software" for each
    student.

    --
    Paul Adare - MVP Virtual Machines
    It all began with Adam. He was the first man to tell a joke--or a lie.
    How lucky Adam was. He knew when he said a good thing, nobody had said
    it before. Adam was not alone in the Garden of Eden, however, and does
    not deserve all the credit; much is due to Eve, the first woman, and
    Satan, the first consultant." - Mark Twain
     
    Paul Adare, May 29, 2006
    #3
  4. Miguel

    Miguel Guest

    Paul, Ken,
    Maybe I did not express myself right. All the attendees are Sales engineers
    with full active MSDN subscrition. The have their own VPC 2004 and I am
    giving them a prebuild image for their own training and test purposes.
    The real problem I have is that during the session I need them to access the
    internet from the same office (connected to the same physical network) and
    all of them will be starting an identical copy of my image (same domain name
    and computer name) form their host XP laptop that takes the IP address from
    our DHCP. If I enable NAT (shared network) and all of them are in the same IP
    range (192.168.131.x), each VPC will see the other ones, right? If that is
    the case, I will have a conflict because the same domain name and computer
    name will be in the same network multiple times. So bottom line what I want
    is for them to be able to boot their identical VPCs simultaneously, access
    the internet through our company and avoid seeing each other's VPC. One idea
    could be to do some subnet segmentation so they don't see each other but I am
    not sure if the "DHCP" built in the VPC allows me to assign a range of IP
    addresses and IP mask to be assigned differentially to each VPC (e.g.
    atendee1 will have 192.168.131.x, attendee2: 192.168.132.x and so on with a
    netmask of 255.255.255.0. )

    Thanks,

    Miguel.
     
    Miguel, May 29, 2006
    #4
  5. Miguel

    Miguel Guest

    Ken,
    Maybe I did not express myself right. What I don't want is that the VPC in
    host1 can see the VPC in host2 even if they have an identical image and the
    host XP systems are connected to the same physical network. I believe that
    the solution you gave wull allow the VPC Windows server on host 1 detect that
    the VPC Windows server that is running on host 2 has the same computer name
    and domain. Am I wrong?

    The real problem I have is that during the session I need them to access the
    internet from the same office (connected to the same physical network) and
    all of them will be starting an identical copy of my image (same domain name
    and computer name) form their host XP laptop that takes the IP address from
    our DHCP. If I enable NAT (shared network) and all of them are in the same IP
    range (192.168.131.x), each VPC will see the other ones, right? If that is
    the case, I will have a conflict because the same domain name and computer
    name will be in the same network multiple times. So bottom line what I want
    is for them to be able to boot their identical VPCs simultaneously, access
    the internet through our company and avoid seeing each other's VPC. One idea
    could be to do some subnet segmentation so they don't see each other but I am
    not sure if the "DHCP" built in the VPC allows me to assign a range of IP
    addresses and IP mask to be assigned differentially to each VPC (e.g.
    atendee1 will have 192.168.131.x, attendee2: 192.168.132.x and so on with a
    netmask of 255.255.255.0. )

    Thanks,

    Miguel.
     
    Miguel, May 29, 2006
    #5
  6. Perhaps you can prepare a sysprepped image for which each sales engineer
    will enter his own product key, etc. This should also ensure that you get
    unique MAC identifiers for the network. However, that only addresses the
    OS. Paul's point on the rest of the software is still applicable.
     
    Colin Barnhorst, May 30, 2006
    #6
  7. Miguel

    Ken Schaefer Guest

    You are wrong.

    Your networking options are described in the online help for Virtual PC. You
    can read (in more detail) there where I have posted (instead of me writing
    it all out for you). But basically "shared networking" works like NAT. The
    only visible IP address/host is your Windows XP host machine.
    No. Think about the 'internet' at large. A lot of people have NAT devices
    connected to the internet. Behind the NAT device is a private network. Each
    privte network probably uses 192.168.x.x

    If you are using, say, 192.168.0.x can you see everyone else's private
    network? No. You can only see their public IP addresses that are on the
    public interface of the remote NAT device.

    Cheers
    Ken






    If that is
     
    Ken Schaefer, May 30, 2006
    #7
  8. Miguel

    Miguel Guest

    Thanks a lot Ken. I was confused regarding the functionality of the VPC
    shared network. This is great, at least for my purposes of doing the training
    based on the same VPC image and saving lots of time and headaches installing
    base software during the training. I already tried it in my office running 2
    copies of the same VPC image on different physical hosts and it behaves
    exactly as you described.

    Miguel.
     
    Miguel, May 30, 2006
    #8
  9. Miguel

    Ken Schaefer Guest

    No problems. The networking options can be a bit confusing when you read
    them the first time. Glad you got it fixed.

    Cheers
    Ken
     
    Ken Schaefer, Jun 1, 2006
    #9
    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.