DHCP Server Errors 1007, 1008, 7023 & DNS Server Errors 407, 408

ID: Q200462

The information in this article applies to:

Microsoft Windows NT Server version 4.0
Microsoft Proxy Server version 2.0

SYMPTOMS

THE DHCP Server service or the DNS Server service will not start. The following events are logged in the system event viewer.

NOTE: You may see only one set of errors (either DHCP or DNS related errors), depending on the services installed.

DHCP Server Service Related Errors

Event ID: 1007
Source: DhcpServer
Description: The DHCP server failed to initialize Winsock data.
The following error occured: [No further data is available]

Event ID: 1008
Source: DhcpServer
Description: The DHCP server is shutting down due to the following error:
[No further data is available]

Event ID: 7023
Source: Service Control Manager
Description: The Microsoft DHCP Server service terminated with the following error:
[No further data is available]

When you start the DHCP server using the Services utility in Control Panel, the following error is received:

Error 2140: An internal Windows NT error has occurred.

When you do a net start dhcpserver from a command prompt, the following error is received:

System Error 10050 has occurred.
The system could not find message for message number 0x2742 in message file for BASE.

DNS Server Service Related Errors

DNS server service will start but the following events are logged in the system event viewer:

Event ID: 407
Source: DNS
Description: DNS server could not bind a datagram (UDP) socket to [IP address of server].
The data is the error.

Event ID: 408
Source: DNS
Description: DNS Server could not open socket for address [IP address of server]. Verify that this is a valid IP address on this machine. 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.

CAUSE

The DHCP/DNS server is also a Winsock Proxy Client and the DHCP/DNS server IP address has not been included in the Proxy Server's Local address table (LAT). You can verify this exclusion by looking at the Msplat.txt in the Proxy Client subdirectory (typically, c:\Mspclnt\Msplat.txt) on the DHCP/DNS server.

RESOLUTION

To resolve this problem, do one of the following:

Include or add the DHCP/DNS server IP address in the Proxy Server's LAT.

Change the DHCP/DNS server IP address to an address that is included in the Proxy Server's LAT.

Disable Winsock Proxy Client on the DHCP/DNS server (in Control Panel, double-click WSP Client, and then click to clear the Enable WinSock Proxy Client check box ).


Keywords          : kberrmsg kbnetwork 
Version           : winnt:2.0,4.0
Platform          : winnt 
Issue type        : kbprb

Last Reviewed: February 27, 1999