After additional debugging we learned that the issue manifests itself on servers that have a difference between the Active Directory object name and the DNS name (our server administrators confirmed this is the case for the server we were trying to connect to). If we created a DNS alias to match the AD name, then the connection would work again.
For example: AD Name: Fileserver DNS Name: Fileserver1 This does not work. However if we add the alias: DNS Name Alias: Fileserver -> Fileserver1 Then it works THE INFORMATION CONTAINED IN THIS E-MAIL MESSAGE AND ANY ATTACHMENTS SENT FROM GENTEX CORPORATION IS GENTEX CONFIDENTIAL INFORMATION INTENDED ONLY FOR THE PERSONAL USE OF THE INDIVIDUAL OR ENTITY NAMED ABOVE. If you are not the intended recipient, you are hereby notified that any review, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail, and delete this e-mail message and any attachments from your computer.
