smbclient incorrectly guesses the service principal if the user and server do not belong to the same kerberos realm and when shortname is used

Solution Verified - Updated -

Issue

  • smbclient from samba-3.0.33 cannot connect to windows server using kerberos when SPNEGO doesn't include Server Principal in the security blob
  • Unable to connect to Windows share using smbclient from RHEL5.5 using kerberos
  • smbclient/samba versions 3.0.33.x cannot connect to windows servers when the SPNEGO answer do not include the server principal in the security blob (MS11-005 security fix).

Environment

  • Red Hat Enterprise Linux 5.6
  • samba-3.0.33
  • samba3x-3.5.4
  • Microsoft Windows 2003 Server SP2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.