General discussion

Locked

DNS keeps failing to start

By Blackcurrant ·
Hi

My network comprises a single AD domain (domain_name.local). The domain comprises one file server (Win2k Server (SP4) with SBS 2K - minus Exchange Server) and 24 clients running Win 3.11 (1 machine-this does not have a computer account), Win98SE, Win2k Pro and WinXP Pro. Recently, we have been getting many DNS errors.

These become manifest when trying to change security settings on shared folders (both on the server and the clients), and the error message displayed is 'The network path was not found'. The server only has one application installed:
Arcserve 2000 backup utility.

The Server's DNS event log contains (after rebooting) the following error events in this order: 408, 407, 408, 407, and on and on. According to the event log description it is recommended that the DNS service is restarted and/or the computer is rebooted. When I restart the service a message states the DNS service could not be started because- 'Error 6: The handle is invalid'. Rebooting the server results in the same events being logged.

Also, the Application Event log contains repetitions of the following: Event 1000 Source Userenv: Windows cannot connect to domainname.local with (0x0) follwed by the same
event but with the description 'Windows cannot query for the list of Group Policy objects . A message that describes the reason for this was previously logged by this policy engine.'

I have tried deleting the listenaddress value as
recommended in one of the entries but this has *never* worked. In the past, I have solved this issue by uninstalling, then reinstalling the DNS server (twice). This has resulted in an error free event log and the domain has funtioned perfectly. However, this time this procedure has not worked. The only thing that has changed
is that about a month ago I ran Windows update and installed all the critical updates. However, the server funtioned fine after this had been done.

Does anyone have any suggestions that I might try?

This conversation is currently closed to new comments.

10 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by Blackcurrant In reply to DNS keeps failing to star ...

The application log also contains numerous errors: SimpTcp event ID 11 (lots of these); Event ID 7225 CheyDiscovery - Failed to bind to socket.
(EC=10042); ID 1008 Winlogon The enterprise root
certificate store could not be updated. (0x80070057) The parameter is incorrect. and ID 1009 The NT Smartcard authentication certificate store could not be updated. (0x80070057) The parameter is incorrect. and ID 1013 The automatic certificate enrollment subsystem could not access network resources needed for enrollment. Enrollment will not be performed. (0x80070057) The parameter is incorrect.

Collapse -

by voldar In reply to DNS keeps failing to star ...

For troubleshooting ur DNS u should do first thing: nslookup from a command prompt, to see what result u get. If, as u say, the DNS service is not starting, try to start it by using a command line: net start dns. Try then uninstalling the patches u last time installed. Hope also u have a backup of the system state. get into the safe mode - AD recovering - and restore it from the backup. For now this is all I can say to you. Hope that may help.

Collapse -

by Blackcurrant In reply to

Hi, thanks for answering. The problem was caused, I think, by internet connection sharing software (not the OS ICS). I had added a second DNS server address in the server's TCP/IP properties that allowed the Internet Connection program to use the software's DNS on the gateway to resolve addresses (the gateway is on a different machine, hence the need for a second address). Removing the second address and uninstalling the software, then rebooting, brought the machine back to full speed and the domain DNS server is now working fine.

I never realised that the domain's DNS server would fall over if a second address was added, after all it says 'use these DNS server addresses in this order' So why did it fail to find itself when trying to contact the first (its own) address??

Collapse -

by sgt_shultz In reply to DNS keeps failing to star ...

do you think a bad nic in the dns server would explain this?

Collapse -

by Blackcurrant In reply to

Hi, thanks for answering. The problem was caused, I think, by internet connection sharing software (not the OS ICS). I had added a second DNS server address in the server's TCP/IP properties that allowed the Internet Connection program to use the software's DNS on the gateway to resolve addresses (the gateway is on a different machine, hence the need for a second address). Removing the second address and uninstalling the software, then rebooting, brought the machine back to full speed and the domain DNS server is now working fine.

I never realised that the domain's DNS server would fall over if a second address was added, after all it says 'use these DNS server addresses in this order' So why did it fail to find itself when trying to contact the first (its own) address??

Collapse -

by kmcniff In reply to DNS keeps failing to star ...

Look at the following Microsoft articles:

http://support.microsoft.com/default.aspx?scid=kb;en-us;200462&Product=win2000

http://support.microsoft.com/default.aspx?scid=kb;en-us;279678&Product=win2000

Remember these are single lines with no spaces.

In short there could be a couple of things that have caused this:

Listen address for the DNS server
NAT being run on the same machine as DNS and the listen address set to all ports
DHCP and DNS on ths same machine with Winsock Proxy

Resd these and you will most likely find the root of your problem

Collapse -

by Blackcurrant In reply to

Hi, thanks for answering. The problem was caused, I think, by internet connection sharing software (not the OS ICS). I had added a second DNS server address in the server's TCP/IP properties that allowed the Internet Connection program to use the software's DNS on the gateway to resolve addresses (the gateway is on a different machine, hence the need for a second address). Removing the second address and uninstalling the software, then rebooting, brought the machine back to full speed and the domain DNS server is now working fine.

I never realised that the domain's DNS server would fall over if a second address was added, after all it says 'use these DNS server addresses in this order' So why did it fail to find itself when trying to contact the first (its own) address??

Collapse -

by w2ktechman In reply to DNS keeps failing to star ...

If none of those work, it may not be correctly added to the AD domain. Try to re-add the DNS server and then update the AD

Collapse -

by Blackcurrant In reply to

Hi, thanks for answering. The problem was caused, I think, by internet connection sharing software (not the OS ICS). I had added a second DNS server address in the server's TCP/IP properties that allowed the Internet Connection program to use the software's DNS on the gateway to resolve addresses (the gateway is on a different machine, hence the need for a second address). Removing the second address and uninstalling the software, then rebooting, brought the machine back to full speed and the domain DNS server is now working fine.

I never realised that the domain's DNS server would fall over if a second address was added, after all it says 'use these DNS server addresses in this order' So why did it fail to find itself when trying to contact the first (its own) address??

Collapse -

by Blackcurrant In reply to DNS keeps failing to star ...

This question was closed by the author

Back to Windows Forum
10 total posts (Page 1 of 1)  

Related Discussions

Related Forums