I have a brand new windows2003 server up and running with active directory and dns, with a new domain/forest/etc (the only 1 in our organization) called 'umapinc.com'. In a testing environment (i.e. this server and an identical one sitting right next to it on the same lan/subnet) I was able to add a second windows2003 server no problem. Unfortunately, neither of these servers will reside in this lan/subnet location, but are both slated to be installed in other offices. I tried adding the 2000 server that does belong in this office to the domain with both 2003 servers still next to me on the local lan, but it had multiple problems(some of which looked like it was pointing to 2003server #2 as the primary server, though I could be mistaken, but which of course would have been wrong - even though dns was set correctly to point to 2003server #1 as primary, and itself as secondary).
So, I tried removing the 2000 server from a.d., which repeatedly failed, saying something like it couldn't contact the primary server to remove itself, etc. I then had the same problem with the 2003server #2 when I tried to remove it. I would up removing the 2003server #2 using 'dcpromo /forceremoval', formatted and reinstalled the 2000server, since it isn't really a production server yet, and removed active directory altogether from the 2003server #1 (the 1st). I then removed DNS from #1 and reinstalled active directory, letting it configure dns along the way, again for the domain 'umapinc.com'. I now had to ship server#2 across the country to the office where I will install it, so I can't do anything with it. However, after finishing all configuration on #1, and recreating the A.D. environment of users, sites, ou's, etc., I went to configure DNS on the 2000 server, which it did successfully(or so it looked), but now when I run dcpromo on the 2000 server to try to add it as an additional d.c. for the existing domain 'umapinc.com', it comes up with the correct name for the 1st/primary controller (#1) in it's first steps, but when it gets to the 'creating the server object' step, it fails every time I try, stating 'the directory service failed to create the server object for (....this server....umapinc.com....on server #1.) Please ensure the network credentials provided have sufficient access to add a replica. "The RPC server is unavailable". over.....and over.....and over....no matter what I try *augh*!
I've made sure the userid and password I give it to use in dcpromo is a member of domain admins, schema admins, enterprise admins, and tried the checkbox for 'trust for account delegation' in the userid is turned on. I can ping #1.umapinc.com (the real name is umegis1.umapinc.com, but #1 makes this easier to follow), and nslookup returns the proper ip address for server and name. Furthermore, the rpcss service is running on both #1 and the 2000server. I've googled this to death and looked in Experts-Exchange at identical or nearly identical problems and tried their suggestions, which include the above tests. Still I can't get this going. I wonder in the back of my mind if #2 will have the same problem when I go to dcpromo it in a week when I'm travelling to our remote office to install it, but I have no idea at this point, because I don't know what the problem is. All I can see that is different from the initial successful test of A.D. is these:
1)Initially, I was working with 2 identical 2003 servers, #1 and #2
2)Initially, I was using the 2 servers on the same lan/subnet. Replication and everything was going smoothly.
Now, however, I'm trying to get the 2000server attached as a new d.c., not just an identical 2003server. Also, now #1 is in another office, connected to this office over vpn through Cisco routers and Cisco PIX, which otherwise has worked just fine for the past 6 years. I noticed in another post on this issue that the guy said something about the 2 servers being in 2 different offices and having problems, and then later he took the one server to the same office as the other, and something started happening, although it didn't fix everything. The things that make me dismiss the idea that the separate wan locations are the problem are: a)I k.n.o.w. active directory is supposed to work across wan vpn links, is it not? and b)the 2000server had problems from the get go, even though #1, #2, and 2000server were initially right next to each other, physically, and on the same lan.
Now, I have the next week to get this working smoothly with #1 and 2000server, while #2 is en route to our remote office. But come a week from Monday (5/23), I need this working smoothly so I can fire up #2 and add it as another d.c. to our umapinc.com domain. So, for now...HELP!! :-)
(and b.t.w. #1 and #2 are W2003 SP1, and 2000server is running SP4 and all are completely up to date with Windows Update)