Hey guys, just looking for some help on a DHCP server crash! So I have a small home domain with a computer acting as a DHCP, DNS, AD DC and Print Server. In the past 2 weeks the DHCP server has failed twice. By failed, I mean that I have woken up of a morning and none of my internet based devices (iPhone, iPad, Laptop, PC) are able to connect to the internet until I restart the DHCP server. I have not logged onto the DHCP server while it was not issueing IP's as the server does not have a keyboard and mouse, obviously I could not remote login as I did not have a IP address. I have looked in the logfile (windir/system32/dhcp/TUE. as detailed below: 06/10,03:08:48,Database Cleanup Begin,,,, 30,07/06/10,03:08:48,DNS Update Request,4.0.168.192,File_Server_Test.bellevueroad.local,, 30,07/06/10,03:08:48,DNS Update Request,6.0.168.192,AD_Replication.bellevueroad.local,, 30,07/06/10,03:08:48,DNS Update Request,8.0.168.192,WIN-A61QP98SRSH,, 30,07/06/10,03:08:48,DNS Update Request,9.0.168.192,Win7_Test.bellevueroad.local,, 30,07/06/10,03:08:48,DNS Update Request,25.0.168.192,front_room_two.bellevueroad.local,, 30,07/06/10,03:08:48,DNS Update Request,50.0.168.192,Becky-PC.bellevueroad.local,, 30,07/06/10,03:08:48,DNS Update Request,51.0.168.192,Nexus-PC.bellevueroad.local,, 25,07/06/10,03:08:48,0 leases expired and 0 leases deleted,,,, 25,07/06/10,03:08:48,0 leases expired and 0 leases deleted,,,, 11,07/06/10,03:08:53,Renew,192.168.0.5,Xavier,C42C03D164B7, 11,07/06/10,03:17:29,Renew,192.168.0.7,Pachelbel,9027E437CE16, 31,07/06/10,03:25:36,DNS Update Failed,192.168.0.4,File_Server_Test.bellevueroad.local,-1, 31,07/06/10,03:26:11,DNS Update Failed,192.168.0.6,AD_Replication.bellevueroad.local,-1, 31,07/06/10,03:26:46,DNS Update Failed,192.168.0.8,WIN-A61QP98SRSH,-1, 31,07/06/10,03:27:21,DNS Update Failed,192.168.0.9,Win7_Test.bellevueroad.local,-1, 31,07/06/10,03:27:56,DNS Update Failed,192.168.0.25,front_room_two.bellevueroad.local,-1, 31,07/06/10,03:28:31,DNS Update Failed,192.168.0.50,Becky-PC.bellevueroad.local,-1, 31,07/06/10,03:29:06,DNS Update Failed,192.168.0.51,Nexus-PC.bellevueroad.local,-1, 11,07/06/10,03:37:38,Renew,192.168.0.5,Xavier,C42C03D164B7, 11,07/06/10,03:44:19,Renew,192.168.0.7,Pachelbel,9027E437CE16, 11,07/06/10,03:44:31,Renew,192.168.0.7,Pachelbel,9027E437CE16, 00,07/06/10,17:11:53,Started,,,, 50,07/06/10,17:12:29,Unreachable Domain,,bellevueroad.local,8250, 55,07/06/10,17:12:29,Authorized(servicing),,bellevueroad.local,, 50,07/06/10,17:12:53,Unreachable Domain,,bellevueroad.local,8250, 11,07/06/10,17:14:39,Renew,192.168.0.5,Xavier,C42C03D164B7, 11,07/06/10,17:15:22,Renew,192.168.0.7,Pachelbel,9027E437CE16, 11,07/06/10,17:24:04,Renew,192.168.0.7,Pachelbel,9027E437CE16, 11,07/06/10,17:25:33,Renew,192.168.0.7,Pachelbel,9027E437CE16, 11,07/06/10,17:35:40,Renew,192.168.0.7,Pachelbel,9027E437CE16, 11,07/06/10,17:38:59,Renew,192.168.0.7,Pachelbel,9027E437CE16, 11,07/06/10,17:44:14,Renew,192.168.0.5,Xavier,C42C03D164B7, as you can see at 3:44 it failed, and wasnt restarted until I reset the machine at 17:12. I am grateful of any troubleshooting tips. In addition, I am finding my WSUS clients not reporting to WSUS regularly unless I do ipconfig /fllushdns combined with the wuauclt/reportnow commands. I have no idea if these problems are related. Others I have explained this issue to have mentioned reverse lookup zones, does anyone have any thoughts? Thanks so much guys, as I'm getting more advanced, more advanced problems keep cropping up!

