Results 1 to 4 of 4
  1. #1
    3 Star Lounger
    Join Date
    Apr 2002
    Location
    UK
    Posts
    298
    Thanks
    6
    Thanked 0 Times in 0 Posts

    Thumbs up

    OK,

    I'm setting up a virtual network using ESXi (that might not sound like home networking but yeah, I'm a computer junkie and I have an ESXi host server at home) ... I don't think this is an ESXI problem specifically (I don't see how it can be) and so far I've built the following VM's:

    • A Windows 2008 (standard) domain controller (static IP, DNS, DHCP etc.)
    • A Windows 2003 file and print server (static IP, member server)
    • A Windows XP Pro client (DHCP client)


    The IP's are in the same range as my physical network (given that my router is the only point of access to the internet and can only have one IP address I assume I have to do that unless I use the DC as some kind of IP bridge as well).

    Both virtual servers can "see" each other and, as I recall, I had no issues making the first a DC or the second a member of the new domain and both have excellent access to the internet. Both servers can also "see" my physical 2003 server.

    The Windows XP Pro VM is a different matter though. It can also access the internet ... by default it was picking up an address from my physical server (DHCP) but I temporarily turned that off, reacquired an address from the virtual DC and now (even with both DC's providing DHCP) it continues to use the virtual DC supplied addresses and DNS.

    That's good but I don't get why it can't "see" any of the virtual servers (can't map drives, can't be joined to the new domain). Do I need to set up some kind of static routing, edit hosts or add some kind of DNS record?

    Any help appreciated

    Kyu

  2. #2
    3 Star Lounger
    Join Date
    Apr 2002
    Location
    UK
    Posts
    298
    Thanks
    6
    Thanked 0 Times in 0 Posts

    Post

    Turns out it was (primarily) lack of WINS assigned by DHCP.

    Microsoft has "demoted" WINS from a "role" to a "feature" so when setting up a new 2008 DC WINS is not so obviously or easily (can't remember which) installed i.e. you have to make a conscious choice to find/install it as a feature in the 2008 server management MMC.

    Once I had installed that and configured DHCP to supply WINS server automatically the XP client worked fine.

    Kyu

  3. #3
    Plutonium Lounger
    Join Date
    Nov 2001
    Posts
    10,550
    Thanks
    0
    Thanked 7 Times in 7 Posts
    Sounds like you're having a lot of fun with this network! Do please keep posting your solutions so we can learn with you as you make progress.

  4. #4
    3 Star Lounger
    Join Date
    Apr 2002
    Location
    UK
    Posts
    298
    Thanks
    6
    Thanked 0 Times in 0 Posts
    [quote name='StuartR' post='788099' date='08-Aug-2009 22:12']Sounds like you're having a lot of fun with this network! Do please keep posting your solutions so we can learn with you as you make progress.[/quote]

    Oh yes!!!

    The DHCP failed and I'm still not sure why (I think it may concern the fact that 2008 gets "upset" when it hasn't got IPv6 configured, I'm only using IPv4) ... I eventually solved it by building a server 2003 VM and that now handles DHCP.

    Perhaps I should start playing with IPv6?

    Kyu

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •