Idle Timeout & Session Timeout in Constraints - NAP win 2016

Question

Hi everyone,
I am using NAP on WIN server 2016 and want to ask about the difference and the best practice to use both Idle Timeout & Session Timeout in Constraints.

NPS -> Policies -> Network Policies-> Constraints -> Session Timeout.

NPS -> Policies -> Network Policies-> Constraints -> Session Timeout.

What will happen if i set the idle timeout to 60 for example?
What will happen if i set the session timeout to 60 for example?
What is the best practices ?

Thread source link: https://social.technet.microsoft.com/Forums/zh-CN/ca79d73d-bd55-49b1-8979-6df0d9c8bff6/idle-timeout-amp-session-timeout-in-constraints-nap-win-2016?forum=winserverNAP

Answer 1

Hi ,

Welcome to our new Microsoft Q&A Platform.

The difference between Idle and Session is network activity.

For example, if you set the session timeout for I minutes, after I minutes the NPS policy will cut the connection.

The idle timeout, based on my knowledge, if the connection is cut down for some network or other reasons, the NPS will hold this connection until the idle timeout. During this period, when your network recover, your client can connect automatically without NPS authentication again.

You can refer the following link for more information:

https://community.spiceworks.com/topic/1729351-rras-vpn-idle-timeout-not-disconnecting-users

Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Best Regards,

Candy