Re: Creating a Virtual Domain

Mike,

Thanks for your response.

Everything you said in your email made perfect sense. I have included
"ipconfig /all" results for the DC and client virtual PCs respectively at
the bottom of this message.

I believe you can verify (see below) that my network connection is exactly
as you had suggested.

The problem is that when I try to join the client to the domain I get a
"Windows cannot find the network path" error. Note, I logged in as
administrator@xxxxxxxxxxxxxx

I ensured that my DC was rebooted.

Also, I am able to ping the DC from the client.

Cheers,
Frank


--------------------------------------------------------------------------------------------------------------

Windows IP Configuration

Host Name . . . . . . . . . . . . : vancouver
Primary Dns Suffix . . . . . . . : mydomain.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mydomain.local

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-03-FF-1C-3E-38
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 127.0.0.1


Windows IP Configuration

Host Name . . . . . . . . . . . . : toronto
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Mixed
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel 21140-Based PCI Fast Ethernet
Adapter (Generic)
Physical Address. . . . . . . . . : 00-03-FF-15-3E-38
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.2.120
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 192.168.2.2





"Miha Pihler [MVP]" <mihap-news@xxxxxxxxxxx> wrote in message
news:%23Tjoypg1FHA.1564@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> Check DNS settings on both virtual computers. IPconfig results that you
> posted here did not show all the ipconfig settings. You should do
>
> ipconifg /all
>
> on all your computers and post here. The result will also show DNS and
> other settings.
>
> In general domain controller must also use Active Directory DNS (and _not_
> e.g. ISP DNS server). So set the domain controller to point back to
> itself. You could enter 192.168.2.2 under preferred DNS server or even
> better 127.0.0.1. Now restart NetLogon service on DC.
> Now change preferred DNS settings on your virtual client that you would
> like to join to domain "mydomain.local" to point to 192.168.2.2 (not --
> here you can't use 127.0.0.1 since there is no DNS installed on this
> server).
>
> Now try to join your virtual client to mydomain.local domain.
>
> Note: in general it is not best practice to use "mydomain.local" for
> production Active Directory DNS name.
>
> --
> Mike
> Microsoft MVP - Windows Security
>
> "Frank J. Reashore" <reashore@xxxxxxxxxxxxxxx> wrote in message
> news:euQeLYg1FHA.1256@xxxxxxxxxxxxxxxxxxxxxxx
>>I have two virtual PCs (running Win2003 Enterprise SP1) hosted on my home
>>WinXP Pro SP2 (which is connected to my ISP). I am trying to create a
>>domain of the virtual PCs, but am encountering problems joining the
>>second virtual PC to the domain.
>>
>> I converted the IP address of one Virtual PC to static, promoted it to a
>> domain controller, and installed DNS. I named the new domain
>> "mydomain.local".
>>
>> Note also that I have assigned distinct names to each to each of the
>> virtual machines.
>>
>> The second virtual PC has a dynamic IP address and belongs to WORKGROUP.
>>
>> I am able to ping the virtual domain controller from the virtual client
>> machine. My exact network configuration is shown at the bottom of this
>> message.
>>
>> When I attempt to join the client virtual PC to the domain (via Control
>> Panel => System =>
>> Computer Name => Change.), I get the standard login prompt (to which I
>> enter administrator@xxxxxxxxxxxxxx and password). However, I then get the
>> following error:
>>
>> --------------------------------------------------------------------------------------
>> The following error occurred when DNS was queried for the service
>> location (SRV) resource record used to locate a domain controller for
>> domain mydomain.local:
>>
>> The error was: "DNS name does not exist."
>> (error code 0x0000232B RCODE_NAME_ERROR)
>>
>> The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.local
>>
>> Common causes of this error include the following:
>>
>> - The DNS SRV records required to locate a domain controller for the
>> domain are not registered in DNS. These records are registered with a DNS
>> server automatically when a domain controller is added to a domain. They
>> are updated by the domain controller at set intervals. This computer is
>> configured to use DNS servers with following IP addresses:
>>
>> 192.168.2.1
>>
>> - One or more of the following zones do not include delegation to its
>> child zone:
>>
>> mydomain.local
>> local
>> . (the root zone)
>>
>> --------------------------------------------------------------------------------------
>>
>> This error is occurring because my virtual client is using the DNS of my
>> ISP and it is not able to "delegate" the join request to the
>> "mydomain.local" domain.
>>
>> Alternatively, I have tried to configure my client virtual machine to use
>> the DNS of the virtual domain controller but that also leads to different
>> errors.
>>
>> So my question is: How do I configure my setup so that the join request
>> for the domain from the virtaul client is successfully passed to the
>> virtual domain controller?
>>
>> Thanks in advance for any help.
>>
>> Regards,
>> Frank J. Reashore, MCSD.net, MCDBA
>>
>> Vancouver, Canada
>>
>> ********************************************************
>>
>> Windows XP Pro (Host PC + WORKGROUP)
>>
>> Connection-specific DNS Suffix . : bc.hsia.telus.net
>> IP Address. . . . . . . . . . . . : 192.168.2.117 (dynamic)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>>
>> Windows Server 2003 Enterprise (Virtual PC + Domain controller + DNS +
>> domain = mydomain.local)
>> Connection-specific DNS Suffix . :
>> IP Address. . . . . . . . . . . . : 192.168.2.2 (static)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>>
>> Windows Server 2003 Enterprise (Virtual PC + Client + WORKGROUP)
>> Connection-specific DNS Suffix . :
>> IP Address. . . . . . . . . . . . : 192.168.2.120 (static)
>> Subnet Mask . . . . . . . . . . . : 255.255.255.0
>> Default Gateway . . . . . . . . . : 192.168.2.1
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>


.

Relevant Pages

  • Re: Remote Web Workspace
    ... Your DNS is definitely wrong. ... the Client computers should point to the server LAN NIC. ... > Ethernet adapter Server Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
  • Re: SRV records
    ... Ethernet adapter Local Area Connection: ... The attempt to establish a replication link for the following writable ... Source domain controller address: ... 8524 The DSA operation is unable to proceed because of a DNS lookup failure. ...
    (microsoft.public.windows.server.dns)
  • Re: Lost Resources
    ... Sorry, but i am talking about the client in the site, not your connection. ... This posting is provided "AS IS" with no warranties, ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD management snap in cannot find DC
    ... Did you check that the time zone and time on the DC and the client are the same? ... The domain machines should all have the imageproc.imageproc.com in the "Primary DNS suffix of this computer" field. ... ping 192.92.109.6 ok ... I get a dialog Domain Controller ...
    (microsoft.public.windows.server.active_directory)
  • Re: Basic, yet detailed, Tor questions.
    ... tor client residing on your machine securely encrypts everything ... anyone observing your connection) can see is encrypted data traveling ... between you and your first tor node. ... Ideally, and typically in socks4a, the tor exit node does DNS ...
    (alt.privacy)