Client Machines Cannot Logon New Windows 2000 Domain Controller

[Mike Willochell]

I am in the process of upgrading our company's NT 4.0
network which worked fine for many years only to have a
major problem configuring the new Windows 2000 Domain
Controller.

I have installed Active Directory, configured DNS, setup
all the user groups and accounts, but no client machine
can locate the domain controller to logon. Strangely, the
shared drives are visible to the client machines, and the
domain controller machine shows up in the Network
Neighborhood on the client machines. Also, none of the
client machines can join the domain because they cannot
find the domain controller.

Any ideas? I am at my wits end trying to find the problem.
I have to put the NT 4.0 PDC on line just so we can logon
and authenticate to get our mail.

Thanks.

 

[Marina Roos]

What OS on the client? How many nics in the server?

Marina

 

[Mike Willochell]

Marina;

The OS's of the clients are mixed WIN 2K Server and
Professional, WIN XP, and WIN 98.

Only one NIC in the server.

Keep in mind that NO client can logon to this DC, but all
can see it and its shared drives. Locally, all user
accounts that I have created work.

Without the old NT PDC on the network, no one can login to
get mail etc.

Thanks.

Mike

 

[Mike Willochell]

Marina;

Not sure about WINS, but the router is the DHCP server so
that is not a problem, and the DNS service is enabled.

Machines cannot join the domain because they do not
recognize the machine as a domain controller.

Mike

 

[Marina Roos]

I would put the DHCP, WINS and DNS-server on your W2000 server.

Can you ping from a client? IP and servername?
Marina

 

[Mike Willochell]

Strangely, I can ping the server by name or IP.