Server 2003 Small Business Problem

The hard drive crashed in my client's server and they did not have a backup. I installed a new hard drive and the operating system. I then configured DHCP on the server and disabled it on the router. After downloading SP2 the server bogged down and there were several instances of something like hlms.exe or something like that in task manager. The client rebooted the server and then could not log on even in safe mode so we did a repair install of Server 2003. I am at the point where it asks to configure DHCP. My question is, what will happen to the settings in the router? Will the DHCP simply be disabled and all other settings remain intact?

Thank you!

Robert
Robert EhingerIT specialistAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Thomas GrassiSystems AdministratorCommented:
Configuring DHCP on Windows 2003 server is ok you do not have to enable it right away.

Check your router to make sure the DHCP server is not running

Having two on the network can cause many issues.

Once you know the router is not running dhcp then you can activate dhcp on this server

Was this server a DC or member server?

What type of router is this?
0
Robert EhingerIT specialistAuthor Commented:
The server is a DC.

The router is a Linksys - not sure the model. I am not at the server right now.

The message I got that I am referring to says that a DHCP server has been found and that we can't have 2. Do I want the server to be configured for DHCP? So I am assuming it has found that the router is currently the DHCP server.
0
Thomas GrassiSystems AdministratorCommented:
I would bypass the DHCP setup at this time.

First get your DC server up and running DNS and everything else.

Once you have a stable network then you can add the DHCP role to the server.

This way you will not have to many issues at this time.

A side note is that you should have a second DC it can be a very low end computer
I ran on a 4 gb desktop for many years.
The DC does not need much fire power

A Backup DC will save you tons of work if one crashes in the future.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

Robert EhingerIT specialistAuthor Commented:
So here is what happened and the problem I now have. The message told me to disable DHCP in the router, which I did. Windows then configured DHCP on the server. Once all the settings and such were installed and configured I verified an internet connection. Then I went to one of the client computers that was in the WORKGROUP workgroup. I was able to join it to the domain and access network resources. I then went to another client computer and put it in the WORKGROUP workgroup rebooted and then tried to join it to the domain. I was unable to do so and I am attacting screen shots of the error. Please advise as we need to get this network back up and running so we can get back to selling cars.

Thank you!

Robert
untitled.JPG
untitled2.JPG
0
Robert EhingerIT specialistAuthor Commented:
Oh, yeah, the clients are all Windows XP SP3.
0
Thomas GrassiSystems AdministratorCommented:
Make sure DNS is running on the server

must be for AD


Run this


netdiag >>dclogx.txt

echo "Starting DCDiag on SERVERNAME" >>c:\util\dclogx.txt
dcdiag >>dclogx.txt
dcdiag /test:registerindns /dnsdomain:FQDN>>dclogx.txt
dcdiag /c /v >>dclogx.txt
dcdiag /test:dns >>dclogx.txt
0
Robert EhingerIT specialistAuthor Commented:
OK, a couple of questions -

Why would the first client join the domain if DNS was an issue?

The Server has Windows Server 2003 SP1. Isn't dcdiag NOT included in this O/S?
0
Thomas GrassiSystems AdministratorCommented:
Seen where XP computers have issues joining the domain are they have been on the domain.

The sid on the XP computer can be out of sync.

Try making the computer a work group computer then after that restart and then try to join the domain

dcdiag here

http://technet.microsoft.com/en-us/library/cc776854(v=WS.10).aspx

download here

http://www.microsoft.com/en-us/download/details.aspx?id=15326

Get server up to service pack 2 before you try this
0
Robert EhingerIT specialistAuthor Commented:
I had already put the client in a workgroup and then tried joining it to the domain.
0
Thomas GrassiSystems AdministratorCommented:
Well lets get the server up to date with all fixes and service packs
0
Robert EhingerIT specialistAuthor Commented:
Here is the text file os DCDIAG
dcdiag.txt
0
Thomas GrassiSystems AdministratorCommented:
Ok see one error so far.


 Starting test: Services
            IsmServ Service is stopped on [HHNISWANDERSERV]
         ......................... HHNISWANDERSERV failed test Services

Check the Intersite Messaging service make sure it is set to automatic.
start the service and rerun the dcdiag.


Also run the rest of the script I posted need to make sure the DC is working ok.


@echo off
netdiag >dclogx.txt

echo "Starting DCDiag on SERVERNAME" >>dclogx.txt
dcdiag >>dclogx.txt
dcdiag /test:registerindns /dnsdomain:FQDN>>dclogx.txt
dcdiag /c /v >>dclogx.txt
dcdiag /test:dns >>dclogx.txt

Exit
0
Robert EhingerIT specialistAuthor Commented:
I brought in my laptop this morning and was able to raise it to the domain with no problem. I will run that script as soon as SP2 is done loading.
0
Thomas GrassiSystems AdministratorCommented:
Ok great keep us posted.
0
Robert EhingerIT specialistAuthor Commented:
SP2 is installed.

I am running that script now. How long should it take?

I put another of the clients that had been on the domain before the server crash in the workgroup and then tried to join the domain but it failed with the same error.
0
Thomas GrassiSystems AdministratorCommented:
script should not take long only a few minutes.

What is the error on the domain join?
0
Robert EhingerIT specialistAuthor Commented:
ran the script and didn't see any errors but just had a blinking cursor. I hit the enter key and it returned the fILE replication file that I am attaching. It was workstation 4 that I was trying to join to the domain. I also ran dcdiag and I am also sending that to you.
filerep.txt
0
Robert EhingerIT specialistAuthor Commented:
dcdiag
dcdiag2.txt
0
Thomas GrassiSystems AdministratorCommented:
What is workstation04 ?

This computer is not a DC should not be referenced in the dcdiag.

The "0x0000165B and 0x000016AD" Event ID appeared for a computer account(s) that had been disabled for some time before it was re-enabled. It had probably become invalid.

Resolution: Disable the Windows XP Firewall. Remove and re-join the computer to the domain. Consider deleting the computer object in Active Directory users and computers in-between to delete any sub-components of the computer object.
0
Robert EhingerIT specialistAuthor Commented:
None of the computers that I sam trying to rejoin to the domain are in active directory. The firewall is off on both systems that I can't join.

The domain had the same name before the HDD replacement as it has now. When I go to change the name and domain I put the computer in WORKGROUP restart and then try to reejoin the domain.

The only computers that show up in AD are the two I have been able to join to the domain.
0
Thomas GrassiSystems AdministratorCommented:
Try this rename the computer name on one computer and see if the new name will join the domain.
0
Robert EhingerIT specialistAuthor Commented:
Nope. Same error.
0
Thomas GrassiSystems AdministratorCommented:
Are they getting the ip address from the dhcp server running on this new server?

Can you get me a screen shot of the error trying to join ?

I know you know how to do this but this article might help

http://www.windowsnetworking.com/articles-tutorials/windows-xp/wxpjoind.html
0
Robert EhingerIT specialistAuthor Commented:
OK. I may have found the problem. While the systems were getting IP addresses through the server via DHCP someone had set up DNS servers on the local computers. Once I got rid of those and set it to get DNS automatically then I was able to join the domain.
0
Thomas GrassiSystems AdministratorCommented:
Right you need to setup the dhcp server scope to but the dns entries so that when the get the ip address the router and dns servers will be there.

I thought I asked for a ipconfig /all before we could have seen that
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.