4 Replies

See the link below for more details as this is often a name resolution or network connectivity problem.

Your domain clients should be able to ping the domain controller by it's IP address and fully qualified domain name as in dc1.mydomain.com as an example of a FQDN. The domain controller should be able to do the same for the domain clients.

Look in Event Viewer on the domain controller to see if any related events are being recorded that may help you resolve the problem such as failed services,etc. The support tool netdiag and dcdiag are also very helpful in tracking down domain configuration/network connectivity problems.

Use netdiag on any computer and dcdiag on just domain controllers. Dns misconfiguration in the domain for domain clients [Windows 2000/XP/2003] and/or domain controllers also is often the cause of such problems.

If you are using downlevel clients in the domain, netbios name resolution also needs to be correctly configured with domain controllers also being wins clients.

Did netdiag show a pass for everything on the domain controller?? The error below is significant. Find the computer account for the DC in AD Users and Computers and look in properties and make sure "trust computer for delegation" is checked which domain controllers should be.

I don't know if the domain controller needs to be restarted after enabling for delegation. If the error in dcdiag persists it would be a good idea to restart it if it will not cause too much disruption. Also see if there are any pertinent events in Event Viewer on the domain controller that may be helpful.

I have a domain controller, but the SW is not install on it. My SW are install in other server 2003, not being a DC. In this server that SW are install, i ping the workstations, and i think that workstations pinging me, because they responde to me. So, i think the tools that you told me not going to help me because i'm not in DC computer, but thanks in the same.

Before I post my doubts, I had already seen this but your comment was a step that I do not understand:

" Select the Group Policy Object for which you want to enable RPC ( Normally this will be the "Default Domain Policy", but if you already have other Group Policy Objects enabled for your networks, select the appropriate one ) "

I not found the Group Policy Object =\ ..

Another question. Can you make this mistake because of the computer in question has never logged in as administrator? I not sure, but I think there are some computer on my network that have never been certified as administrators.

Finally, I had to do some more problems and did an update to the DNS server, because I think they were a few names which have no longer existed.

I think that is not necessary, in my situation, define the GPO, because they are already set to default. But however, the machine that gave me a error i sure that the settings of GPO were correct.

Also verify that the other settings were also correct, and everything seemed fine. But the error still.
However, when I did a scan only the machine in question, with the same administrator account, it was no error and we got the information that i need.
Thus to resolve all other errors, but I can not understand why = \.

Someone explain me?

Example:
If I do a scan the network with the user administrator of some computers give error. The computers with these errors, if I do a single scan with the same account, the error is disappeared!

Another question. There is some reason to the command "netsh firewall set service remoteadmin enable" no longer work and have to enter again?

Again, thanks for the help. For now I have the problem solved :D

Hasta

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.