NTAUTHORITY\NET SERVICE not authorized

  • Thread starter Thread starter ChuckD_Duncan
  • Start date Start date
C

ChuckD_Duncan

(Platform: 2003 or XP, IIS) From a Web Service, I have a sqlConnection with
a correct (tested) connection string. When I try to
myConn.Open();
it fails with NTAUTHORITY\NET SERVICE not authorized... meaning it seems
to be looking for that in the SQL users list. However, I can't find such
an account in the system to add to the database security.
Somehow I have a combination of DejaVu and Alzheimer's .... appreciate
your help.

Thanks in advance.
Chuck Duncan
 
CORRECTION:
That should be: NT AUTHORITY\NETWORK SERVICE

Do I just "Create" this in the SQL Logins even though it doesn't exist in
the NT system?
 
Hi,

This is the default nt account under which your webservice runs.
And you have set windows authentication in your connection string.
Thus webservice tries with its account.
Is Sql server on the same machine?
 
I have tried it with SQL on the same and on different machines... same
problem. I am surprised that I cannot seem to find that account anywhere
so I can add it to the database.
 
Did you try adding "NT AUTHORITY\NETWORK SERVICE" (without quotes) user to
sql server? Note that this account doesn't appear in available user list.
Other possibility is to create a new application pool (on the IIS) and
assign it a certain user account (Make sure your web application uses this
new pool). This account will be used for connection to sql server then.
 
I did try adding NT AUTHORITY\NETWORK SERVICE which I thought might work
too, but it just said it doesn't exist. Isn't it a different account on
2003 ??
As for the rest of your suggestion, I'm afraid you are way beyond me on
that. I don't know how to do any of those.
The problem is that when I try to create a web application or service in
Visual Studio, it tries to do it using the NT AUTHORITY... account so if I
don't get that working, then I am going to be stuck even creating the
project.
 
BTW, I WAS ABLE to add NT AUTHORITY\NETWORK SERVICE on a XP system just
fine. So it must be something unique to 2003 ??
 
The issue is really getting the app or service built in the first place...
without VStudio 2003 throwing up. You can't modify config files that
don't exist yet... see my problem?
 
Back
Top