Please disregard this. It was a password mismatch after all, in some
way, shape, or form. The password used for the trust principal was a
strong password with many special characters, and despite recreating the
principal numerous times with the password checked and rechecked on each
side, it
And one more potentially useful piece of information that may suggest
the krbtgt/linux.example@windows.example.com principal doesn't
exist:
[selble@NW-8504LM ~]$ kinit krbtgt/linux.example@windows.example.com
krbtgt/linux.example@windows.example.com's Password:
kinit: krb5_get_init_c
