This discussion is locked
EvilCsnikneJ

Q: Login aborted by the client

I have several OSX 10.5.8 systems that this happens to - and several others that work just fine:

All can download and Install the FCS client without any trouble, and the FCS Client shows the login screen - but on some of the clients a login attempt results in the message "Login aborted by the Client"

Software update reports everything up to date on all systems, including the FCServer itself - which is also running on OSX 10.5.8

Has anyone any ideas on what may be causing this? I have scoured the web, and this site for any hint of what may be going on - but so far I am stuck.

All systems are on the same gigabit switch, I do not see much in the FC Server logs that seems related, or the Apache logs. Running a Java console reveals the following error line:

ec 8, 2010 1:37:01 PM com.apple.FinalCutServer.javaui.LoginDialog$6 actionPerformed
WARNING: couldn't determine AUTH_TYPE, defaulting to PPS


But I have no idea what that really means.

Anyone willing to help?

Cheers Clive

MacPro / Various, Mac OS X (10.5.8)

Posted on Dec 7, 2010 6:38 PM

Close

Q: Login aborted by the client

  • All replies
  • Helpful answers

  • by John F. Whitehead,Helpful

    John F. Whitehead John F. Whitehead Dec 7, 2010 8:35 PM in response to EvilCsnikneJ
    Level 2 (380 points)
    Dec 7, 2010 8:35 PM in response to EvilCsnikneJ
    It can't figure out how to authenticate to the directory server.

    Make sure you are bound correctly on those machines, and that you're up to date on Java.
  • by EvilCsnikneJ,

    EvilCsnikneJ EvilCsnikneJ Dec 7, 2010 9:49 PM in response to John F. Whitehead
    Level 1 (0 points)
    Dec 7, 2010 9:49 PM in response to John F. Whitehead
    Ah - so it's an OSX Network configuration problem. I see. Thank you.

    So does this imply that I must have OSX Server for authentication and that I am required to bind all these systems into a domain?

    Can I not simply use local authentication without having them all bound to a server?

    Many thanks,
    Clive
  • by John F. Whitehead,

    John F. Whitehead John F. Whitehead Dec 7, 2010 11:38 PM in response to EvilCsnikneJ
    Level 2 (380 points)
    Dec 7, 2010 11:38 PM in response to EvilCsnikneJ
    You can use local auth, in which case you don't have to worry about domains. I didn't know if you were using Open Directory or Active Directory.

    Do all the users have accounts on the server? You can test that it's not their computer but a user issue by logging in as someone else from their computer.
  • by EvilCsnikneJ,

    EvilCsnikneJ EvilCsnikneJ Dec 8, 2010 3:12 PM in response to John F. Whitehead
    Level 1 (0 points)
    Dec 8, 2010 3:12 PM in response to John F. Whitehead
    Hi John,

    I really appreciate your responses, thanks.

    Basically, I have a setup with no OSX server - FCS is installed on OSX Workstation - but that's all this machine does is handle FCS.

    There are local individual OSX user accounts setup on the FCS System, and each is assigned to a local group, all of these are given different permissions in FCS software itself.

    I can connect the FCS Client without any problem from several of the other computers in our facility - we have about 20 OSX systems that need access to FCS. But, as I mentioned, quite a few give this error when trying to connect with the client.

    I am not very wise in the ways of OSX - and if I have to buy OSX Server to get this going, well - so be it, but I am trying to avoid it.

    I have had no trouble getting our Storage systems mounted and working on all our systems - and all of our Windows computers can connect to FCS without any problems at all.

    Local Auth is just fine for us - these systems can be managed without resorting to an NIS type setup.

    Is there a setting in Apache that I would need to change to allow local auth to take effect?

    Many thanks for your helpful advice.

    Clive
  • by John F. Whitehead,Helpful

    John F. Whitehead John F. Whitehead Dec 8, 2010 6:07 PM in response to EvilCsnikneJ
    Level 2 (380 points)
    Dec 8, 2010 6:07 PM in response to EvilCsnikneJ
    If you don't have OD or AD, then you are using local auth. Apache isn't relevant (b/c you're talking about problems using the client, not problems trying to download it, I believe).

    I'd make sure Java is current, and clear out its prefs if you need to. After that, all I can suggest is looking more closely to find the difference between those that work and those that don't.
  • by EvilCsnikneJ,

    EvilCsnikneJ EvilCsnikneJ Dec 8, 2010 6:48 PM in response to John F. Whitehead
    Level 1 (0 points)
    Dec 8, 2010 6:48 PM in response to John F. Whitehead
    Ah - OK. Thanks.

    I already made sure that Java is up to date, and tried dumping all the java cache and removing the client, etc. I have no problem downloading and running the client - it just fails at the Client login stage - it doesn't seem to matter what user I enter, it will always fail with the 'aborted by client' message.

    I will move on to try and find out what the difference is between the ones that connect and the ones that cannot.

    Many thanks,
    Clive
  • by EvilCsnikneJ,

    EvilCsnikneJ EvilCsnikneJ Dec 13, 2010 8:50 PM in response to EvilCsnikneJ
    Level 1 (0 points)
    Dec 13, 2010 8:50 PM in response to EvilCsnikneJ
    I just thought I would follow up on this, and note here that my issue has been resolved.

    Solution was to get the OSX Install disk, and perform an "Archive & Install", then apply all updates to get it back to 10.5.8 - voila! After installing FCS Client, all is fine.

    Something nasty must have been lurking in the OSX system files on these machines. In case anyone suffers from similar problems in future, it may be a reasonable solution for them - although I must admit that installing the updates - particularly the OSX-10.5.8-Combo can be a frustratingly painful process.

    Regards,
    Clive