How to influence who the User is

[Guest]

I have an ASP.NET application that was ported from a server where IIS, the
database (SQL Server 2000) and web application were on the same server.

The new server is a Windows 2003 (Webserver edition) and the database server
is a Windows 2003 (SMB edition) (also SQL Server 2000).

The application uses sql data adapters and sql command object to access the
database. The connection string is correct. When I run the application, I
get the error message that . . . "Login for WebDell$ failed." WebDell is the
name of the webserver.

Event though WebDell$ does not show up as a Windows users, I explicitly
added it to the SQL Server Login and granted access to the database as dbo.
When I run the application, the login succeeds but the error states that
"access to the catalogue = "DMS" is denied.

How do we influence what user an ASP.NET application runs as? Where does
the WebDell$ user come from?

WR

PS: Given the innumerable possible configurations that exists, I may have
not included enough information, but I am hoping some recognizes this problem.

 

[Alec MacLean]

Hi WhiskyRomeo,

I would guess that your WebDell$ may be the account being used by IIS for
anonymous access. You can check this on the security properties page of the
web site in the IIS MMC console.

I would perhaps suggest that you create a separate SQL account and a DB
Role, then add the SQL account as a member of the Role. The SQL user would
need to be a member of public (by default), and access to the DBO. The Role
would have execute rights to your sprocs.

You would need to update your connection string to use the new SQL account
values.

Hope this helps.

Al