Actually, just figured it out. SQL Server's picking up the connection as 'Microsoft Data Access Components'. Our login trigger's screening applications like '%ACCESS%'...

thanks for looking.. 😀