Help I got a strange problem trying to connect to a database

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?!

Certainly! This is not a serious problem. But... didn't I answer this question already today? hmm.. maybe that was on a different forum. anywho..... 1) seach your cmputer for the machine.config file You should have 1 file for every SDK you have on your machine. I have the .Net framework 1.0 and 1.1 on my machine so I had two machine.config files. I altered both, but you really only need to make changes to the one framework that you will compile in. 2) Double click on the file (it should open in your visual studio developer). 3) search for the field 'username' (you should find two instances). 4) the first instance of 'username' is commented out, this is merely descriptive text. 5) the second instance of username will equal 'machine', this should be changed to 'SYSTEM' This will fix your problem, however, be aware that this does open a small security hole. Your ASP.NET page now has system access. If a clever hacker finds out how to manipulate your page (don't ask me how, I'm not that clever), they will have access to your database servers. The way around this is to create an explicit trust between your db server and your web server using the machine account that is logged into the web server. Personally, I'm a little fuzzy on the details of creating an explicit trust between computers, but that information is out there. When I had a similar problem I just told a network enginner I needed a trust set up between computer a and computer b with the user id 'username' and he took care of it for me. that should fix your problem. ~TAD

1 Reply

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

Administrator23y ago
Certainly! This is not a serious problem. But... didn't I answer this question already today? hmm.. maybe that was on a different forum. anywho..... 1) seach your cmputer for the machine.config file You should have 1 file for every SDK you have on your machine. I have the .Net framework 1.0 and 1.1 on my machine so I had two machine.config files. I altered both, but you really only need to make changes to the one framework that you will compile in. 2) Double click on the file (it should open in your visual studio developer). 3) search for the field 'username' (you should find two instances). 4) the first instance of 'username' is commented out, this is merely descriptive text. 5) the second instance of username will equal 'machine', this should be changed to 'SYSTEM' This will fix your problem, however, be aware that this does open a small security hole. Your ASP.NET page now has system access. If a clever hacker finds out how to manipulate your page (don't ask me how, I'm not that clever), they will have access to your database servers. The way around this is to create an explicit trust between your db server and your web server using the machine account that is logged into the web server. Personally, I'm a little fuzzy on the details of creating an explicit trust between computers, but that information is out there. When I had a similar problem I just told a network enginner I needed a trust set up between computer a and computer b with the user id 'username' and he took care of it for me. that should fix your problem. ~TAD
+1