Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / General / February 2006

Tip: Looking for answers? Try searching our database.

How to influence who the User is

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
WhiskyRomeo - 13 Feb 2006 20:37 GMT
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 - 13 Feb 2006 21:59 GMT
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

>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.
[quoted text clipped - 25 lines]
> not included enough information, but I am hoping some recognizes this
> problem.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.