I'm connected to the Domain but I'm not, please HELP...

  • Thread starter Thread starter Kelvin Beaton
  • Start date Start date
K

Kelvin Beaton

I've had my network and domain running for a year or so now.
Windows 2003 DC (current on service packs)
Windows 2003 member server
Windows 2000 (used to be the DC but brought then new one on months ago)

I'm not aware of any changes to the network, but ass of a day or so ago I
have the following symptom.

From a Windows XP work station if I go to Control Panel\User
Accounts\Advanced Tab\Advanced button\Groups\Administrators\Add, and if I
clik on Locations, under the list of locations to search, the only option is
my local computer name. The Domain is not listed.

If I click on a folder then choose the Security Tab and try and add a user
of group from the Domain and click on Locations I get the same thing, only
the local computer name, the Domain is not an option.

These symptoms are the same for a new computer and also computers that have
been on the network. I've tested this on my computer and it acts the same as
the new one.

When I setup the new PC I added it to the domain and it showed up in the
Computers folder like normal. So that seemed fine.

I also noticed that when I try and open an MMC that I created on my
workstation and have used for a year of so, now I can't open it.
The box is titled, Active Directory, "Naming information cannot be located
because: The specified domain either does not exist of could not be
contacted. Contact your system administrator to verify that your domain is
properly configured and is currently online."

I have also noticed that when users a logging in it takes a long time. First
it says Loading Personal Setting and then it says Applying Person Settings
and it takes 2-3 minutes to load. They can log in. I have created new users
and they can log in.

Can anyone shed light on this issue?

Any advice would be appreciated.

Kelvin
 
Kelvin said:
I've had my network and domain running for a year or so now.
Windows 2003 DC (current on service packs)
Windows 2003 member server
Windows 2000 (used to be the DC but brought then new one on months
ago)
I'm not aware of any changes to the network, but ass of a day or so
ago I have the following symptom.

From a Windows XP work station if I go to Control Panel\User
Accounts\Advanced Tab\Advanced button\Groups\Administrators\Add, and
if I clik on Locations, under the list of locations to search, the
only option is my local computer name. The Domain is not listed.

If I click on a folder then choose the Security Tab and try and add a
user of group from the Domain and click on Locations I get the same
thing, only the local computer name, the Domain is not an option.

These symptoms are the same for a new computer and also computers
that have been on the network. I've tested this on my computer and it
acts the same as the new one.

When I setup the new PC I added it to the domain and it showed up in
the Computers folder like normal. So that seemed fine.

I also noticed that when I try and open an MMC that I created on my
workstation and have used for a year of so, now I can't open it.
The box is titled, Active Directory, "Naming information cannot be
located because: The specified domain either does not exist of could
not be contacted. Contact your system administrator to verify that
your domain is properly configured and is currently online."

I have also noticed that when users a logging in it takes a long
time. First it says Loading Personal Setting and then it says
Applying Person Settings and it takes 2-3 minutes to load. They can
log in. I have created new users and they can log in.

Can anyone shed light on this issue?
Click to expand...

So..
What happens if you remove the system from the domain and rejoin?
What happens if you remove the system from the domain, use AD U&C and remove
it completely - wait 15 minutes and then rejoin the computer to the domain?
 
The box is titled, Active Directory, "Naming information cannot be
Nine time out of ten "naming information" errors refer to a DNS problem.

Basic AD DNS setup. Set up a DNS server for the AD domain, point this server
to itself in the properties of TCP/IP, Point all AD clients to the DNS
server setup for the AD domain only. For Internet access configure your AD
DNS server to forward requests and list your ISP's DNS server as the
forwarder. This is the only place on your domain your ISP's DNS server
should be listed.

*Usually* Naming information errors are because the AD client is pointing to
the ISP's DNS. This will cause naming information errors, long log in times,
group policy won't work, and a whole host of other problems.

hth
DDS W 2k MVP MCSE
 
Something has happened in the last day or so and my guess is that there may
be a problem with the domain controller since many domain computers are
affected. Check the logs on it via Event Viewer to see if anything pertinent
is recorded. I would also run the support tools netdiag and dcdiag on it
which will run a battery of tests and report the results. Also run netdiag
on one of the problem domain computers. Failures or warnings can help
pinpoint and solve the problem. The support tools are on the install disk in
the support tools folder where you need to run the setup program to install
the support tools set. First I would reboot the domain controller to see if
anything changes in case it has a problem with a stalled service, etc that a
reboot may resolve. You can post any results of netdiag/dcdiag here in a
reply if you need some help interpreting the results. --- Steve

http://support.microsoft.com/default.aspx?scid=kb;en-us;321708 --- netdiag
and how to install support tools
 
thanks for the help.

Turns out I had the wrong DNS IP addresses in my DHCP service...

Seems all is well now!

Thanks

Kelvin



Danny Sanders said:
Nine time out of ten "naming information" errors refer to a DNS problem.

Basic AD DNS setup. Set up a DNS server for the AD domain, point this
server to itself in the properties of TCP/IP, Point all AD clients to the
DNS server setup for the AD domain only. For Internet access configure
your AD DNS server to forward requests and list your ISP's DNS server as
the forwarder. This is the only place on your domain your ISP's DNS server
should be listed.

*Usually* Naming information errors are because the AD client is pointing
to the ISP's DNS. This will cause naming information errors, long log in
times, group policy won't work, and a whole host of other problems.

hth
DDS W 2k MVP MCSE
Click to expand...
 
Back
Top