Kerberos V4 krb_mk_req failed: You have no tickets cached

[jonnybb1]

When trying to remotely login to WUFTP (version 2.6) on a newly updated RH8.0 box I get the following error:
"530 Must perform authentication before identifying USER.
Login failed."
When trying to locally login, I get the following error:
Connected to 127.0.0.1.
220 silver01 FTP server (Version 5.60) ready.
334 Using authentication type GSSAPI; ADAT must follow
GSSAPI accepted as authentication type
GSSAPI error major: Miscellaneous failure
GSSAPI error minor: No credentials cache found
GSSAPI error: initializing context
GSSAPI authentication failed
334 Using authentication type KERBEROS_V4; ADAT must follow
KERBEROS_V4 accepted as authentication type
Kerberos V4 krb_mk_req failed: You have no tickets cached
Name (127.0.0.1:john01):

PLEASE HELP ME SOMEBODY!

Thanx,

jonnybb1@lantexco.com

 

[HeyZuess]

looks like wuftpd is trying to use kerberos for it's authentication mechanism. not quite sure how to tell it not to, because one of the first things i did after loading rh8 was to remove all of wuftpd and install pro-ftpd (

http://www.proftpd.org).

 

[marsd]

You have configured your ftp server to use kerberos
v5/gssapi,or Kerberos v4 as it's auth and no other
means of authenticating is what it looks like from here.

If you meant to do this, and you are in a kerberos
domain then see your sysadmin for why you are not
getting a ticket or try to kinit again.

 

[jonnybb1]

I really just want regular text login and password. I can only say that this started shortly after the last up2date -u upgrades I did for RH 8.

Anyone know how to manually change the authentication type back to defaults??

Jonnybb1@lantexco.com

 

[jonnybb1]

OK ALL I HAVE THE ANSWER!!!!!!!!!!

The short answer is I had the sbin/kerberos/ftpd deamon checked in the services GUI. How it got checked is that I believe during the last update either it magically got turned on or I was playing around wit it and forgot to turn it off! @#@#!!!&!^!%!

So there it is for all searching he web for thos funky errors, just remove any instance of Kerberos/ftpd from the startup sequence (sorry Windows terminology) and have fun!

Thanx for your navigation to the root problem!

jonnybb1