Can you post unedited ipconfig /all from both server and client? Regards, Dave Patrick .... Microsoft Certified Professional -Microsoft MVP [Windows]

0,07/06/10,03:08:48,DNS Update Request,4.0.168.192,File_Server_Test.bellevueroad.local,, 31,07/06/10,03:25:36,DNS Update Failed,192.168.0.4,File_Server_Test.bellevueroad.local,-1, 11,07/06/10,03:37:38,Renew,192.168.0.5,Xavier,C42C03D164B7, Where is the DHCP failure? I'm seeing a 30-Minute life interval for the DHCP renewals. 31,07/06/10,03:25:36,DNS Update Failed,192.168.0.4,File_Server_Test.bellevueroad.local,-1, That is a DNS failure, are you using a combination of Home PCs with PCs using Pro, added to the domain? If that is the case, you may need to disable "Secured Updates only" for your Dynamic DNS Settings in your DNS Console by right clicking the domain bellevueroad.local and opening properties. As far as Reverse Lookups, they can have a little issue with nameserver lookups but not too bad. It definately helps to have a reverse zone but it's not required... however, in your scenario... I have seen some strange behavior similar for a system running all in one. I have reverse lookup and have no problems with DHCP. It could be causing your DHCP Server to stop manually by failing to update DNS. I just posted a reverse DNS Setup recently. 1) Configure DNS a) Open the DNS console from "Administrative Tools" under the start menu i) Right Click on the Server (next down from “DNS” with the dns icon) (1) Open Properties from the menu ii) Click on the “Forwarders” Tab and enter your ISP’s DNS Information there. (1) Your ISP information is displayed on your Routers “Gateway” configuration page that displays your public IP and miscellaneous other information about your WAN Link. (2) Click OK to finish after entering your ISP DNS information. This will redirect traffic for domain names that your server is not familiar with. Obviously “google.com” is not going to be “Known” by your DNS until it queries the internet DNS servers via your ISP. b) Now you need to configure the Reverse Lookup Zone. i) Right click on “Reverse Lookup Zone” and select “New Zone” (1) Create a Primary Zone (Your Server is authoritative for Primary Zone) (a) Select the default Zone Replication Scope since it seems like a single LAB domain. (b) IPv4 Reverse Lookup Zone(after you’ve completed updates it may offer IPv6) (c) Enter your IP Network ID, example 192.168.3.6 – This makes your Network ID 192.168.3 ii) Once you’ve created your zone, add a ptr record to your server. (1) Right Click on your new “Reverse Lookup Zone” in the Reverse Lookup Zone folder and select “New Pointer(PTR)…” (a) Enter the IP address for your Server (b) Click on “Browse” (i) Double click on your Server Name (domain controller) (ii) Double click on Forward Lookup Zone (iii) Double click on your Domain Name (iv) Select your server’s host record that was automatically created c) Finish your DNS configuration by updating your IP Address information. i) Start> Run> NCPA.CPL (I’m lazy and this is the fastest way to pull it up) (1) Double click on your Ethernet controller (2) Open properties (3) Click on “Internet Protocol Version 4 (TCP/IP) (a) If you did not reconfigure this Post installation of AD, you might notice it set itself to the loop back address 127.0.0.1 – Change this back to the IP of the Server. Here's the directions I posted there. I hope they help. Follow these directions, best of luck!! Steve Kline - MCITP: Server Administrator All answers are posted, "As Is" with no warranties or guarantees implied. http://www.itjournal-stevekline.com - Content coming soon.

