Help I got a strange problem

Administrator

I got a weird problem that I hope can be fixed. Im creating an ASP.Net page which will allow users to create a game account for a Game Server that I'm planning to build within the following year. The game accounts will be stored on a database on my computer. I have already written a windows version of the Account manager which allows people to create/edit/or get a password reminder. The problem is that when I try to open an sqlConnection it gives the following error System.Data.SqlClient.SqlException: Login failed for user 'BRANDON\ASPNET'. at System.Data.SqlClient.SqlConection.Open() ... The connection strings for the windows version and the ASP.NET version are identical so what could be the problem. Here is what the connection string is for both versions this.m_sqlConnection.ConnectionString = "data source=(local)\\NetSDK;initial catalog=Game Server;integrated security=SSPI;persist security info=False;workstation id=BRANDON;packet size=4096"; Does anyone have any idea what could be causing this problem?!!

2 Replies

Know the answer? Post it — somebody with the same question will find it here.

Administrator23y ago
Hi, I gave up trying to get Windows authentication going, it just meant too many calls to the support desk to get accounts and permissions set up. On SqlServer, I created explicit user accounts and pass those in with my connection string: "server=localhost;uid=MyUser;pwd=MyPassword;database=TX360C1Build7" I also use the SqlHelper app block to reduce the amount of typing I have to do. Cheers,
Administrator23y ago
This is a bit of a reach, but I think you need to check your credentials and how they are passed. In your WinForm version the current windows administrator is passing your credentials back to the SQL Server. In you WebForm version IIS is passing your credentials. I would make sure that you IIS administrator is also an administrator to you SQL server connection. But of course, typically your IIS admin is the same user as your windows admin so there is only a slim chance that this is the real problem. Also, one other thing you may want to check into is you .NET web security settings. Here is a web page that may help http://www.ntsecurity.net/Articles/Index.cfm?ArticleID=9002 It's not much, but the page does describe in detail how web page security interacts with SQL server 7 and how user names and passwords should be passed because of certain trusts that must exist between SQL server and whatever is trying to log in. Ultimately, if all else fails, create and ODBC connection and then have your web page use that ODBC connection for communication.