"Bill Grant" <not.available@xxxxxx> wrote in message
news:O4%23D07P$JHA.4376@xxxxxx
Quote:
>
>
> "Jack" <noreply@xxxxxx> wrote in message
> news:eb2xhIH$JHA.3732@xxxxxx Quote:
>> "Bill Grant" <not.available@xxxxxx> wrote in message
>> news:uczP2gE$JHA.3708@xxxxxx Quote:
>>>
>>>
>>> "Jack" <noreply@xxxxxx> wrote in message
>>> news:e#qhqcE$JHA.1376@xxxxxx
>>>> "Bill Grant" <not.available@xxxxxx> wrote in message
>>>> news:OM8pPKE$JHA.3320@xxxxxx
>>>>>
>>>>>
>>>>> "Jack" <noreply@xxxxxx> wrote in message
>>>>> news:OEBxidD$JHA.4692@xxxxxx
>>>>>> I want to add a server role to my guest OS Win2.3k server... DC
>>>>>> I want to be able to play with Active Directory, mostly querying it
>>>>>> using LDAP.
>>>>>>
>>>>>> I'm not really from a networking knowledge (more app prog). When I
>>>>>> try to add this role Win2.3k asks me for a DNS FQDN. As this guest is
>>>>>> just a stand alone instance there is no domain etc.
>>>>>> Am I able to get around this stuff so I can get AD up and running?
>>>>>
>>>>> If you want to play with AD, the best method is to put the server in
>>>>> Local Only and give it a static IP in its own IP subnet (ie not the
>>>>> same one as the host). You can then set up AD in its own domain with
>>>>> its own DNS (and DHCP if you like).
>>>>>
>>>>> With only 2G of memory you are pretty limited, but you could
>>>>> probably run an XP guest as well if you give both server and client
>>>>> 512M each. Put the guest in Local Only as well and it should get its
>>>>> network config from DHCP on the server.
>>>>
>>>>
>>>> Thanks Bill,
>>>> I'm 99% certain I chose to not join a forest/domain at this point when
>>>> setting up 2.3
>>>> Is this what you meant? I'm not sure how to specify local only.
>>>> I don't want another guest to talk to the server. Simply using .NET
>>>> code to talk to AD on the server.
>>>> Can you tell me where I assign the IP, Subnet addresses and set the DNS
>>>> and DHCP options please?
>>>
>>> Where are you planning to talk to AD from? The host machine? I would
>>> not recommend that. I also suggest you do a bit more reading on AD!
>>>
>>> You select Local Only for the NIC in the guest from the vm settings
>>> for the guest machine.
>>
>>
>> If I select local only I get no internet access for the guest.
>> But now that I have all the latest windows updates etc perhaps I don't
>> need net access anymore >
> Once you promote it to a DC, you wouldn't have Internet access anyway
> unless you modified the DNS. You are better off having the DC isolated
> from the host machine and any network it might connect to.
> OK I've changed the VPC settings to be "local only"
Now I go to add/remove roles and select DC.
It goes through the set up and tells me that I have to set up the DNS server
address before I can continue.
Any ideas?
How can I get past all these networking config requirements and just get the
role up and running so I can play with AD?