0,07/06/10,03:08:48,DNS Update Request,4.0.168.192,File_Server_Test.bellevueroad.local,, 31,07/06/10,03:25:36,DNS Update Failed,192.168.0.4,File_Server_Test.bellevueroad.local,-1, 11,07/06/10,03:37:38,Renew,192.168.0.5,Xavier,C42C03D164B7, Where is the DHCP failure? I'm seeing a 30-Minute life interval for the DHCP renewals. 31,07/06/10,03:25:36,DNS Update Failed ,192.168.0.4,File_Server_Test.bellevueroad.local,-1, That is a DNS failure, are you using a combination of Home PCs with PCs using Pro, added to the domain? If that is the case, you may need to disable "Secured Updates only" for your Dynamic DNS Settings in your DNS Console by right clicking the domain bellevueroad.local and opening properties. As far as Reverse Lookups, they can have a little issue with nameserver lookups but not too bad. It definately helps to have a reverse zone but it's not required... however, in your scenario... I have seen some strange behavior similar for a system running all in one. I have reverse lookup and have no problems with DHCP. It could be causing your DHCP Server to stop manually by failing to update DNS. I just posted a reverse DNS Setup recently. 1) Configure DNS a) Open the DNS console from "Administrative Tools" under the start menu i) Right Click on the Server (next down from “DNS” with the dns icon) (1) Open Properties from the menu ii) Click on the “Forwarders” Tab and enter your ISP’s DNS Information there. (1) Your ISP information is displayed on your Routers “Gateway” configuration page that displays your public IP and miscellaneous other information about your WAN Link. (2) Click OK to finish after entering your ISP DNS information. This will redirect traffic for domain names that your server is not familiar with. Obviously “google.com” is not going to be “Known” by your DNS until it queries the internet DNS servers via your ISP. b) Now you need to configure the Reverse Lookup Zone. i) Right click on “Reverse Lookup Zone” and select “New Zone” (1) Create a Primary Zone (Your Server is authoritative for Primary Zone) (a) Select the default Zone Replication Scope since it seems like a single LAB domain. (b) IPv4 Reverse Lookup Zone(after you’ve completed updates it may offer IPv6) (c) Enter your IP Network ID, example 192.168.3.6 – This makes your Network ID 192.168.3 ii) Once you’ve created your zone, add a ptr record to your server. (1) Right Click on your new “Reverse Lookup Zone” in the Reverse Lookup Zone folder and select “New Pointer(PTR)…” (a) Enter the IP address for your Server (b) Click on “Browse” (i) Double click on your Server Name (domain controller) (ii) Double click on Forward Lookup Zone (iii) Double click on your Domain Name (iv) Select your server’s host record that was automatically created c) Finish your DNS configuration by updating your IP Address information. i) Start> Run> NCPA.CPL (I’m lazy and this is the fastest way to pull it up) (1) Double click on your Ethernet controller (2) Open properties (3) Click on “Internet Protocol Version 4 (TCP/IP) (a) If you did not reconfigure this Post installation of AD, you might notice it set itself to the loop back address 127.0.0.1 – Change this back to the IP of the Server. Here's the directions I posted there. I hope they help. Follow these directions, best of luck!! Steve Kline - MCITP: Server Administrator All answers are posted, "As Is" with no warranties or guarantees implied. http://www.itjournal-stevekline.com - Content coming soon. Hi there, thanks for all the advice guys, if I take this piece of the log: 31,07/06/10,03:25:36,DNS Update Failed,192.168.0.4,File_Server_Test.bellevueroad.local,-1, 31,07/06/10,03:26:11,DNS Update Failed,192.168.0.6,AD_Replication.bellevueroad.local,-1, 31,07/06/10,03:26:46,DNS Update Failed,192.168.0.8,WIN-A61QP98SRSH,-1, 31,07/06/10,03:27:21,DNS Update Failed,192.168.0.9,Win7_Test.bellevueroad.local,-1, 31,07/06/10,03:27:56,DNS Update Failed,192.168.0.25,front_room_two.bellevueroad.local,-1, 31,07/06/10,03:28:31,DNS Update Failed,192.168.0.50,Becky-PC.bellevueroad.local,-1, 31,07/06/10,03:29:06,DNS Update Failed,192.168.0.51,Nexus-PC.bellevueroad.local,-1, 11,07/06/10,03:37:38,Renew,192.168.0.5,Xavier,C42C03D164B7, 11,07/06/10,03:44:19,Renew,192.168.0.7,Pachelbel,9027E437CE16, 11,07/06/10,03:44:31,Renew,192.168.0.7,Pachelbel,9027E437CE16, 00,07/06/10,17:11:53,Started,,,, You would agree that 3.44.41 it tried to renew Pachelbel, that was the logs last entry, when I got in from work it would not give any devices DHCP address until I restarted the machine, as shown on the log at 17.11.53 with the entry : 00,07/06/10,17:11:53,Started,,,,

Also I will post ipconfig /all later

Also I will post ipconfig /all later Will continue this after the weekend