Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
WH Server seems to shut itself down. RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi,

    I've been running WHS for about 4 months and have been very pleased with the system. I built my own server (P4 with 1Gb ram on an Intel D865GBF motherboard). There are 3 pcs talking to the server. Most of the time.

    However, recently I've noticed that when I come to them in the morning the server icon is that muddy brown colour and when I mouse-over it, I get the message that I'm not connected. Occasionally, running discovery.exe fixes things, but mostly I have to turn off the server and restart it from scratch.

    I thoughts about why this is happening?

    Thanks

    Robin
    Sunday, June 14, 2009 4:25 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Robin,
    can it be brought in timely context with a recent Windows Update (on client or server side)?
    If yes, you could try to uninstall the upgrades one by one and see, if it still happens.
    If you still can access the shared folders, there could also be a name resolution problem.
    Can you ping the server correctly by name and by IP address in this situation?

    Without clear messages (like errors or warnings in the event log or error messages you get if trying to map a network drive to a server share from command prompt) the following tips may be contra productive and are more kind of crystal ball polishing.

    We had something similar on some of our corporate servers about a year ago. You can try import the following lines after putting them to notepad and saving them as .REG file:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
    "PagedPoolSize"=dword:ffffffff
    "PoolUsageMaximum"=dword:00000030

    Reboot the server after importing the lines (which has to be done locally on the server desktop).
    These entries deal with the memory management for certain ressources.

    Eventually also this parameter change helps:
    1. Start regedit.
    2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\lanmanserver\parameters.
    3. Double-click IRPStackSize (or if this registry setting doesn't exist, create it with type DWORD and ensure the case is correct).
    4. Change the base to decimal, set the value to 50, and click OK.
    5. Reboot the computer.

    Best greetings from Germany
    Olaf

    • Marked as answer by Glynderi Monday, June 15, 2009 6:42 PM
    Sunday, June 14, 2009 6:56 PM
    Moderator

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Which version of WHS did you install? If it was a trial version, keep in mind, that the trial ends after 120 days, so the server rebooting itself all 2 hours or so is expected behavior in this case.
    If it was an OEM version, there may be other reasons, i.e. network drivers, power save settings etc.
    Best greetings from Germany
    Olaf

    Sunday, June 14, 2009 4:32 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    It's an OEM version, purchased from a Microsoft Partner and I don't believe there's any issue with network drivers or power save settings. The network drivers are the standard Intel ones and the power save settings - well, set to always on.

    As I said above, the problem has been a recent one that hasn't occured until recently.

    Robin
    Sunday, June 14, 2009 5:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Hi Robin,
    can it be brought in timely context with a recent Windows Update (on client or server side)?
    If yes, you could try to uninstall the upgrades one by one and see, if it still happens.
    If you still can access the shared folders, there could also be a name resolution problem.
    Can you ping the server correctly by name and by IP address in this situation?

    Without clear messages (like errors or warnings in the event log or error messages you get if trying to map a network drive to a server share from command prompt) the following tips may be contra productive and are more kind of crystal ball polishing.

    We had something similar on some of our corporate servers about a year ago. You can try import the following lines after putting them to notepad and saving them as .REG file:

    Windows Registry Editor Version 5.00

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]
    "PagedPoolSize"=dword:ffffffff
    "PoolUsageMaximum"=dword:00000030

    Reboot the server after importing the lines (which has to be done locally on the server desktop).
    These entries deal with the memory management for certain ressources.

    Eventually also this parameter change helps:
    1. Start regedit.
    2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\lanmanserver\parameters.
    3. Double-click IRPStackSize (or if this registry setting doesn't exist, create it with type DWORD and ensure the case is correct).
    4. Change the base to decimal, set the value to 50, and click OK.
    5. Reboot the computer.

    Best greetings from Germany
    Olaf

    • Marked as answer by Glynderi Monday, June 15, 2009 6:42 PM
    Sunday, June 14, 2009 6:56 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thanks for all that. Been thinking about this and I've decided to do a fresh install with a much newer motherboard - 4 SATAII connectors on board - and see how that works.

    Thanks for the advice.

    Robin
    Sunday, June 14, 2009 8:42 PM