Server Messed up

Guys i need an urgent help here.....

After uploading the new server by my senior the old one is not working, the old one was the PDC running AD, DNS and DHCP he run dcpromo on new one selected additional domain controller option AD got copied in the new one..... He took the old one out of network put the new one there and then remove the AD with dcpromo /forceremove and DNS and DHCP from the old one and re-instered it in the network...... Now this old system is not coming on the network i mean one can ping host from here but no one can access this computer...... Both running windows 2003....... I need this computer to be running as a client in the network as ther internal database is runnning on the computer.

WHen i try to join this computer on domain i get this message " A domain contorller for the domain abc.com could not be contacted. ENsure the domain name is type correctly."

Although i am writing the domain name correctly..... Need urgent help here guys.....

When i try to access this computer from other clients of even server i get the message " No network Provider accepted the given network path"

Normally, whenver I've had this issue, It was becuase of one of two reasons:

1. The specified DNS server was unavailable.
2. The network properties of the active NIC were incorrect.

I'm thinking just from experience and not searching the web.

Its purley something to do with the new server configuration i think when the AD and other things were copied into it.....something might have left behind during that operation and its making trouble....... WHen i look into the DNS and other entries it was showing that the old server is domain controller although the old one is not on network anymore and even the Dns and AD things has been wiped off from it....

NOw i would be interested to know if there are any tools and utilities available for repairing these issues. I have searched over the net and could not find such things.

Although the domain is there and DHCP too but the two things i have noticed in current setup are: -

1) NO new node can be join on this domain, i mean whenever i try to join a new computer i get the messege, the drectory services are unavailable sort of thing.
2) WHen i try to ping the server itself, the DNS resolve the IP of my DSL line, although it should return me the LAN IP not the router's IP.

Fanacool,
Have you changed the new server to be the Global Catalog? I think when you run dcpromo and add an additional domain controller, it assumes you want to keep the original server as the Global Catalog.

I didnot done it ..... Its my senior and i am sure he doesnot followed the procedures well and keeping old server as GC he might have missed it....... If this is what he has done, what are the steps to make the new server working smoothly or rather i would say perfectly, as I have mentioned its not let'ing any new Nodes on the network.

Fanacool,

Quote:

---

Demotions that are performed by using the dcpromo /forceremoval command leave FSMO roles in an invalid state until they are reassigned by an administrator.

---

In addition to tranferring the GC, Did your senior transfer the FSMO roles to the new server?

You might tell him he needs to transfer all the roles to the new server. I'm assuming you now only want one Domain Controller?
To transfer the FSMO roles, read this article.
To transfer the GC:

Quote:

---

Promote 2003 computer to a global catalog server. To do this, follow these steps:
a. Click Start, point to Administrative Tools, and then click Active Directory Sites and Services.
b. Expand Sites, expand Default-First-Site-Name, expand Servers, expand your SBS 2003 computer, right-click NTDS Settings, and then click Properties.
c. Click the General tab, click to select the Global catalog check box to assign the role of global catalog to this computer, and then click OK.
d. Restart the computer.

Note Wait for the account and the schema information to replicate to the new global catalog server. Wait for event 1119 or event 1869 to be logged in the Directory Services event log with a description that states that the computer is now advertising itself as a global catalog server.

---

I will try this and will let you know the results.
Thanks in advance.

ShagDevil

Event 1119 occured and its written there that the server is now global catalog server..... Now there is one more event coming contineously, i am attaching that log please refer it and let me know what it it?

