Upgrade to WIN2000 -> Can I continue to use WINS?

[Mickee]

When I upgrade my WinNT4.0 PDC to Win2000, does it require me to use DNS for
our internal network?

Currently, the DNS settings on our workstations refer to our ISP's DNS
servers and, as we use WINS internally, Primary and Secondary WINS server
are local I.P. addresses.

I would like to keep this same setup after upgrade to WIN2000. Is this OK?
Any specific step during upgrade?


Thanks.

 

[Danny Sanders]

When I upgrade my WinNT4.0 PDC to Win2000, does it require me to use DNS
for

our internal network?

You MUST have a DNS server set up for the AD domain and ALL AD clients MUST
point to the AD DNS server ONLY. Do not point them to your ISP's DNS server.

See:
Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675

For Internet access see:
How to: Configure DNS for Internet Access In Windows 2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;300202

You can continue to use WINS if you need to.

hth
DDS W 2k MVP MCSE

 

[Mickee]

Thanks for reply.
I guess, what you say is true only if I install AD. If I do not install AD
for now, I do not have to worry about DNS - isn't that right?

 

[Danny Sanders]

I guess, what you say is true only if I install AD. If I do not install AD

for now, I do not have to worry about DNS - isn't that right?

That is true, but you should be aware that the installation of AD is what
changes a Win 2k member/standalone server into a DC. You can not have a Win
2k DC without AD.

Without AD the most you can accomplish is to have a Win 2k member server on
a NT 4.0 domain or a Win 2k workgroup.

No AD no domain in Win 2k and Win 2k3.

hth
DDS W 2k MVP MCSE

 

[Mickee]

YOU SAID:

Without AD the most you can accomplish is to have a Win 2k member server on
a NT 4.0 domain or a Win 2k workgroup.

However, I am upgrading my WinNT PDC. Which will remain the PDC after
upgrade to Win2000 and not become a member server - Right?

Thanks, once again.

 

[molsonexpert]

YOU SAID:


However, I am upgrading my WinNT PDC. Which will remain the PDC after
upgrade to Win2000 and not become a member server - Right?

Thanks, once again.

Correct me if I'm wrong, but the concept of a PDC in W2K doesn't exist
(although a PDC emulator role does exist). After the upgrade, you will
either have a W2K workgroup, which I don't believe requires DNS, or you can
configure a W2K domain, in which case you will have to install Active
Directory and you must have DNS configured as well.

steve.

 

[Danny Sanders]

However, I am upgrading my WinNT PDC. Which will remain the PDC after

upgrade to Win2000 and not become a member server - Right?

Thanks, once again.

When you upgrade your NT 4.0 PDC to Win 2k the install will realize it is a
DC and run dcpromo automatically. Running dcpromo installs AD, which
requires DNS.

This server will become the "PDC emulator", one of 5 roles that can be
transferred to *any* DC in the domain/forest. All DCs in Win 2k are equal
except for the 5 FSMO roles of which there can only be one per
domain/forest.

The idea of a PDC/BDC was dropped with Win 2k.

hth
DDS W 2k MVP MCSE

 

[Mickee]

Ok. I think I will
1. Upgrade PDC to Win2000.
2. Install DNS.
3. Install AD.
4. Upgrade BDC to Win2000.

The main confusion / hesitation I have is related to DNS. I don't host any
website and my network has nothing to do with the zones on the internet. I
have a DSL router through with I connect to the internet. This is a small
network with 20 Win2K workstations and WINNT PDC and BDC.

My LAN domain is named "ABC".
When I install DNS, exactly what information will be required to enter? Can
someone give an example specific to my type of environment?


Thanks.

 

[Danny Sanders]

1. Upgrade PDC to Win2000.

2. Install DNS.
3. Install AD.
4. Upgrade BDC to Win2000.

When you upgrade the PDC to Win 2k dcpromo is ran automatically. After
dcpromo is ran install DNS.

The main confusion / hesitation I have is related to DNS. I don't host any
website and my network has nothing to do with the zones on the internet. I
have a DSL router through with I connect to the internet. This is a small
network with 20 Win2K workstations and WINNT PDC and BDC.

My LAN domain is named "ABC".
When I install DNS, exactly what information will be required to enter? Can
someone give an example specific to my type of environment?

Actually Win 2k's DNS is dynamic. By pointing the DNS server to itself in
the properties of TCP/IP it will use the netlogon process to register the
DNS records that your clients MUST find in order to find the domain. That is
why ALL AD clients MUST point to the DNS server set up for AD.

In your environment you would install Win 2k and AD. Install DNS, and
manually input the DNS server's own IP address as the entry for DNS in the
properties of TCP/IP. When you reboot (netlogon process runs) check your DNS
server for the proper SRV records.
See:
How to Verify the Creation of SRV Records for a Domain Controller

http://support.microsoft.com/default.aspx?scid=kb;en-us;241515



Point ALL other clients and servers to this DNS server either manually or
use DHCP.



The fact that Win 2k's DNS is dynamic means that ALL those clients pointed
to the DNS server for DNS resolution will register their own records during
logon. You do not have to manually enter any DNS records unless you name
your AD domain the same ad your publicly registered Web domain.



If you follow these two links closely you can get DNS up and running fairly
easily. Your AD clients MUST point to the AD DNS server ONLY. Using your
ISP's DNS server on AD clients will result in LOOOONG login times (they are
looking for the SRV records that will NOT be found on your ISP's DNS
servers).



I can understand you hesitation with DNS but it is easier with Win 2k.

See:

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675



For Internet access

see:

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

 

[Mickee]

Thanks a lot Danny - You have been great help.

When you upgrade the PDC to Win 2k dcpromo is ran automatically. After
dcpromo is ran install DNS.



Actually Win 2k's DNS is dynamic. By pointing the DNS server to itself in
the properties of TCP/IP it will use the netlogon process to register the
DNS records that your clients MUST find in order to find the domain. That is
why ALL AD clients MUST point to the DNS server set up for AD.

In your environment you would install Win 2k and AD. Install DNS, and
manually input the DNS server's own IP address as the entry for DNS in the
properties of TCP/IP. When you reboot (netlogon process runs) check your DNS
server for the proper SRV records.
See:
How to Verify the Creation of SRV Records for a Domain Controller

http://support.microsoft.com/default.aspx?scid=kb;en-us;241515



Point ALL other clients and servers to this DNS server either manually or
use DHCP.



The fact that Win 2k's DNS is dynamic means that ALL those clients pointed
to the DNS server for DNS resolution will register their own records during
logon. You do not have to manually enter any DNS records unless you name
your AD domain the same ad your publicly registered Web domain.



If you follow these two links closely you can get DNS up and running fairly
easily. Your AD clients MUST point to the AD DNS server ONLY. Using your
ISP's DNS server on AD clients will result in LOOOONG login times (they are
looking for the SRV records that will NOT be found on your ISP's DNS
servers).



I can understand you hesitation with DNS but it is easier with Win 2k.

See:

Setting Up the Domain Name System for Active Directory

http://support.microsoft.com/default.aspx?scid=kb;en-us;237675



For Internet access

see:

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



me me