Can't join new domain

  • Thread starter Thread starter Tom
  • Start date Start date
T

Tom

I just setup a new win2000 server a few weeks ago.
At that time the office people could log in fine.
When I went there today to try to join the rest of
the machines(which are mainly win2000 pro) I get an
error saying that the name could not be resolved and now
no machines can log in. I can see the shared network
resources fine, but that's it. I have checked the DNS
settings and they haven't changed....any suggestions would
be greatly appreciated.
Thanks.
 
In the TCP/IP properties. What IP addresses are you specifying for DNS?
Is it you ISP? Are you pointing to your self for DNS?

If this is the only domain controller in the domain then you should have DNS
server running on that machine and the machine should be pointing to itself
for DNS. You should also have a forward lookup zone for you DNS domain and
it should be allowing dynamic updates.

Check out Q237675. This should give you the basic info to make sure that DNS
is configured for your Active Directory environment.


--
Todd Maxey
Windows 200X Directory Services
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
-----Original Message-----
In the TCP/IP properties. What IP addresses are you specifying for DNS?
Is it you ISP? Are you pointing to your self for DNS?

If this is the only domain controller in the domain then you should have DNS
server running on that machine and the machine should be pointing to itself
for DNS. You should also have a forward lookup zone for you DNS domain and
it should be allowing dynamic updates.

Check out Q237675. This should give you the basic info to make sure that DNS
is configured for your Active Directory environment.


--
Todd Maxey
Windows 200X Directory Services
=====================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.




.
Click to expand...
Also, I would suggest that you install the Support Tools
from the WIN2000 SP3 CD. Then, go to a command prompt and
enter /dcdiag /v" and "netdiag /fix".


In your DNS, do you have the four subfolders in your FLZ?

HTH,

Cary
 
Todd said:
In the TCP/IP properties. What IP addresses are you specifying for DNS?
Is it you ISP? Are you pointing to your self for DNS?

If this is the only domain controller in the domain then you should have DNS
server running on that machine and the machine should be pointing to itself
for DNS. You should also have a forward lookup zone for you DNS domain and
it should be allowing dynamic updates.

Check out Q237675. This should give you the basic info to make sure that DNS
is configured for your Active Directory environment.
Click to expand...
Also, if you need to resolve web addresses through a gateway, you can
add your internet DNS settings in as Forwarders on a non root DNS
server, if the machine is the only Active Directory Server, you will
need to set it as non root to do this.

This link can help you with that, this was my latest stumbling block,
shortly after having the same issues as yourself, as the reason for my
problems was that I was using the internet gateway for DNS, which
isn't quite what Active Directory wanted.

http://forums.devshed.com/showthrea...&threadid=57909&highlight=Domain+Cable+Router

Good luck

Glenn
 
Back
Top