I did, doesn't apply to our situation and the error is different - "SEC_E_WRONG_PRINCIPAL". Our issue is that the domain from the trusted forest doesn't know about the SPNs registered...
Additional info: ran wireshark and determined that the error is "KDC_ERR_S_PRINCIPAL_UNKNOW". Looks like the domain to which a user belongs (DomainB) doesn't know about the SPN registered in the resource...