Discussion Locked

W2K domain problem

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a network at home and I am having a problem getting the workstation to acknowledge the domain. I have set
this up B4 and it worked but now I don't know if I'm over looking something or if it's the OS. The Client is W2K Pro on a Compaq deskpro EN 733 and the Server is W2K Adv. Server on a Compaq deskpro EN 733(tower). When I try to set the client up to access the domain it tells me that the domain doesn't exist or could not B contacted. After this error message I check the server to see what is listed on the network and the workgroup is listed. I can also access the server from the client. So instead of adding a single PC to the network it adds the clients workgroup to the domain. DNS & WINS is set up on the server. My laptop can hit the server and network just fine. The weird thing is that I can pull files from the server from this client that tells me the domain does not exist. The folder it is pulling from has the perm. set to just the users on the domain and NOT to everyone.

5 replies

by ian mclaws

In your question, you mention that after n error, you check and find that the "workgroup" is listed. I thought you said you had a domain? If you have not run the Active Directory setup, you have not yet created a domain. To check, go to system properties \ network identification tab. If the "change" button is not grayed out, you have not yet got a domain! (You must run the "configure my server" wizard to create the domain.)
If the button is grayed out, you are a domain controller, and chances are your problem is DNS. WINS won't help you, the Active Directory service relys on DNS exclusively. Check to make sure that your DNS server has the proper .srv records on it that advertise the domain. If it does not, the client will get the error message you mention. The zone you created in DNS must also be enabled for dynamic updates. (If you didn't create a zone....you're not running a domain at all...see first suggestion!)
Also make sure your client system is using the DNS server (DNS server search entry).

Let me know how it goes,

Ian

This discussion is closed to new replies.