<div>
did you try to uninstall/install the network card (using device manager)<br />
do you have issues like two clients has the same IP?
</div>


<div>
I'd like to attach the client's system event log which I saved immediately after the most recent drop. Is that a security risk?
</div>


<div>
Won't be able to troubleshoot more until a little later --- the computer is currently in use. I can say that I just today noticed in DHCP on the server that there was one entry just named &quot;BAD_ADDRESS&quot; and in the description it said that the IP was already in use (though it didn't tell me what the IP is or what the name is). I deleted it from DHCP and it has not reappeared.<br />
<br />
I have not tried uninstalling and reinstalling the network card (assuming you meant on the client?) but as I mentioned, just disable/enable prompts a DHCP request that results in a good IP.<br />
<br />
I'll try to run those couple commands on the client asap and see where that gets me.
</div>


<div>
I wish you quick good luck,<br />
regarding system event log, there is no need for that at the moment,
</div>


<div>
Okay, re: event log. I'm finding the following leading up to the drop:<br />
<br />
First this:<br />

<pre><code class="code-1 nolinks" id="code-20-40464738-1"><span>Event ID 7038 The nvUpdatusService service was unable to log on as .\UpdatusUser with the currently configured password due to the following error: </span>
<span>Logon failure: the specified account password has expired.</span>
<span></span>
<span>To ensure that the service is configured properly, use the Services snap-in in Microsoft Management Console (MMC).</span>
</code></pre>
<br />
Then this:<br />

<pre><code class="code-1 nolinks" id="code-20-40464738-2"><span>Event ID 7000 The NVIDIA Update Service Daemon service failed to start due to the following error: </span>
<span>The service did not start due to a logon failure.</span>
</code></pre>
<br />
Seems like that would be extremely relevant, right? <br />
<br />
Not sure why it's saying the account password has expired... b/c it hasn't.
</div>


<div>
I think not, but maybe it is a surface of a bigger problem<br />
make sure that the NVIDIA Update Service Daemon is running on local system account<br />
if yes, then dis-join the computer from AD and re-join it again
</div>


<div>
It was stopped but set to use UpdateusUser. I changed it to Local system account, hit start and got a message that &quot;some services won't start if not currently in use&quot; or something. I'm thinking after a reboot this might solve THAT particular error appearance.
</div>


<div>
I have not gotten another user reported network drop since doing a TCP/IP reset, flushdns and tweaking the nvidia update service logon credentials. It's been about 20 hours though the majority of that time has been non-work hours.<br />
<br />
In looking through the system event log I don't see any evidence of network drop with the exception of one particular event:<br />
<br />

<pre><code class="code-1 nolinks" id="code-20-40466691-1"><span>Event ID 1006, Error Code 49 -- The processing of Group Policy failed. Windows could not authenticate to the Active Directory service on a domain controller. (LDAP Bind function call failed). Look in the details tab for error code and description.</span>
</code></pre>
<br />
Under the EventData heading on the Details tab it says &quot;ErrorDescription: Invalid Credentials&quot;.
</div>


<div>
I think It is better now to rejoin the client computer to the domain
</div>


<div>
i was afraid of that... will that mess up user profiles... outlook/desktop/documents folder etc or will it be pretty seamless?
</div>


<div>
it did not happened to me, but I'cant give guarantee (this is Microsoft :))<br />
Ok, try to reset computer account <br />
check this<br />
<a href="http://redmondmag.com/articles/2014/04/21/domain-trust-issues.aspx" rel="ugc">http://redmondmag.com/articles/2014/04/21/domain-trust-issues.aspx</a>
</div>


<div>
Anbody know exactly what the reset function does?
</div>


<div>
there is some explanation in the URL I've sent to you, reset the security key (password) of the computer that to communicate with AD
</div>


<div>
It appears that John Hurst's suggestions were the fix (or one of them was). Can't completely verify which one or if either did the trick since I was simultaneously trying a number of things and since it has been an intermittent problem, but it has been a few days and the problem has not recurred. Thanks!
</div>


<div>
@jpfulton - Thanks for the update and I was happy to help.
</div>


<div>
<div class="content wysiwyg-content">
Small Windows domain with one DC. DC is the only DHCP server on network. One client on the network is randomly dropping (multiple times throughout the day) its IP and then coming up with a 169. IP thereby dropping the network connection. ipconfig /renew just hangs. Disable/enable the network adapter comes up with a good IP again.<br />
<br />
MODEM ----&gt; &nbsp;FIREWALL (10.0.0.1) -----&gt; SERVER (10.0.0.2) -----&gt; DHCP CLIENTS (.50-.99)<br />
<br />
Background: Recent issues with server/network in last month. Blue screens and network dropouts. I think possible power outage related. Maybe a half-fried network port (on-board) on server (not yet replaced) and a half-fried switch (which we've since replaced). I was trying to plan for a possible replacement of the server with new hardware so I virtualized our existing server (bad idea). I think in the process I may have confused the hell out of our network (suddenly had 2 DHCP servers on the network). I fixed those issues but now have this one remaining problem client. Any help much appreciated.
</div>
</div>


Small Windows domain with one DC. DC is the only DHCP server on network. One client on the network is randomly dropping (multiple times throughout the day) its IP and then coming up with a 169. IP thereby dropping the network connection. ipconfig /renew just hangs. Disable/enable the network adapter comes up with a good IP again.

MODEM ---->  FIREWALL (10.0.0.1) -----> SERVER (10.0.0.2) -----> DHCP CLIENTS (.50-.99)

Background: Recent issues with server/network in last month. Blue screens and network dropouts. I think possible power outage related. Maybe a half-fried network port (on-board) on server (not yet replaced) and a half-fried switch (which we've since replaced). I was trying to plan for a possible replacement of the server with new hardware so I virtualized our existing server (bad idea). I think in the process I may have confused the hell out of our network (suddenly had 2 DHCP servers on the network). I fixed those issues but now have this one remaining problem client. Any help much appreciated.

One Client on Windows Domain Intermittently Drops Good IP and gets 169. IP

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

Network Operations includes asset management, help-desk supervision, security and user policies, infrastructure administration and anything else that affects the operation of your network. Discussions will include those of best practices in platforms, configurations, performance, security and accounting.