Windows 2000 Sever AD Quesiton

  • Thread starter Thread starter Chan Ho
  • Start date Start date
C

Chan Ho

I have set up a new AD - domain controller, which take over the job of my
old server. I've set all 5 roles of AD controller to the new server, and
also set the new server as global category server. However, when I try to
shut down the old server. User is unable to login, or login use the cache
information on local machine. What should I need to do more on the new
server. Please help.
 
Does your new server do DNS or do you have another DNS server on the
network?
 
DD, as Berndon says the new Domain Controller or any other existing Domain
Controller must running an Active Directory Integrated Zone. All Servers and
clients must point to this Domain Controller in there TCP/IP DNS Settings.

Also look in the Directory Service log in the event we there you should see
messages about the particular servers now are a Global Catalog Server.
 
DD, as Berndon says the new Domain Controller or any other existing Domain
Controller must running an Active Directory Integrated Zone. All Servers and
clients must point to this Domain Controller in there TCP/IP DNS Settings.
Click to expand...
No, the DNS doesn't have to be Active Directory integrated even on a
Domain Controller. DNS doesn't have to be on the Domain Controller at
all. All that is required of DNS by AD is that it supports SRV
records.

Many people happily run AD Domains with bind and Novel and other DNS
servers.

Cheers,

Cliff

(MVP)
 
Sorry, I am so dumb, do you mean I need to set the new server as DNS server
as well to do so?

Bye the way, my worksatations on the network DNS setting is not point to the
domain controller. But it can still join domain and login......
In my experience, the DNS should set to the domain contoller to do
so.......sounds strange.....
 
The workstations need to know where the DNS is that contains the SRV
records. This is normally the internal DNS for the LAN. All clients,
server or workstation, should point to the internal DNS for DNS
lookups. The internal DNS should normally be set to point to itself.
If there are more than one servers that run the DNS service, each DNS
server should point to itself for DNS, and it should also forward
requests for external Domains for external servers and services (eg
http://www.microsoft.com). Each server in the internal DNS should
replicate with the others either by normal DNS master/slave or via AD
replication for AD Integrated DNS. (This is the NORMAL setup. There
may be other solutions for other needs, but this will serve for most
simple setups).

You do not say anything about your DNS configuration so I don't know
what to recommend. Could you tell us of your DNS configuration? The
original question about DNS leads me to believe that the poster
thought that your DNS was on the original DC and that you hadn't set
up DNS anywhere else. Hence the workstations couldn't find the SRV
records.

I don't know whether or not this is true, though it is a strong
possibility. Please tell us more about your setup.

Cheers,

Cliff

(MVP)
 
Back
Top