I'm in the process of setting up a new SQL environment.
Server SQL1 is hosting SQL Server.
Server SSIS1 is running Integration Services.
Client 1 is running SSMS.
SQL Server and Integration Services are both running as the same active directory user: DBServiceAcct.
DBServiceAcct is a local admin on both servers, and is explicitly defined as a sysadmin on SQL1.
I have modified MsDtsSrvr.ini.xml on the SSIS1 to point to SQL1.
I have configured SQL1 to automatically create SPN's on startup in order to connect with kerberos authentication and I have verified it is working properly.
If I RDP with my own AD Credentials to SSIS1, launch SSMS "as administrator", and connect to Integration services on SSIS1 I can expand out the MSDB folder. A SQL Trace verifies that I am connecting to SQL1 as myself.
If I launch SSMS on my local PC (Client 1) logged in as myself, and connect to SSIS1 I get a failure when I expand the MDSB folder.
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (MsDtsSrvr)
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. (Microsoft SQL Server Native Client 11.0)