Hello again Stefan, thanks for looking into this.
First, confirm that a regular SSH login using the same username, client,
and server, with Kerberos enabled, works.
debug1: Next authentication method: gssapi-with-mic
debug1: Authentication succeeded (gssapi-with-mic).
Authenticated to newhost ([SERVER IP]:22).
Second, can you create an account on the server that does not need to
authenticate via Kerberos, and attempt a regular user/password or SSH
Public Keyfile login, to see if that works? If that doesn't work, then
your X2Go installation (server, client, or both) is botched somehow, and
the issue is independent of Kerberos.
Jan 24 09:43:04 newhost sshd[10146]: Authorized to remoto, krb5 principal remoto@KERBEROS.COM (krb5_kuserok)Jan 24 09:43:04 newhost sshd[10146]: Accepted gssapi-with-mic for remoto from [CLIENT IP] port 33428 ssh2: remoto@KERBEROS.COMJan 24 09:43:04 newhost sshd[10146]: pam_unix(sshd:session): session opened for user remoto by (uid=0)Jan 24 09:43:04 newhost systemd-logind[554]: New session 12 of user remoto.Jan 24 09:43:04 newhost sshd[10210]: Received disconnect from [CLIENT IP] port 33428:11: disconnected by userJan 24 09:43:04 newhost sshd[10210]: Disconnected from user remoto [CLIENT IP] port 33428Jan 24 09:43:04 newhost sshd[10144]: dispatch_protocol_error: type 90 seq 3 [preauth]Jan 24 09:43:04 newhost sshd[10146]: pam_unix(sshd:session): session closed for user remotoJan 24 09:43:04 newhost systemd-logind[554]: Removed session 12.