I am setting up DHCP on a Windows NT Server SP6 machine. This system is the PDC for my ADMIN domain. I had DHCP setup once before, however one day it just stopped working. I checked the services and the DHCP client service was not started. When I try to start it I get the following error: " Could not start the DHCP Client Service on \\servername. Error 2140: An internal Windows NT error occurred. " Any help would be greatly appreciated. TIA

It was working but the log stated the DHCP service wasn't started? HMMM! If this is a small network, configure your addresses manually. DHCP is much more complex than just turning on the service. If you use DHCP servers, you must use WINS servers so that the dynamic IP addressing of DHCP clients can be dynamically updated in name- to- IP- address mappings.

This is no small Network. I run 250 Client machines not counting ADMIN staff. We have 2 domains one for our agents which is an internal sub domain, and another for administrative staff. Our WAN connects to 5 other offices arounf the US. When I set up DHCP for our administrative side of the network I know that service was running. I also know that in order to get DHCP working that service must start. My queastion was more aong the lines of how to check what is causeing that error and get DHCP started again. I know how to use DHCP and how to set it up. Both in Windows NT and 2K. I am now looking at setting up Linux to run DHCP. However haveing it on my Domain Controller would work the best for administering DHCP. Thanks.

Foud this on the subject, Hope it helps! PROBLEM The following error occurs when trying to start DHCP client in Windows NT services Could not start the dhcp client on//file server error 2140:internal windows, nt error occurred. SYMPTOM Could not start the dhcp client on//file server error 2140:internal windows, nt error occurred. An IP conflict occurs between the DHCP manager range of 10.100.100.100 to 10.100.100.255, and the static IP address of the server 10.100.100.100. SOLUTION Delete and re-creating the scope. Check user manager for domains and ensure that the user has the permissions to logon remotely. If the problem also occurres when logging on as a user, ensure that the primary logon is Microsoft Client and the domain name is correct. Ensure TCP/IP is set to obtain an IP address, file and print sharing is enabled. Ensure that the user is not disabled and that logon occurs without any problems. Well its worth a try.