From: "Lewis G Rosenthal" Received: from [50.73.8.217] (account lgrosenthal@2rosenthals.com HELO [192.168.200.30]) by 2rosenthals.com (CommuniGate Pro SMTP 5.4.10) with ESMTPSA id 9676199 for ecs-isp@2rosenthals.com; Thu, 16 May 2024 11:19:15 -0400 Subject: Re: [eCS-ISP] Bind 9.11.37 issue - ticket #784 - update To: eCS ISP Mailing List References: Organization: Rosenthal & Rosenthal, LLC Message-ID: <664623F1.1050006@2rosenthals.com> Date: Thu, 16 May 2024 11:19:13 -0400 User-Agent: Mozilla/5.0 (OS/2; Warp 4.5; rv:38.0) Gecko/20100101 Firefox/38.0 SeaMonkey/2.35 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit On 05/16/24 11:04 am, Massimo S. wrote: > Hi all, > > my own "startup.cmd" do: > > inetcfg -s keepalive 60 > inetcfg -set all > > i've now seen with inetcfg -get all that my keepalive is still the very > old default: 300 > You just overwrote your 60 second keepalive (likely still too long, anyway) with whatever was written in %ETC%\inetcfg.ini (default=300 seconds). Just: inetcfg -s keepalive 15 inetcfg -g all *once* Remove any inetcfg references in STARTUP.CMD. When the stack initializes, it will automatically read %ETC%\inetcfg.ini which will have keepalive 30 in it. > maybe this could cause issues on the stack ip > Ya think? A 5 minute keepalive on a modern LAN or even broadband connection is almost forever. > i don't understand why inetcfg -s keepalive 60 at startup don't work > anyway i've set it manually in the "lunch break" and rebooted the VM > It doesn't work because inetcfg.ini is higher and you are reading that (inetcfg -get all = read all settings from %ETC%\inetcfg.ini and overwrite what is currently in use). -- Lewis ------------------------------------------------------------- Lewis G Rosenthal, CNA, CLP, CLE, CWTS, EA Rosenthal & Rosenthal, LLC www.2rosenthals.com visit my IT blog www.2rosenthals.net/wordpress -------------------------------------------------------------