<div>
How often does DHCP lease expire? Servers should always have static IPs. I would assign the server a static IP, and then try the following:<br />
With the static IP, see if the problem still occurs.<br />
If it doesn't, try adding a host entry to the client machine that keeps losing connection.<br />
If that doesn't work try mapping the drive using the IP of the machine instead of the hostname.<br />

</div>


How often does DHCP lease expire? Servers should always have static IPs. I would assign the server a static IP, and then try the following:
With the static IP, see if the problem still occurs.
If it doesn't, try adding a host entry to the client machine that keeps losing connection.
If that doesn't work try mapping the drive using the IP of the machine instead of the hostname.


<div>
Should the server be set to auto-config dns / dhcp from the router or should I set statically?
</div>


Should the server be set to auto-config dns / dhcp from the router or should I set statically?

<div>
<div class="content wysiwyg-content">
We are running server 2003 and active directory and recently moved offices. &nbsp;The only thing that changed was our isp. <br />
<br />
The server and the workstation are set to dynamically assign IP addresses. The users have access to the internet and printers without issue. &nbsp;The problem is we share the server drive as F drive for all of the workstations. &nbsp;When the users start up in the morning - they have no issues connecting to the F drive. &nbsp;But a couple of times a day when the go access the F drive they get an error message that F drive could not be reached. &nbsp;The only way to fix is to reboot their workstations. <br />
<br />
What can we do to permantly resolve this issue?<br />

</div>
</div>


We are running server 2003 and active directory and recently moved offices.  The only thing that changed was our isp. 

The server and the workstation are set to dynamically assign IP addresses. The users have access to the internet and printers without issue.  The problem is we share the server drive as F drive for all of the workstations.  When the users start up in the morning - they have no issues connecting to the F drive.  But a couple of times a day when the go access the F drive they get an error message that F drive could not be reached.  The only way to fix is to reboot their workstations. 

What can we do to permantly resolve this issue?


Network drive disconnects through the day in AD enviroment

Microsoft server applications are those applications developed specifically, but not necessarily exclusively, on the Windows Server platform. In addition to well-known products like SQL Server, Exchange, Internet Information Services (IIS), Microsoft Dynamics, Forefront, Lync and Sharepoint, they include applications like Skype, BizTalk, Hyper-V, Groove and Commerce Server. Server applications are managed with the Microsoft System Center.

Microsoft Server Apps

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.