Your best friend for file transfer.

Fetch application logoFetch

fetch with airport (2 posts)

This is an archived topic. The information in it is likely to be out-of-date and no longer applicable to current versions of Fetch.
  • Started 12 years ago by john.halle
  • Latest reply 12 years ago from Jim Matthews
  • john.halle Member

    When using Fetch 4.0 I get the following error message when I attempt to connect to the Yale server:

    Time is out of bounds (krb_rd_req)-20037.

    Some background.
    1) I am running Mac system 9.2.
    2) I do not get the problem when I am directly connected to my DSL service (SNET-SBC). The problem only occurs when I am going through the airport network.
    3) I am running airport 2.0.2.
    4) The problem (according to techs I have spoken to) has to do with the synchronization between my computers internal time and the time of the server. I have reset the time on my computer (in the date and time control panel).
    5) This version of fetch is required to use Yale's kerberos authentication protocol so I must use the version of fetch (4.0) which I download from their site. I am not able to try other newer versions of fetch.
    6) Previous versions of fetch also fail to connect.

    Any help would be hugely appreciate.

    Thanks,

    John

    Posted 12 years ago #

  • Jim Matthews Administrator

    2) I do not get the problem when I am directly connected to my DSL service (SNET-SBC). The problem only occurs when I am going through the airport network.

    I have also had trouble using Kerberos through a router (such as an Airport base station) that performs network address translation (NAT). The Kerberos protocol includes information about your IP address, and if you are going through NAT it will look to the server as if your connection is coming from the wrong address. There is a Kerberos configuration option, "noaddresses", that is intended to make it possible to bypass this address check. I have not had success using it, but it's something to bring up with the folks at Yale.

    I don't know how the NAT problem could manifest itself as an error about time synchronization. If you are still stuck you might post a question to the krbdev@mit.edu mailing list; the real Kerberos experts hang out there.

    Thanks,

    Jim Matthews
    Fetch Softworks

    Posted 12 years ago #

Topic closed

This topic has been closed.