12 replies
by mhasf
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
by mhasf
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
by douglasb
by n3voc
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.
by douglasb
Poster rated this answer.
by cg it
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.
by douglasb
Poster rated this answer.
by douglasb
by sgt_shultz
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
by douglasb
Poster rated this answer.
by douglasb
by briangbeaton
Your problem is that your client machine cannot resolve the Domain name you are providing. In order to be able to contact the Active Directory it first has to know where it is.
In order to achieve this, you have to set your TCP/IP properties on your client machine to point your Primary DNS or Alternative DNS to either the IP address of the Active Directory machine itself (Which normally has DNS running) or a DNS server which can resolve the IP address of the Active Directory Domain name to the IP address of your AD server.
This should fix your problem.
Island Boy
This discussion is closed to new replies.
Trending Networks posts
Sort by Trending