Your best friend for file transfer.

Fetch application logoFetch

AUTH before ADAT? (3 posts)

  • Started 8 years ago by PG
  • Latest reply 8 years ago from PG
  • PG Member

    Hello,

    I cannot get Fetch 5.0.5 to connect to an FTP server on a kerberos realm. The error seems to be with the ADAT response. Here's the transcript:

    220 flxi06.fnal.gov FTP server (Version 5.60) ready.
    ADAT
    503 Must identify AUTH type before ADAT
    AUTH This command is checking whether this server supports Kerberos or GSS security, see RFC 2228
    504 Unknown authentication type: This command is checking whether this server supports Kerberos or GSS security, see RFC 2228
    AUTH KERBEROS_V4
    334 Using authentication type KERBEROS_V4; ADAT must follow
    sec_krbv4_get_auth_data() krbv4_service_name = ftp.flxi06
    sec_krbv4_get_auth_data() krbv4_service_name = rcmd.flxi06

    Can anyone help me?

    Thanks,
    --patrick.

    Posted 8 years ago #

  • Scott McGuire Administrator

    Hi,

    Is the Macintosh you're trying to connect from behind a NAT (are you using an Airport base station or other router for sharing Internet connections)?

    KClient (Kerberos 4) connection do not work from behind a NAT. You may want to see if the server supports connecting via GSSAPI (Kerberos 5) instead.

    If this turns out not to be the problem, let us know.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 8 years ago #

  • PG Member

    Hi,
    Switching to Kerberos 5 worked (GSSAPI).

    Thanks!
    --patrick.

    Originally posted by ScottMcGuire:

    Hi,

    Is the Macintosh you're trying to connect from behind a NAT (are you using an Airport base station or other router for sharing Internet connections)?

    KClient (Kerberos 4) connection do not work from behind a NAT. You may want to see if the server supports connecting via GSSAPI (Kerberos 5) instead.

    If this turns out not to be the problem, let us know.

    Thanks,

    Scott McGuire
    Fetch Softworks

    Posted 8 years ago #

Reply

  • Or nickname, if you prefer.
  • This will be kept confidential.
  • This is to ensure that you’re a person, not a spambot.