J
John J. Hughes II
I have "Computer A" which is running Win2K3 and MS SQL server. And
"Computer B" which is running a service that I have created. If I change
the service on "Computer B" to run as a user my program is able to connect
to the SQL server on "Computer A" correctly. But if I set the service on
"Computer B" to run as a local system then I get an error connecting to the
SQL on "Computer A" --- "NT AUTHORITY\ANONYMOUS LOGON". I understand why I
have the error but would prefer to keep the service set to local system
rather then running it under a user account.
So the question is how to either reconfigure the SqlConnection connection
string so the user is not anonymous or to tell the SQL server it's ok for
this computer to log in. I don't want to allow anonymous log in to my SQL
server obivously but I am not really happy about using the SQL user name and
password either.
Thanks in advance,
John
"Computer B" which is running a service that I have created. If I change
the service on "Computer B" to run as a user my program is able to connect
to the SQL server on "Computer A" correctly. But if I set the service on
"Computer B" to run as a local system then I get an error connecting to the
SQL on "Computer A" --- "NT AUTHORITY\ANONYMOUS LOGON". I understand why I
have the error but would prefer to keep the service set to local system
rather then running it under a user account.
So the question is how to either reconfigure the SqlConnection connection
string so the user is not anonymous or to tell the SQL server it's ok for
this computer to log in. I don't want to allow anonymous log in to my SQL
server obivously but I am not really happy about using the SQL user name and
password either.
Thanks in advance,
John