TCP/IP Services Aplication encountered a problem and needed to close
This is on our domain controller that is also are DHCP server. Its windows 2003 server SP2. Power was cycled several times due to the utility company, and somehow caused this.
I have tried the netsh int ip reset resetlog.txt command but that didn't work.
I read a lot of people recommending to run "configure email and internet connection wizard" ,but I cant seem to find it to try it out.
I can't start my DHCP server, but I think this issue is related to the TCP/IP services.
Any help appreciated.
Thanks!
I have tried the netsh int ip reset resetlog.txt command but that didn't work.
I read a lot of people recommending to run "configure email and internet connection wizard" ,but I cant seem to find it to try it out.
I can't start my DHCP server, but I think this issue is related to the TCP/IP services.
Any help appreciated.
Thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
> encountered a problem and needed to close
to identify the actual problem and address the reason we need to check the logs and original error message giving the problem. are they available?
to identify the actual problem and address the reason we need to check the logs and original error message giving the problem. are they available?
ASKER
I did the KB article and the same error came up. Still can't load the DHCP server.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
bbao yes I have the logs The first events I see regarding DHCP was event 1008, 1018 and 1014, also service control manager even 7031 and
ASKER
Pnutbutteradmin,
I found that article, and I had tried to find the wizard they speak of, but I don't think it exists on sever 2003. I think its only available on the small business version.
Tom
I found that article, and I had tried to find the wizard they speak of, but I don't think it exists on sever 2003. I think its only available on the small business version.
Tom
ASKER
I was able to get DHCP backup and working. I had to restore the dhcp.mdb file. So everything is back up and working, but I still get the error every time I reboot.
1. Try to change the dhcp service start mode to delayed start.
2. Go to C:\ProgramData\Microsoft\W
open it with notepad and see any crash application is mentioned.
2. Go to C:\ProgramData\Microsoft\W
open it with notepad and see any crash application is mentioned.
ASKER
I don't have a folder named programData, and I don't have any files named report.wer on my computer.
any error logs in event ?
check the dependency of DHCP service and see those are at automatic startup.
check the dependency of DHCP service and see those are at automatic startup.
ASKER
The only DHCP event is se is event id 1056
No, its just warning and its good, nothing wrong with this log.
are you using symentic anti virus ?
ASKER
No McAfee Enterprise
Any error log in system logs ?
run DCDIAG /V and share the result if any thing wrong.
run DCDIAG /V and share the result if any thing wrong.
ASKER
The only error I see in the system logs since the last reboot was 7026, and that's because I updated the network card drivers as someone suggested above.
The dcdiag /v passed all but one test, and that was for failing a sysvol replication failure in the last 24 hours.
The dcdiag /v passed all but one test, and that was for failing a sysvol replication failure in the last 24 hours.
humm
Total how many DC you have ?
check for replication related error ?
Total how many DC you have ?
check for replication related error ?
ASKER
Just one dc. The error is because it syncs with a remote dc. I am concerned about the error on boot up. Any ideas what causes that?
Do not worry about that error, you can check and update that file/driver. http://social.technet.microsoft.com/wiki/contents/articles/13469.event-id-7026-the-following-boot-start-or-system-start-driver-s-failed-to-load.aspx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Its working although the error still appears after every reboot.
ASKER
I did the NIC driver and that didn't fix it. I am following the steps in the KB article now.