• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3458
  • Last Modified:

DNS Client Service Failing to Start - Missing Dependencies

Windows Server 2003 SP2 - The DNS Client Service does not start up upon starting the server. When attempting to start it manually I receive this error:

Could not start the DNS Client service on Local Computer.
Error 1075: The dependency service does not exist or has been marked for deletion.

The event viewer posts this error in the system log each time I try to start the service:

The DNS Client service depends on the following nonexistent service: ALGS

Actions taken in an attempt to correct:
We have reset the IP Stack using net sh int command - http://support.microsoft.com/kb/299357

Notes
There is no ALGS (Application Layer Gateway Service listed in services at all. But there is one on our other servers.
When viewing the properties of the DNS Client Service there are no dependencies listed. On all of our other servers, there is a tree starting with "TCP/IP Protocol Driver" with a child item called "IPSec Driver"

We aren't sure how the ALGS Service was removed or why its related to DNS Client Service, but if there was some way we could "resinstall" the DNS Client Service or ALGS Service to get them back into working order than we'd be willing to reset it back to however it was before.

Any help is appreciated. Thanks in advance.
0
mmahelpdesk
Asked:
mmahelpdesk
  • 3
1 Solution
 
kaskhedikar_tusharCommented:
Hello,

Have you configure properly  the DNS server ?

Check the forward & reverse lookup zones. Also check the host a records in reverse lookup zones.

http://support.microsoft.com/kb/814591

http://www.windowsreference.com/dns/how-to-create-dns-reverse-lookup-zone-in-windows-server-2003/

Regards,
Tushar Kaskhedikar  
0
 
mmahelpdeskAuthor Commented:
Configuring DNS would require that the DNS Client Service could start in the first place. I'm assuming your reply was a very generic response that you give most tickets.

We managed to figure out the issue int the wee hours of the night.

As it turns out, there were a number of different services that all had newly created dependencies. The name of the dependency, found in the registry (not through the properties of the service) was called "ALGS". It was on the Print Spooler, DNS Client, COM+, and Messenger. We know ALG is the Application Layer Gateway Service. I managed to export that whole ALG Key found under HKLM_system_current*_services from another machine and run the created .reg on the fault machine to import all of the ALG components. Afterwards, we checked a working machine for the correct dependencies for all of the services where ALGS was and replaced ALGS with the proper dependencies. After that the services started up right away.
0
 
mmahelpdeskAuthor Commented:
Best possible solution.
0
 
mmahelpdeskAuthor Commented:
Best possible solution.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Worried about phishing attacks?

90% of attacks start with a phish. It’s critical that IT admins and MSSPs have the right security in place to protect their end users from these phishing attacks. Check out our latest feature brief for tips and tricks to keep your employees off a hackers line!

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now