Fanacool,
Ok, I noticed some anamolies here. For starters, it is important that
you are only running one domain controller. The reason being is that I told you to transfer all
roles to the one DC. This means, all FSMO roles and the GC should be on one DC. One of the FSMO
roles is the Domain Naming Master (which I'm not sure if that might the cause of your Event ID 1925).
If you only have one DC, all the roles should be placed on that DC. If you have multiple DC's, then
it is recommended that you place the GC, Schema master and the Domain Naming master on one DC and the Infrastructure master, RID master and PDC emulator should be on a different DC. If you haven't transfered the FSMO's to your DC, I suggest you do that (from the link I provided above). Just changin the GC won't suffice.
Again, I'm assuming you are only using one DC. Let me know how this goes.

Well let me tell you few things again..... there was and old sever say suppose OLDSRV and it has all the AD and DNS things in it..... the new server NEWSRV was deployed using additional domain controller and soon after AD got copied and DNS settings in it, OLDSRV was taken out from the network, dcpromo and everything wipe out from it and the only server on the network is NEWSRV.

I have made this new server Global catalog and manually deleted all the entries of the previous server...... Now i just opened the AD sites and directory and expanding the deafil-first-sites and then servers i saw 2 old servers there too.

On the NDTS replicaiton its saying in the log that unable to find FSMO role the current FSMO owner not found.

So what should i do now? i mean how can i delete the old entries of the server as they are no longer on the network.

Evidently your senior does not follow a task checklist when doing something as important as a depromotion/promotion of a DC. (we all make mistakes)

Let's assume you set the new Domain Controllers TCP/IP DNS settings to look at ITSELF. You did do this, didn't you? Go check it in the NIC settings.

(I'll also assume since the promotion, that you've rebooted the machine once or twice.)

First run Netdiag at the command line. Copy and paste the results to notepad and see if anything needs correction.

If all is well,

Then run DCdiag at the command line. Copy and paste..........

You know the drill.

Edit: Here's a specific FSMO command: DCdiag /test:Knowsofroleholders /v

Also find out more FSMO here: FSMO Role finding

Forgot to answer your "how do I delete old AD info on new DC"

Too much to type, just go here: Cleanup old AD info in new DC

(wonder why your senior forcefully removed the old DC?? **puzzled**)

Fanacool,
I'm going to agree with ZT3000 in that your senior should have planned this better.
Your current situation: OLDSRV removed, NEWSRV added via Dcpromo as an Additonal Domain Controller (AD & DNS copied over). Now you're getting error messages (understandably) because the OLDSRV was removed before the FSMO roles were transferred. Now you have a GC on the NEWSRV but no FSMO roles.
What should have happened: NEWSRV should have been added via Dcpromo, GC & FSMO roles should have been transferred to NEWSRV, then OLDSRV should have been removed.

I'm going to have to check into this some more. I'm at work right now so I won't be able to give you any in-depth anwers as of yet. Try a few suggestions ZT3000 has mentioned. I'm not entirely sure if seizing the FSMO roles will work at this point. Talk soon.

Fanacool,
Ok. Did some research. Seems that if you didn't transfer the FSMO roles to the new server before taking the old server offline, you'll have to seize the FSMO roles rather than transfer them.

Quote:

---

You can transfer all five FSMO roles through the MMC tool in Windows 2000. In order for a transfer to work both computers must be available on-line. If a computer no longer exists, then the role must be seized. To seize a role, you must use a utility called Ntdsutil

---

From this article. (I'm assuming this is also true for Windows 2003 Servers).
You can read how to seize the FSMO roles here

Hi guyz

Ok I got busy in another project and didn't got time to take a look at the issue...... Now i have tried every possible option i can on this but still the problems remains there...... Ok when i go to sieze the FSMO roles..... or simply use the ntdsutil when i try to connect to the server or hte domain i get the error message 80070057 parsing input - illegal syntax?

So i am unable to proceed further......

Please help here...... i am begining to loose hope :(

My mistake here ..... i was writing the syntax wrong...... was able to connect to the domain controller and sieze the role. I will let you know the results later

Hey things are back to normal again..... although there is one issue but the main one is resolved and now i can see the server as PDC, Schema Master e.t.c. User's account can be created in AD and new computers can also now be join on the domain.

Its been really a learning experience for me........ Thanks to all of you..... Specaially Shag Devil :thumbsup:

GOD Bless You All.

Fanacool,
No problem buddy. Glad to hear you resolved all your issues. Sorry it took me so long to reply. been quite busy on my own network. Go figure. The same week I was talking to you, the server on my network crashed (hardrive got corrupted) and we suffered some major issues. Not only that but, it happened during the middle of the work day when everyone was depending on the network. In a nut shell, we basically transferred everything to our new server, re-configured every client and basically got 46 ulcers in the process. It was an IT's guys worst nightmare.
Not taking any chances this time. Now we got two brand new servers with redundancy, and are using the nifty new DFS features in Windows 2003 Server. File replication, domain based file shares so that if one server goes down, people can still work on their files on the other server.
joygasm.
Fanacool, trust me. If you don't want to go clinically insane, I highly recommend your senior purchases another server and set up redundancy. You don't ever want to go thorugh what I did. In any event, good luck.

Luckily there is a budget of another server for us here, but at the moment Managment willl not go for it......I do have an internal server dunning the Database (SQL) being accessed only internally, Its running Windows 2000 advanced server so I need to switch it to Windows 2003 in order to avail that Distributed File System.