October 5, 2015 at 2:56 am
Just started getting the NT Authority\Anonymous Logon failure but not sure why.
1) SSIS package running on server B invoking SP via db on server A to retrieve data, was working fine for ages, then last week failing to run and interrogating the package itself the user the connection it uses fails to logon.
2) My own account (Sysadmin) from my laptop trying to invoke the SP on server A very intermittently works, but mostly now fails with NT Authority\Anonymous Logon failure. Again previously as far as I can tell this was fine.
What changes have been made recently?
The only significant things are
a) Added a Linked server reference from server A to another unrelated server in all this, server C. (That aspect and the 4 part synonym names being used are working fine).
b) Some work is going on, on the domain, but server A is not on the domain as such, whereas server B and my laptop is. But not sure what questions to ask as to what might have been changed (if at all) to impact this.
One thing I did note was on SQL Server 2005 Surface Area Configuration the Database Engine remote connections was stating Local and Remote Connections for 'Using TCP/IP only. as opposed to Using both TCP/IP and named pipes.
So the question is, what might have happened to make this now not work?
October 6, 2015 at 6:54 am
This is more obscure than I thought.
The problem appears to only apply to one database in the instance.
The rest can be accessed ok remotely?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply