From this tab, you can add or remove a KDC (Key Distribution Center), and rearrange the order of KDCs for the selected realm. You can also define an administrative KDC for the realm and specify UDP or TCP for communications.
The options are:
|
Displays the current list of KDCs. The order of hosts in the determines the order in which the KDCs attempt to service an authentication request. If the first KDC in the list fails to service a request, the next KDC makes an attempt, and so on.Use the and buttons to change the order of the list. |
|
Specifies the administrative KDC or master for this realm. You must specify a master KDC to change passwords. |
|
When selected, the session uses your Windows credentials to supply Kerberos identification and authentication. This option is available only if you're logged on to a Windows domain and your system is configured to support this feature. |
|
When selected, the Kerberos client uses your Leash32 credentials cache to obtain service tickets. If you authenticate to the KDC through Leash32, you don't need to reenter your Kerberos passwords. This option is available only if you installed Leash32 on your system. |
|
Specifies the maximum packet size for UDP communications with the KDC. The Kerberos client uses UDP as the default protocol for communications unless the packet size exceeds the value specified, in which case, it uses TCP. Set the value to zero to use only TCP. Decrease this value if you have trouble authenticating to a Windows KDC and you belong to a large number of groups, or if is selected. |