Hi Travis,
We had the same issue, and it was caused by a Microsoft security patch on the MS AD controllers (18.04) related to RC4 encryption.
To resolve it, we configured the user account used for the SPNEGO setup to use AES-256 encryption instead. ...