Click to See Complete Forum and Search --> : W2K Server logon authentication


ej115
July 21st, 2001, 09:47 PM
Hello.
We are trying to set up a W2K server as a domain controller.It is one W2K server on a network of 35 nodes in a mixed mode setup. At first, we could not see any other nodes other than W2K Professional machines. I added the permission to add workstations to the domain and tweaked the WINS service and now I can see the rest of the network, but I can't logon from anywhere other than the server. But I can cancel the logon and I can see the network from other machines. I also get the error message that the domain controller was not able to authenticate the logon. What am I forgetting to turn on? Is there some permission I am lacking. I browsed the permissions but didn't see any that applied.There are about 15 or so Win 98s and about 5 or so Win 95s. There are no other domaincontrollers on the network. the DNS is handled by dsl.gtei.net. That is how it was set up when we had an NTserver. The DNS server, then, is different from the server handling the Active Directory. The Active dir and WINS and DHCP is handled ny the server we are trying to configure, and DNS is handled by the afore mentioned server.
We also get some errors that there is no domain controller.
Thanks for your help.

Ron Prestenback
July 21st, 2001, 10:40 PM
What other machines do you have on the network? Are there any domain controllers already on this network? And if so, what type are they? You'll have to explain a little bit about how your network is set up right now, and what you've changed in adding the Win2K Server. For instance, is your DNS contained on the same Server that you just set up, or is it somewhere else? Are the clients configured to use the same DNS server that is handling Active directory?

Are you getting this error when you try to join the domain from the workstation machines, or are you able to join the domain, but you can't logon thereafter? Are there any errors in your event viewer logged? I would check both the Server and the Professional machines and see if any turn up. It could be DNS problems. It could also be Active Directory issues. Once you post more info, I'll be able to help a little more.