Definitely an issue with Kerberos. 
I had the same problem and after doing some troubleshooting, found out that the package would run successfully if ran from an SSMS installed on the server, but would fail to run if ran from an SSMS client outside the server. This is a double hop issue. 

Going to try out Microsoft's Kerberos config manager and see if that fixes the issue. 
https://www.microsoft.com/en-us/download/details.aspx?id=39046