<div>
If anyone knows, this is an urgent issue...
</div>


<div>
Ok I found that we had another group policy overriding the default policy with the refresh settings, and I have changed the default timeout for mapped drives.<br />
<br />
I'll update in a day here on how it worked.
</div>


<div>
That's why I kept Refresh of Group Policy Object Setting as the first one..<br />
Glad to see it fixed..
</div>


<div>
Well its not quite fixed yet...<br />
Lanmanserver is still crashing, but the group policy change seemed to prolong the reboots needed.<br />
There aren't any clear defined events that show why this would be happening either...<br />
<br />
<br />

</div>


<div>
&lt;&lt; Make sure the restarting events or reasons are captured in your server. &gt;&gt;<br />
<br />
Capture the reason why it is restarting. This will help you to solve the crash issue.
</div>


<div>
It is restarting, because i physically have to reboot the server to have it funcitoning again.<br />
<br />
Sorry if i was unclear
</div>


<div>
The solution was the start to finding the final problem. &nbsp;It was a combination of the settings described with an intrusion event locking the server. 
</div>


<div>
<div class="content wysiwyg-content">
Here is my situation:<br />
<br />
I am running Windows Server 2003 on several servers, two of which are an application server and a database server (SQL Server 2005). &nbsp;The system allows connections through TCP/IP to the database, but not named pipes ( for all applications on the application server ). &nbsp;Every 2-4 hours, the lanmanserver ( Server ) service will hang and cause mapped drives and connectivity on the application server to hang. &nbsp;Rebooting the server will remedy the situation, with the cycle repeating about 2-4 hours later.<br />
<br />
Named pipes and TCP/IP are enabled on SQL Server, and both servers have been updated with the most current windows updates.<br />
<br />
Any idea what may be causing the lanmanserver service to hang?
</div>
</div>


Here is my situation:

I am running Windows Server 2003 on several servers, two of which are an application server and a database server (SQL Server 2005).  The system allows connections through TCP/IP to the database, but not named pipes ( for all applications on the application server ).  Every 2-4 hours, the lanmanserver ( Server ) service will hang and cause mapped drives and connectivity on the application server to hang.  Rebooting the server will remedy the situation, with the cycle repeating about 2-4 hours later.

Named pipes and TCP/IP are enabled on SQL Server, and both servers have been updated with the most current windows updates.

Any idea what may be causing the lanmanserver service to hang?

Named Pipes - Lanmanserver Crashing - Mapped Drives disconnecting

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Microsoft SQL Server 2005 is a suite of relational database management system (RDBMS) products providing multi-user database access functionality.Component services include integration (SSIS), reporting (SSRS), analysis (SSAS), data quality, master data, T-SQL and performance tuning. It includes support for managing XML data and allows a database server to be exposed over web services using Tabular Data Stream (TDS) packets encapsulated within SOAP (protocol) requests.

Microsoft SQL Server 2005

Transmission Control Protocol/Internet Protocol (TCP/IP) is the set of networking protocols that define end-to-end connectivity specifying how data should be packeted, addressed, transmitted, routed and received at the destination. This functionality is organized into four abstraction layers which are used to sort all related protocols according to the scope of networking involved.