XPClient/Server2003 setup using Virtual PC2007

Discussion in 'Virtual PC' started by Lee Wild, Mar 8, 2010.

  1. Lee Wild

    Lee Wild Guest

    Hello all,

    I currently have two virtual machines installed, one for 2003 and the other
    for XPpro. I attempting to setup a small Domain environment to aid me with
    the 70-290 exam but I seem to have hit a brick wall. The server is set up
    with multiple roles, DHCP,DNS and as a Domain Controller. Within the DHCP
    server settings it is possible to bind this to the virtual NIC to use this
    for it's IP address. So lets just say that I configure my virtual NIC with an
    IP address of 192.168.0.1, the DHCP would be assigned this too. In the TCP/IP
    LAN settings for the adapter, what IP address would I use as a default
    gateway? Also, would I be correct in saying that the 2003 VM running multiple
    roles, is it possible to use just the one IP address for DHCP,DNS and the DC,
    and if the answer is yes then for the virtual NIC TCP/IP settings would I
    also use 192.168.0.1 on the server2003 settings.
    In addition to the above, both virtual NIC's for the XP client and 2003 VM's
    are configured as 'Local only'. My XP client is configured to acquire it's IP
    address automatically, although up to now it has not recieved any lease.


    Thanks in advance.
     
    Lee Wild, Mar 8, 2010
    #1
    1. Advertisements

  2. Lee Wild

    Bill Grant Guest


    Put both of the virtual machines in Local Only. Manually configure the DC
    with its own IP address in its own IP subnet. (I would use a less popular
    subnet like 192.168.66 rather than 192.168.0). It does not need a default
    gateway setting as it cannot communicate with any other network.

    You can configure DHCP on the server. Configure the scope to to issue IP
    addresses in the subnet you chose for the DC. The clients don't need a
    gateway either. Configure your scope to issue the DC's IP address for DNS.
    All AD clients need to use the local DNS server.

    If you feel that you need Internet access, create another vm and install
    a server OS. Use this server (not your DC) as a NAT router between your AD
    network and the physical network. You would then use this router as the
    default gateway for the domain network. You would also configure your local
    DNS to forward to a public DNS service (like your ISP's DNS or 4.2.2.2) to
    resolve foreign URls for your domain machines. By default your local DNS
    will only resolve local machines and AD resources.
     
    Bill Grant, Mar 8, 2010
    #2
    1. Advertisements

  3. Lee Wild

    Lee Wild Guest

    Thanks for the reply Bill. I seem to be making some good progress after your
    advice and it has also helped me unearth plenty of settings on the server,
    which before I was unreluctant to do. This is what I have done so far:

    1. Both client and server NIC's are set as 'Local' as you recomended.
    2. I have configured a new scope using the following adresses 192.168.66.1 -
    192.168.66.10
    3. I have created an 'exclusion' for 192.168.66.1
    4. 192.168.66.1 is now the IP address for the NIC on the server
    5. Not sure if this is correct but I have configured both 'Server Options'
    and 'Scope Options' to issue 192.168.66.1 as a DNS server (006) and DNS
    Domain Name (015). Both configured for each option that is.
    6. My default gateway on both the Client NIC and server NIC are now blank.
    7. Also, the DHCP scope that has been newly configured is also activated.

    Just to confirm Bill, now that I have 192.168.66.1 as my DNS address, is
    this the same ip address detail I use on the Server's NIC?

    The IP address on my client is currently static and set to 192.168.66.2 in
    the event that DHCP is not functioning. As a result of this config I can ping
    192.168.66.1 from my client and get a response so there must be connectivty.

    There is an available computer account in my domain but when I try to
    connect the client I get a message returned stating that it is unable to
    locate an SRV record concerning LDAP:

    "The query was for the SRV record for _ldap._tcp.dc._msdcs.contoso.com"

    Am I correct in saying that the ip address for the DC,DHCP and DNS servers
    should be identical?

    Also, I added 192.168.66.1 to the client host file and mapped it to
    , out of shear frustration.

    Do you have any idea bill where I am going wrong based on the info above?
    I will look at setting internet connectivity up eventually just need to get a
    little domain set up first.

    Thanks again.
     
    Lee Wild, Mar 9, 2010
    #3
  4. Lee Wild

    Bill Grant Guest

    Check that the client has 192.168.66.1 as its DNS address. AD uses DNS to
    find the logon server. That is what the following message is all about.
    "The query was for the SRV record for _ldap._tcp.dc._msdcs.contoso.com".

    Did you allow dcpromo to configure DNS for you? Does the SRV record
    above actually exist in your DNS?

    This really has nothing to do with VPC. I recommend that if you have
    further problems, post in the AD newsgroup or forum.
     
    Bill Grant, Mar 9, 2010
    #4
  5. Hello Bill,

    1 red herring to watch out for is to be sure that there are no DHCP settings
    within VPC2007 "local only" network.

    These settings would trump any DHCP server you have in place.
     
    Brad Bird(MVP), Mar 12, 2010
    #5
    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.