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?