http://blogs.technet.com/b/jhoward/archive/2006/04/27/426562.aspxOne of those oddities I discovered a couple of days ago after trying to tune down my IIS box which is configured with a static IP address. I stopped the DHCP Client service as I figured (incorrectly) that it wouldn't be needed due to not using DHCP foren-GBTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)http://blogs.technet.com/b/jhoward/archive/2006/04/27/426562.aspx#3074658Fri, 20 Jun 2008 00:54:14 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3074658David<p>Good post. &nbsp;I also found out the hard way that the dhcp Client is required.</p> <p>Who would have thought for those servers who are statically assigned.</p> <p>Thanks.</p><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3074658" width="1" height="1">http://blogs.technet.com/b/jhoward/archive/2006/04/27/426562.aspx#426631Fri, 28 Apr 2006 05:33:02 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:426631DeanPMore than likely the clients had cached the DNS entry previously. You should always do an ipconfig /flushdns before diagnosing DNS errors. Especially to get rid of negative entries that might have been cached.<div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=426631" width="1" height="1">