General discussion

Locked

Add User/Computer to Active Directory

By DouglasB ·
I got a job working in a small office setting maintaining their computers. The previous tech set the office up as a domain, no workgroups. On the Windows 2000 server I set up a new user/computer but when trying to connect the new user/computer workstation to the server it won't go. I put in the user name and domain name in the network setup but get the error message "can't find the domain controller." Any ideas? I have never worked with a domain before, just workgroup setup. Thanks!

This conversation is currently closed to new comments.

12 total posts (Page 1 of 2)   01 | 02   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by mhasf In reply to Add User/Computer to Acti ...

Did you join the workstation to the domain? You need to do that if you want it to log into the domain normally. Just add the workstation to the domain by going in to the System Properties in control panel and go to computer name. You will see where you can put in the domain name, etc. When it gets to the point of adding it, use your admin user name and password. After the required reboot, log in to the domain with the user you created.

Good Luck!

Marc

Collapse -

by mhasf In reply to

One other issue is that you need to point the DNS in the workstation to the address of the AD server that has the DNS server. I believe you have a rather simple network in that there would be only one server. Make sure to point your workstation's DNS entry there.

Marc

Collapse -

by DouglasB In reply to

This was the fix, I was not using the admin username and password. Thanks!

Collapse -

by n3voc In reply to Add User/Computer to Acti ...

Verify you are connected to the network (NIC signal light blinking?)

The first question would be are you running DHCP or static IP addresses? DHCP needles to say is much easier to maintain. IF DHCP, make sure the NIC has DHCP enabled.

If no DHCP, you need to configure TCP/IP with a static IP address and add the computer in your Active Directory on the domain controler.

Then right click my computer, click the computer name tab, click the Change button. Enter a computer name, and the complete domain name (yourdomain.net) then click OK.

Collapse -

by DouglasB In reply to

Poster rated this answer.

Collapse -

by CG IT In reply to Add User/Computer to Acti ...

both DouglasB and Mhasf have the answers.

I would highly recommend that if you are going to be the network admin you atleast get your MCSA Windows 2000 certification. With that you'll have a fundamental working knowledge of Windows 2000 server, Active Directory, DNS, DHCP, Group Policy, File Folder permissions on NTFS, TCP/IP, published resources in Active Directory [such as shared printers and folders]. Another highly recommended area to learn is Software Update Service/Windows Update Service so that you can keep your servers and your workstations up to date with patches, service packs and hotfixes. I would baseline all the computers [servers and workstations] now to find out what you might need to patch up. Last area to learn is security. There are many security settings for domain controllers, DHCP, DNS, workstations that if your connected to the internet, you need to have configured. As an example zone transfers, DNS queries, Remote Access, Secure AD updates etc.

Collapse -

by DouglasB In reply to

Poster rated this answer.

Collapse -

by DouglasB In reply to Add User/Computer to Acti ...

OK, so I need to use the Admin username and password on the workstation? That is what I was doing wrong, I think, I was inputing the workstation username and password, was that is that my problem? I checked other stations that were already setup and everything is set for DHCP, no DNS entries that I could see.

Collapse -

by sgt_shultz In reply to Add User/Computer to Acti ...

what os at ws did you mention on ws and what sp?
maybe not ad problem, maybe tcpip or physical network problem (cabling, nic media type mismatch)
take error message at face value: it can't find the domain controller. it can't even get to ad yet to find how you messed that up (rdl)(you go!)
at bad computer:
check link lite both ends
check network connection to see if firewalled, if yes, turn off that xp firewall and any others for a test
open command prompt,
use ipconfig /release then /renew to see if ws is
ping domain controller
see what ipconfig reports, compare to working ws

Collapse -

by DouglasB In reply to

Poster rated this answer.

Back to Networks Forum
12 total posts (Page 1 of 2)   01 | 02   Next

Hardware Forums