Server registry keys

Bgestel

Hi all,

A customer of mine is running a 3.70 native server. This server is running on a co location. performance is good but once in a while te connection fails and everybody is kicked out of his/her client. This isn't the problem. What also happens is that nav keeps the sessions alive <- see session table of the people who got kicked out. So when logging back in they are using to users in the licence. Nav doesn't have a kick user function #-o so the serverservice needs to be restarted.

I can remember there being a registry key which i can add to the registry keys for the navision server which allows me to set a Time to live for inactive/disconnected sessions.

Does annyone know what this key is ?

thx in advance.

kine

it was something like:

How to change KeepAliveTime in WIN NT

The KeepAliveTime is an adjustable parameter where you can decide how often NAVISION and NAVISION Financials will check for a "dead" client.

The NAVISION server and NAVISION Financials server uses the TCP/IP keep alive packet, to find out If a client beaks down, or the user shuts it off.

The following is a copy from a Microsoft forum. (Look for KeepAliveTime)

KeepAliveTime
Key: Tcpip\Parameters
Value Type: REG_DWORD - Time in milliseconds
Valid Range: 1 - 0xFFFFFFFF
Default: 7,200,000 (two hours)
Description: The parameter controls how often
TCP attempts to verify that an idle
connection is still intact by sending a keep
alive packet. If the remote system is still
reachable and functioning, it will
acknowledge the keep alive transmission. Keep
alive packets are not sent by default. This
feature may be enabled on a connection by an
application.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"KeepAliveTime"=dword:0000ea60
"KeepAliveInterval"=dword:000003e8

todro

kine wrote:

it was something like:

How to change KeepAliveTime in WIN NT

The KeepAliveTime is an adjustable parameter where you can decide how often NAVISION and NAVISION Financials will check for a "dead" client.

The NAVISION server and NAVISION Financials server uses the TCP/IP keep alive packet, to find out If a client beaks down, or the user shuts it off.

The following is a copy from a Microsoft forum. (Look for KeepAliveTime)

KeepAliveTime
Key: Tcpip\Parameters
Value Type: REG_DWORD - Time in milliseconds
Valid Range: 1 - 0xFFFFFFFF
Default: 7,200,000 (two hours)
Description: The parameter controls how often
TCP attempts to verify that an idle
connection is still intact by sending a keep
alive packet. If the remote system is still
reachable and functioning, it will
acknowledge the keep alive transmission. Keep
alive packets are not sent by default. This
feature may be enabled on a connection by an
application.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]
"KeepAliveTime"=dword:0000ea60
"KeepAliveInterval"=dword:000003e8

although I know some of the discussions about these parameters, I still would like to remind for the following things:

a.) the registry settings are globally used for every TCP connection, not only for Navision, unless b.) b.) if the navision client would support application-level keepalive, it could also overwrite the registry settings on a connection level directly by ioctl calls c.) as the KeepAlive works on a TCP stack level, it only covers communication problems on a network level and not a "hanging" client d.) keepalive is by default switched off and has to be enabled by the application

Therefore, I would not expect too much out of this approach...

Bgestel

thank you, regard this as solved