Re: Can't DCPROMO server needed for migration
From: Danny Sanders (Danny.Sanders_at_NO-SPAMcpcmed.org)
Date: 02/17/05
- Next message: dave Admin: "Re: Can't DCPROMO server needed for migration"
- Previous message: dave Admin: "Re: Can't DCPROMO server needed for migration"
- In reply to: dave Admin: "Re: Can't DCPROMO server needed for migration"
- Next in thread: dave Admin: "Re: Can't DCPROMO server needed for migration"
- Reply: dave Admin: "Re: Can't DCPROMO server needed for migration"
- Reply: dave Admin: "Re: Can't DCPROMO server needed for migration"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 17 Feb 2005 12:09:49 -0700
>> With your set up basically point your original DNS server to itself in
>> the properties of TCP/IP for DNS. Use the actual IP address not
>> 127.0.0.1.
>
> HOW??
Control Panel - Network and dialup connections - Lan connection.
Right click on Lan connection (NIC that attaches the server to the network)
On the general tab select "Internet protocol TCP/IP" and click the
properties button
On the resulting screen your server *should* have a static IP address ( The
radial button should be enabled next to "Use the following IP address")
To "point" your DNS server to itself for DNS you would enable "use the
following DNS server address" and input the preferred DNS server IP address
as the same IP address listed under "Use the following IP address" - IP
address field.
Example if under "use the following IP address" and the IP address entry is
10.1.1.1 Your preferred DNS server will be 10.1.1.1.
>> During logon the proper records will be registered that clients of the AD
>> domain must find in order to *find* the domain.
>
> What does this mean in English?? How do I know if it happened??
When you boot/reboot your DNS server after setting up DNS the netlogon
service is used to register SRV records in the DNS zone on your DNS server.
These records are used by AD Clients (*every* computer on the domain) to
*find* the domain.
If one were to "point" you AD clients to say your ISP's DNS server for DNS,
the SRV records for your domain will not be there. These clients will take
an extraordinarily long time to log in, Group policy will not work and you
will have other problems.
To see if these records have been created see:
How to verify that SRV DNS records have been created for a domain controller
http://support.microsoft.com/default.aspx?scid=kb;en-us;816587
>> Point the server you are trying to add to the domain to the original AD
>> DNS server so it can *find* the records your AD DNS server registered.
>
> How do I "point to the server"???
Control Panel - Network and dialup connections - Lan connection.
Right click on Lan connection (NIC that attaches the server to the network)
On the general tab select Internet protocol TCP/IP and click the properties
button
On the resulting screen your server *should* have a static IP address ( The
radial button should be enabled next to "Use the following IP address")
To "point" your second server to the original DNS you would enable "use the
following DNS server address" and input the preferred DNS server IP address
as the same IP address of your original DNS server.
Example if your original DNS server's IP address is 10.1.1.1, you would
"point" the second server to the original server by inputting 10.1.1.1 as
the preferred DNS server.
>> Set up forwarding or use root hints for Internet access.
>
> How??
This article takes you through setting up forwarders step - by step.
How to configure DNS for Internet access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
hth
DDS W 2k MVP MCSE
"dave Admin" <dmackler@mds.acsol.net> wrote in message
news:OfuhrBSFFHA.3728@TK2MSFTNGP14.phx.gbl...
> >
>> With your set up basically point your original DNS server to itself in
>> the properties of TCP/IP for DNS. Use the actual IP address not
>> 127.0.0.1.
>
> HOW??
>>
>>
>>
>> During logon the proper records will be registered that clients of the AD
>> domain must find in order to *find* the domain.
>
> What does this mean in English?? How do I know if it happened??
>>
>>
>>
>> Point the server you are trying to add to the domain to the original AD
>> DNS server so it can *find* the records your AD DNS server registered.
>
> How do I "point to the server"???
>>
>>
>>
>> Set up forwarding or use root hints for Internet access.
>
> How??
>
> My problem is despite great effort by people like yourself, I have NO
> IDEA what any of this means. Netware does not require DNS, everything just
> communicates by IP addresses.
>
>
- Next message: dave Admin: "Re: Can't DCPROMO server needed for migration"
- Previous message: dave Admin: "Re: Can't DCPROMO server needed for migration"
- In reply to: dave Admin: "Re: Can't DCPROMO server needed for migration"
- Next in thread: dave Admin: "Re: Can't DCPROMO server needed for migration"
- Reply: dave Admin: "Re: Can't DCPROMO server needed for migration"
- Reply: dave Admin: "Re: Can't DCPROMO server needed for migration"
- Messages sorted by: [ date ] [ thread ]