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).

<snip>