<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: automate server reboot in Netservers</title>
    <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032205#M5097</link>
    <description>Hi Paul,&lt;BR /&gt;&lt;BR /&gt;You can make use shutdown.exe command which is a part of WindowsNT resource kit. This command can be put in a small script which checks for network connectivity and if the test case fails shutdown (reboot) can be invoked.&lt;BR /&gt;&lt;BR /&gt;For getting Unix like commands and to write shell scripts for the above task you can additionally install "Windows Services for Unix" ( 4months trail from MS site). &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.microsoft.com/windows/sfu/default.asp" target="_blank"&gt;www.microsoft.com/windows/sfu/default.asp&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Karthik S S</description>
    <pubDate>Thu, 24 Jul 2003 12:05:37 GMT</pubDate>
    <dc:creator>Karthik S S</dc:creator>
    <dc:date>2003-07-24T12:05:37Z</dc:date>
    <item>
      <title>automate server reboot</title>
      <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032201#M5093</link>
      <description>I have a server that keeps losing it's network connectivity.  As a temporary fix it usually gets rebooted.&lt;BR /&gt;&lt;BR /&gt;This means coming out at night if it goes wrong.&lt;BR /&gt;&lt;BR /&gt;Is there a way of checking network connectivity every 30 secs, maybe a batch file that pings the default gateway for example, and then reboots itself if it gets no reply.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance</description>
      <pubDate>Thu, 24 Jul 2003 09:15:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032201#M5093</guid>
      <dc:creator>paul_280</dc:creator>
      <dc:date>2003-07-24T09:15:25Z</dc:date>
    </item>
    <item>
      <title>Re: automate server reboot</title>
      <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032202#M5094</link>
      <description>Must be something to do with the hardware. Script to reboot the system will be of no use for a permanant fix.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;You can try the following one by one to zero down on the root cause..&lt;BR /&gt;&lt;BR /&gt;1. Check the network settings on the system&lt;BR /&gt;&lt;BR /&gt;2. Check for the duplicate IP addresses on the network.&lt;BR /&gt;&lt;BR /&gt;3. Try with a different UTP cable&lt;BR /&gt;&lt;BR /&gt;4. Try connecting the server to a different switch or switch port. &lt;BR /&gt;&lt;BR /&gt;5. Replace the NIC card on the system&lt;BR /&gt;&lt;BR /&gt;6. Try installing latest patches for the OS&lt;BR /&gt;&lt;BR /&gt;Pl. post more details about the system &lt;BR /&gt;&lt;BR /&gt;-Karthik S S</description>
      <pubDate>Thu, 24 Jul 2003 10:24:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032202#M5094</guid>
      <dc:creator>Karthik S S</dc:creator>
      <dc:date>2003-07-24T10:24:46Z</dc:date>
    </item>
    <item>
      <title>Re: automate server reboot</title>
      <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032203#M5095</link>
      <description>Karthik&lt;BR /&gt;&lt;BR /&gt;Thanks for the input, yes it's a temporary fix I agree, the problem is caused by 3rd party software that we've paid lots of money to the manufacturers to put right.  &lt;BR /&gt;&lt;BR /&gt;Until they do though, I'm trying to find a fix so we don't keep having to come out at night, and rebooting the system does seem to do the trick for a few hours&lt;BR /&gt;&lt;BR /&gt;Details of server&lt;BR /&gt;&lt;BR /&gt;Name   ourserver&lt;BR /&gt; Model   HP NetServer LP 2000r  &lt;BR /&gt; Location     &lt;BR /&gt;   &lt;BR /&gt; Processor 1   Pentium III, 1266 MHz  &lt;BR /&gt; Processor 2   Pentium III, 1266 MHz  &lt;BR /&gt; BIOS Version   4.06.06 RP  &lt;BR /&gt; Video BIOS Version   4.328  &lt;BR /&gt; Memory Total   1280 MB  &lt;BR /&gt; Up Time   2 days, 17:48:38.56  &lt;BR /&gt; OS   Windows NT  &lt;BR /&gt; OS Version   4.0 Build 1381 Service Pack 6  &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 24 Jul 2003 11:22:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032203#M5095</guid>
      <dc:creator>paul_280</dc:creator>
      <dc:date>2003-07-24T11:22:14Z</dc:date>
    </item>
    <item>
      <title>Re: automate server reboot</title>
      <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032204#M5096</link>
      <description>Should be possible to do with some freeware tools.&lt;BR /&gt;&lt;BR /&gt;There are PING variants that set errorlevel and command line tools to shut down the system. Mix them together in a batch file and schedule the batch file via scheduler service (or add a freeware timer tool).&lt;BR /&gt;&lt;BR /&gt;A google search for PING and ERRORLEVEL revealed this:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://wettberg.home.texas.net/alive.htm" target="_blank"&gt;http://wettberg.home.texas.net/alive.htm&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Use this to ping a 'known good' ip address (like another server). If errorlevel isn't zero reboot.&lt;BR /&gt;&lt;BR /&gt;(No, I haven't tried that before)</description>
      <pubDate>Thu, 24 Jul 2003 11:40:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032204#M5096</guid>
      <dc:creator>Martin Breidenbach</dc:creator>
      <dc:date>2003-07-24T11:40:15Z</dc:date>
    </item>
    <item>
      <title>Re: automate server reboot</title>
      <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032205#M5097</link>
      <description>Hi Paul,&lt;BR /&gt;&lt;BR /&gt;You can make use shutdown.exe command which is a part of WindowsNT resource kit. This command can be put in a small script which checks for network connectivity and if the test case fails shutdown (reboot) can be invoked.&lt;BR /&gt;&lt;BR /&gt;For getting Unix like commands and to write shell scripts for the above task you can additionally install "Windows Services for Unix" ( 4months trail from MS site). &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.microsoft.com/windows/sfu/default.asp" target="_blank"&gt;www.microsoft.com/windows/sfu/default.asp&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Karthik S S</description>
      <pubDate>Thu, 24 Jul 2003 12:05:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032205#M5097</guid>
      <dc:creator>Karthik S S</dc:creator>
      <dc:date>2003-07-24T12:05:37Z</dc:date>
    </item>
    <item>
      <title>Re: automate server reboot</title>
      <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032206#M5098</link>
      <description>Martin / Karthik&lt;BR /&gt;&lt;BR /&gt;OK with your help I'm on my way to solving this.&lt;BR /&gt;&lt;BR /&gt;I've downloaded the Alive program and installed the reskit.  I've written a batch file that pings another server on the same switch (this will probably be changed) every 30 seconds, if I pull the network cable out of the other server the problem server is rebooting as planned.&lt;BR /&gt;&lt;BR /&gt;All I need to do now is get it to log back in automatically.  There is a program that needs to be running for the server to do it's job, so I could put that program in the start up folder&lt;BR /&gt;&lt;BR /&gt;So any ideas about getting it to automatically logon?</description>
      <pubDate>Thu, 24 Jul 2003 13:20:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032206#M5098</guid>
      <dc:creator>paul_280</dc:creator>
      <dc:date>2003-07-24T13:20:00Z</dc:date>
    </item>
    <item>
      <title>Re: automate server reboot</title>
      <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032207#M5099</link>
      <description>I believe automatic logon can be done by doing some registry settings - should be documented somewhere in MS knowledgebase. I think the MS tweakui powertoy can do that too.&lt;BR /&gt;&lt;BR /&gt;AFAIK automatic logon is a security risk because the admin password is written unencrypted in the registry.</description>
      <pubDate>Thu, 24 Jul 2003 17:52:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032207#M5099</guid>
      <dc:creator>Martin Breidenbach</dc:creator>
      <dc:date>2003-07-24T17:52:34Z</dc:date>
    </item>
    <item>
      <title>Re: automate server reboot</title>
      <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032208#M5100</link>
      <description>Paul,&lt;BR /&gt;&lt;BR /&gt;To enable autologon read,&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www.itworld.com/nl/win_admin_tips/07202001/" target="_blank"&gt;http://www.itworld.com/nl/win_admin_tips/07202001/&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;To lock the workstation once it has logged in ... probably you can enable screen saver password.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Karthik S S</description>
      <pubDate>Fri, 25 Jul 2003 06:19:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032208#M5100</guid>
      <dc:creator>Karthik S S</dc:creator>
      <dc:date>2003-07-25T06:19:59Z</dc:date>
    </item>
    <item>
      <title>Re: automate server reboot</title>
      <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032209#M5101</link>
      <description>Karthik / Martin&lt;BR /&gt;&lt;BR /&gt;Yes, all done, thanks for the help&lt;BR /&gt;&lt;BR /&gt;Incase anyone has done a search and found this and needs to do something similar here's what I did with your help:&lt;BR /&gt;&lt;BR /&gt;Downloaded the alive program from &lt;BR /&gt;&lt;A href="http://wettberg.home.texas.net/alive.htm" target="_blank"&gt;http://wettberg.home.texas.net/alive.htm&lt;/A&gt; &lt;BR /&gt;&lt;BR /&gt;Copied the shutdown.exe from the reskit and copied both files to system32&lt;BR /&gt;&lt;BR /&gt;then put a batch file like this in scheduled tasks to run every 30 secs&lt;BR /&gt;&lt;BR /&gt;alive servername&lt;BR /&gt;if errorlevel 1 shutdown \\ipaddress /Y /R /C&lt;BR /&gt;&lt;BR /&gt;Then changed the registry in regedt32 to enable autologon, see this article for instructions&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://support.microsoft.com/default.aspx?scid=kb;en-us;310584" target="_blank"&gt;http://support.microsoft.com/default.aspx?scid=kb;en-us;310584&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Then made another batch file like this &lt;BR /&gt;&lt;BR /&gt;RUNDLL32 USER32.DLL,LockWorkStation&lt;BR /&gt;&lt;BR /&gt;Then put this .bat file and a shortcut to the program that needs to running on the server in the startup folder&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 25 Jul 2003 07:25:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032209#M5101</guid>
      <dc:creator>paul_280</dc:creator>
      <dc:date>2003-07-25T07:25:51Z</dc:date>
    </item>
    <item>
      <title>Re: automate server reboot</title>
      <link>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032210#M5102</link>
      <description>Great ...&lt;BR /&gt;&lt;BR /&gt;Thanks for sharing the procedure that you have followed.&lt;BR /&gt;&lt;BR /&gt;Now have a look at,&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x1fd2e6ab52b11743b07c0dd4ca137e4c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x1fd2e6ab52b11743b07c0dd4ca137e4c,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Enjoy&lt;BR /&gt;&lt;BR /&gt;-Karthik S S</description>
      <pubDate>Fri, 25 Jul 2003 07:49:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/netservers/automate-server-reboot/m-p/3032210#M5102</guid>
      <dc:creator>Karthik S S</dc:creator>
      <dc:date>2003-07-25T07:49:29Z</dc:date>
    </item>
  </channel>
</rss>

