By the way, computer name is "Pasha" and domain name is "experimental.net"
Before, when I setup DNS and AD on a 2003 server, both the "Server:" and the "Name:" section read the same information--computername.servername.net. I suspected that something was wrong. I then ran Active Directory Users and Computers, and received the following error:
Naming information cannot be located because:
The server is not operational.
Contact your system administrator to verify that your domain is properly configured and is currently online.
I looked up the error on Google and it says that TCP/IP filtering may be blocking LDAP traffic, but I verified that all the TCP/IP filters settings were set to "Permit All."
Should I first setup DNS then run DCPROMO, or the other way around?
I used this site (
) to assist me in setting up DNS and AD, but the site isn’t well organized and so I must have either skipped something, or added something that shouldn’t have been added. I’ve tried demoting the server, uninstalling DNS and running them again several times, but neither time am I able to get it working properly.
I ask for your assistance in helping me resolve this issue.
Thanks for your time,
Re: DNS or AD problem?
11 years 3 months ago #21617
Ok. I uninstalled DNS and then demoted the server. I then started over, this time I ran DCPROMO and allowed it to config DNS for me. In the end, I ran nslookup and got a worse looking message then what I started with....so I went into DNS and setup the forward and reverse lookup zones, in the end, the nslookup result looked the same as yesterday and when I would try to access AD Users and Computers.....I would receive the same error.....then I looked in event viewer and saw a suggestion of "restart DNS," so I went into DNS and stopped it, then started it, I was then able to pull Users and Computers with no error.
I'm still not sure if the problem is resolved, and I'd hate to imagine that just because no error shows up, that DNS is working fine....only to find out later that internally, the DNS is screwed up.
The result of running nslookup shows the following