I'm not sure if this belongs here or on serverfault, but I already have an account here so this is where I'll start.
In my office we have a development server running windows 7 pro or server 2008 (I'm not sure which as I don't personally have access, but I can find this out if it's important), with network shares for each of the current builds. We've always done it this way, but it used to be a windows server 2003 box.
Anyway - periodically the server starts refusing connections from xp/2003 boxes, and there are errors in the server log about something running out of space; however we've found that someone rdp'ing into the server and running
net stop server,
net start server,
net start "Computer Browser" fixes the issue.
This however requires for someone with access rights to stop what they are doing and do this about 2-3 times per week.
Is there any way to solve this issue permanently? It seems obvious that there is an issue with the windows legacy network share, but is this a setup issue that can be solved, or if not is there a seamless workaround such as some way of monitoring the error log and restarting the service as soon as there's a problem?
Having checked it's Windows 7 Professional
OK I got the error message from the windows server log :
The server was unable to allocate from the system nonpaged pool because the server reached the configured limit for nonpaged pool allocations.