asked on

Can not start DNS Server Service

Hi,

I have a problem with an SBS 2003 machine. A few days ago the server restarted because of Windows Updates and when it restarted I received a message about some services not being able to start. I looked in Event Viewer and found an error saying that DNS could not start because there is not enough storage available. I found that the C drive had run out of space, so I freed up more than 3Gb of space. I then went back and tried to manually start the service but I receive the error below. I have also attached two further errors found in the DNS log.

Could not start the DNS server service on Local computer.
Error 14: Not enough storage is available to complete this operation

To workaround this I have had to add Hosts files to each PC but I need to find a long term solution, as I have no internet access on the server.

Event Type:	Error
Event Source:	DNS
Event Category:	None
Event ID:	407
Date:		14/07/2008
Time:		12:42:51
User:		N/A
Computer:	ALPHA
Description:
The DNS server could not bind a User Datagram Protocol (UDP) socket to 127.0.0.1. The event data is the error code. Restart the DNS server or reboot your computer.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 26 27 00 00               &'..    
 
 
Event Type:	Error
Event Source:	DNS
Event Category:	None
Event ID:	408
Date:		21/07/2008
Time:		15:36:51
User:		N/A
Computer:	ALPHA
Description:
The DNS server could not open socket for address 127.0.0.1. 
Verify that this is a valid IP address for the server computer.  If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces.  Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error.  In that case remove the DNS\Parmeters\ ListenAddress value in the services section of the registry and restart.) 
 
If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port. 
 
For more information, see "DNS server log reference" in the online Help.
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

Chris Dent

Silly question, but I'm going to ask it anyway.

You have rebooted again since making space, right?

Chris

TonyWalker821

ASKER

Yes :)

Chris Dent

hehe had to check, you know how it is :)

Can you use this to see if anything is listening on Port 53 at the moment?

netstat -an | FindStr 53

The DNS service normally listens on localhost like this:

TCP 127.0.0.1:53 *:*
UDP 127.0.0.1:53 *:*

You should also find similar entries for the other IP addresses on the system.

Finally, it's possible that a third party bit of software is trying to start up the service for a second time. That would cause an overlap as the port is already in use. You don't have anything to keep an eye on services with the server do you?

Chris

TonyWalker821

ASKER

I have
UDP 127.0.0.1:53 *.*
but no entry for TCP

Chris Dent

Okay, TCP is less important in this case. It's used for UDP overflow and zone transfers, not regular queries.

Is the DNS Service listed as Started at the moment?

Can you try:

nslookup
server 127.0.0.1
www.google.com

Just to see if it's actually responding on that?

Chris

ASKER CERTIFIED SOLUTION

TonyWalker821

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

SOLUTION

Chris Dent

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial