[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Single Page
Top Document: Kerberos FAQ, v2.0 (last modified 8/18/2000)
Previous Document: 4.8. "Couldn't authenticate to server: Bad sendauth version was sent"
Next Document: 4.10. When I telnet from a Linux machine to a Solaris machine with Kerberos and hit Ctrl-C, the connection hangs.
-
Search the FAQ Archives
Single Page
Top Document: Kerberos FAQ, v2.0 (last modified 8/18/2000)
Previous Document: 4.8. "Couldn't authenticate to server: Bad sendauth version was sent"
Next Document: 4.10. When I telnet from a Linux machine to a Solaris machine with Kerberos and hit Ctrl-C, the connection hangs.
4.9. When I try using Kerberos ftp, it doesn't work, but it says, "No error".
What you probably saw were errors like the following: GSSAPI error major: No error GSSAPI error minor: No error There is an error here, it's just not being reported very well. This comes from the ftp daemon; it is trying to build a service principal for the ftp service using the fully-qualified local hostname as the principal instance, and it's not finding it in the local keytab. This generally results in a confusion between the machine's local hostname and it's hostname in DNS. Note that ftpd is currently the only program that deals with service principals this way, so this is why these problems crop up with the Kerberos ftp daemon and not other Kerberized services.
Top Document: Kerberos FAQ, v2.0 (last modified 8/18/2000)
Previous Document: 4.8. "Couldn't authenticate to server: Bad sendauth version was sent"
Next Document: 4.10. When I telnet from a Linux machine to a Solaris machine with Kerberos and hit Ctrl-C, the connection hangs.
Single Page
[ Usenet FAQs | Search | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
Ken Hornstein <kenh@cmf.nrl.navy.mil>
Last Update December 05 2008 @ 00:11 AM