Re: Can't connect to SQL Server, using Windows Authentication users of SQL server? help

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Reza (uwhockey_at_hotmail.com)
Date: 06/07/04 

Date: Mon, 7 Jun 2004 07:31:04 -0700

Greg,

Thanks for taking the time and explaining all the details.

I turned off the annoymous access, also checked the server/client utility of the sever. Looks like tcp/ip and network pipes are both there. Yes I am using the windows authentication security of .net with list of users in my web.config, thus didn't prompt for login. Just an extra detail that might help, when I use trusted_connection in my connection string, and have the aspnet user added to the database, I am able to connect without any problem, only this is not an option for me

However, I still have the same problem?

Reza
     
     ----- Cowboy (Gregory A. Beamer) [MVP] wrote: -----
     
     I apologize if I am getting too simple, but the background theory is
     important.
     
     There are two ways of connecting to SQL Server
     
     1. Windows auth, which uses windows built-in security
     2. Mixed mode, which uses a name/password combo in SQL Server
     
     It sounds like you wish to use Windows auth, which is fine. The problem,
     however, is the user logs into a web app as an anon user unless you force
     authentication. The easiest way to do this is open the Internet Services
     Manager and remove anonymous access. Now, you know who the user is and
     everything works fine. Of course, this will also bring up a dialog box for a
     user to log into windows for the web app.
     
     ADDED INFO:
     ----------------
     I just saw your OSql info in your followup. While it does not "change" the
     above advice, there is one more component to consider and that is network
     libraries. It is possible you are trying to connect with named pipes (top of
     connection stack on both client and server). You may not even have the
     TCP/IP network library installed (while not absolutely necessary, it
     simplifies things tremendously).
     
     You can check network libraries on the SQL Server machine by opening the
     server network library tools. If you do not see TCP/IP, you should
     "re-install" SQL Server and add the components. The installer should only
     add the library, but I advise database backup any time you are tinking with
     the server install utility. I have never had a problem here, but an ounce of
     prevention is worth a pound of cure.
     
     On the client, if you have SQL tools installed, you can check the network
     libs as well. On both server and client, move TCP/IP to the top of the
     stack.
     
     If this still does not work, follow up with another post.
     
     --
     Gregory A. Beamer
     MVP; MCP: +I, SE, SD, DBA
     
     ************************************************
     Think Outside the Box!
     ************************************************
     "Reza" <uwhockey@hotmail.com> wrote in message
     news:4EFCB397-4A9E-4C21-AA4C-0387FEAA7B8F@microsoft.com...
> Hello,
>> I tried this friday, but didn't get anywhere so trying again.
> Basically, I have a fixed list of people that can access the application
     in the Intranet, and with the policy of the company the Users can be created
     only with Windows authentication in SQL Server - with SQL server
     authentication have no problem.
> So every time I try to connect get the error message, "Login failed for
     user, 'username'."
> I have also tried windows authentication of .net with different setting,
     but still the same problem.
>> A help would be greatly apreciated since I am stuck because of this,
>> Thanks in advance,
> Reza
     
     
     
     

Quantcast