- Run Registry Editor (REGEDT32.EXE).
- From the HKEY_LOCAL_MACHINE subtree,
go to the following key:
- The Value is "KeepAliveTime".
If present (usually not), double click on it to edit in milliseconds as noted below. Otherwise, continue with Step 4.
- Select "Edit -> Add Value".
- For Value name, enter KeepAliveTime.
- From the Data Type drop down list, select REG_DWORD.
- Press OK.
- In the DWORD Editor dialog, enter the number of milliseconds. Select the Radix Decimal option.
- Select OK.
- Enter the Keep-Alive value in
milliseconds; i.e., 5 minutes = 300000 msec.
Valid Range: 1 - 0xFFFFFFFF
Default: 7,200,000 (two hours)
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.
- After typing in the value, use the "Data Type" checkbox to set the value type.
- Select OK.
- Exit the Registry Editor.
- Reboot the system to make the change take effect.
Sunday, November 10, 2013
How to set the TCP/IP keep alive in Windows
When the database connection is TCP/IP, the server machine utilizes a TCP/IP feature called "Keep-Alive". Keep-Alive packets are used to probe a connection that has been inactive for a long time. The server initiates a disconnect when the probes do not get through. This means that if the client connection is lost for a prescribed length of time, the server sends a disconnect message to its server job (usually the result of a system crash or power-down). The default Keep-Alive setting for Windows is two hours.
Use the following procedure to change these parameters:
Networker slow backup issue We are facing slow backup issue many times or previously added clients suddenly slow backup issue occurs. ...
When you cannot connect to the networker server by NMC Check from putty if the networker services are running on server by nsradmin...
· Run the below commands from backup server where client resides. recover -c "source client name" -R "desti...
Dell EMC Elect 2017 Today again I am very delighted to inform you all that this was 3rd time I took part in prestigious Dell EMC ELECT...