Tom's Guide | Tom's Hardware | Tom's Games
 |
 |
 |
I am trying to connect my NT computer to a domain.
I am able to ping the domain computer and the domain computer can ping my computer but when I try to connect the computer to the domain it gives me the following error:
The domain controller for this domain cannot be located.
Has anyone seen this before?
Yes I have.
Going through network neighbourhood I can see my domain and the domain controller. When I double click on the domain controller it says:
Domain Controller is not accessible.
Access is denied.
0 
You said when you try to connect the computer to the Domain, you get the error that the DC cannot be located. Yet, in your second post, you say you can't access the DC through Network Neighborhood. Those are two different issues.
Have you indeed added the client computer name to the Server and then removed the machine from the Workgroup and changed it to actually authenticate to the Domain?
Perhaps you could type in the steps you followed before getting the error "the domain controller for this domain cannot be located."
0
Here are the steps:
1. Go to Control Panel
2. Open up Network
3. Click on Change
4. Select Domain
5. Type in my domain
6. Click okayWhen I click okay, thats when I get the error:
The domain controller for this domain cannot be located.
What I was trying to say with the Network Neighbourhood was that I can see the Domain, I can see the Domain Controller, I just can't get my Network Identification to change from my Workgroup to the Domain so I can log on under the Domain.
The machine is definitely added to the server.
0
I guess I should also say the client computer is running Windows NT Workstation 4.0 and the server is running Windows 2003 Server.
0
I know this may be an obvious question, and the answer is probably yes, but do you actually have the proper privileges (such as Domain Admin) to change the machine from a Workgroup to authenticating it on the Domain?
0
the no domain found can sometimes mean your dns entries are off. Is the dns server listed in the network properties? Can you ping the server by name?
0
David,
Try this first:
Go to Control Panel
Network.
Protocols
TCP/IP
Properties
WINS Address.
Clear the Enable LMHOSTS Lookup check box.
OK
Close
RebootThen try to re-add the client.
If that doesn't work, the client may be trying to authenticate using cached credentials. So, if that's the case:
Remove the computer account from the Server.
Login to the client locally and put it back into the Workgroup.
Reboot
Login locally
Wait 15 minutes or so...re-add the computer account to the Server
Wait another 15 minutes and go through steps to add the client to the Domain.
0
Not the worlds best person at running a domain, but I think you need to make a user on the primary domain controller first, and give permissions in the domain your trying enter.
I know there are ways to do this and enter as a domain guest, but never had managed to get that to work. Least that what they said in RAS class so long ago.
NT is a frustrating thing, I give up a lot on my box here. Then another day take a shot at it again.
Cheers
Good judgment comes from experience, and a lot of that comes from bad judgment..... Will Rogers
0  |
 |
 |
This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |
