Avatar of nikhil61107
nikhil61107Flag for United States of America

asked on 

Login Delay and Browsing Issues

I had a 2000 server that decided to crap out on us.  It was running 2000 with AD.  We have three servers on our network running AD.  Before I started, they had, supposely moved the roles from the old server, that is running 2000 AD to our new DC's.  

Since this server has failed and no longer on the network, we are having long login times and also have issues broswing our network.  Everything was running fine until the server decided to kick the bucket.

The question is....what you recommend I check to make sure every step had been taking to make the switch to the new DC's.  I have done some checkin, but nothing is sticking out.

If you need more information from me to help, please let me know.

Thanks in advance for your help.
Microsoft Server OSMicrosoft Legacy OS

Avatar of undefined
Last Comment
nikhil61107
Avatar of cdbeste
cdbeste

you need to run DCPROMO on
one of the systems to promote
it to the Primary Domain Controller

just do start|run
type cmd
hit enter
type DCPROMO
Avatar of cdbeste
cdbeste

Also check your IPCONFIG on your clients..  
If the old systems ip is in the DNS
this would cause problems as well..
Avatar of nikhil61107
nikhil61107
Flag of United States of America image

ASKER

DCPromo had been run on the new server.  The thing I can't reverify if it was run on the old server to demote it as a DC and designated as a File Server.  I called the consulstant that here before I started and he can't remember...figures.

We are running DCHP and the DNS is set correctly.

So if it was not demoted like it should have been, any advice to what I should do next.

Thanks,
ASKER CERTIFIED SOLUTION
Avatar of victornegri
victornegri

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of nikhil61107
nikhil61107
Flag of United States of America image

ASKER

I checked the FSMO and all the roles have been moved to the new server.  

I double checked our DHCP and all those settings are correct.  We are not using WINS.  

I checked DNS and it is listed as one of the servers.  If delete it from the list, will help or are there other steps to be taken to remove it.

I ran the dcdiag and it is still wanting to replicate with the old server.  Where do I remove that from happening.

Thanks again for you all your help so far.
Avatar of nikhil61107
nikhil61107
Flag of United States of America image

ASKER

One last question.....

We are not sure if the server will be able to be brought back to life, will know tomorrow, if so, should I wait to see if it does come back up or go ahead with the steps to remove it from AD.

Thanks again.
Avatar of victornegri
victornegri

Follow the steps above and remove it from AD. Don't even attempt to re-join it to the domain (or turn it on with it plugged into the network). Format and reinstall the OS and bring it up as a brand new server.
Avatar of nikhil61107
nikhil61107
Flag of United States of America image

ASKER

I would do that if we didn't have a couple of programs that we don't have any software to do a re-install.  It is an old program and nobody seems to know where the software is located.  I know where the data is, but not the software to re-install it onto a new server.  

So if I did connect to the network, just for those two program, i was going to run dcpromo on it and remove it that way.  Or is there something else you recommend besides wiping it clean, which i would love to do but can't at this moment.

Thanks again.....
SOLUTION
Avatar of victornegri
victornegri

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Avatar of victornegri
victornegri

Oh also, continuation of the last paragraph above. Remove it from the domain and join it to a workgroup while it's still connected to the dummy network. Then after you connect it back to the real network, join it back to the domain.
Avatar of nikhil61107
nikhil61107
Flag of United States of America image

ASKER

victornegri....thanks for you help....

I will try this tomorrow once our new memory arrives.
The FSMO roles were transferred cleanly.  The only thing that was not done was the dcpromo to demote it to a file server.  

Avatar of nikhil61107
nikhil61107
Flag of United States of America image

ASKER

The server has passed...I made the changes in DNS to remove the old server.  FSMO has been transfered cleanly, just some DNS steps that were not done correctly. That has done the trick to solve my login issues.  Also, I had found that someone that manually put in the DNS info instead of allowing DHCP to provide that information on about 20 or so computers which also caused some issues.



Thanks again for all you help.
Microsoft Server OS
Microsoft Server OS

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

59K
Questions
--
Followers
--
Top Experts
Get a personalized solution from industry experts
Ask the experts
Read over 600 more reviews

TRUSTED BY

IBM logoIntel logoMicrosoft logoUbisoft logoSAP logo
Qualcomm logoCitrix Systems logoWorkday logoErnst & Young logo
High performer badgeUsers love us badge
LinkedIn logoFacebook logoX logoInstagram logoTikTok logoYouTube logo