Re: can't connect to sql server with domain users? Help....

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


Date: Fri, 4 Jun 2004 13:16:02 -0700

Well I thought I had resolved this, but looks like this company's policy not allows sql authentication for the users, so I am back to step one.
It works for aspnet user, however, there is a fix list of people that will be able to access it, which they belong to a domain.
and looks like I get the same message, login failed for user 'username'?

     
     ----- Martin Marinov wrote: -----
     
     Now when you change it to sql and windows authentication you have to add the
     aspnet user to the database and use Integrated Security=True
     
     Regards
     Martin
     
     "Reza" <anonymous@discussions.microsoft.com> wrote in message
     news:EE20B721-6D8E-45F9-8216-826C58A3FADD@microsoft.com...
> Martin,
>> I get the same message when I tried your suggestion. Looks like it is
     complaining that there is not a secure connection. How do I do this? I
     changed the authenticaion to both, SQL and windows, but still the same
     thing!
>> Any idea?
>> thanks,
> reza
>> ----- Martin Marinov wrote: -----
>> Have you tried to connect with sql query analizer with your username
     and
> password
> if you don't have query analizer try this:
>> osql -U yourusername -P password -S servername -d database
>> if this is failed to than you don't have sql authentication to your
     server
>> Regards
> Martin
>> "Reza" <anonymous@discussions.microsoft.com> wrote in message
> news:ADFEE77D-2ADD-4ED9-AF72-4E6ACB7CD423@microsoft.com...
>> Yes, I tried both of these, but no luck. I tried with domain name
     and
> without. Tried the trusted connection, Integrated Security=True, but
     still
> the same problem - Login failed for user 'username'!
>>> ----- Martin Marinov wrote: -----
>>> are you sure that in the connection string the user is
> DOMAINNAME\USERNAME ?
>> have you tried by connection like this:
>>> server=servername;database=databasename;Integrated
     Security=True
>>> Regards,
>> Martin
>>>> "Reza" <uwhockey@hotmail.com> wrote in message
>> news:B692F699-0808-4276-987D-CD866271C3E5@microsoft.com...
>>> Hello,
>>>> The project was working, where I had a domain user registered in
> the
>> database as a user, and I used that user to connect the
     datebase.
> Everything
>> was fine and it was working, then when I moved the project to
     the
> production
>> servers - database server and web server. Following that all
     the
> users are
>> failing to connct to database, getting this message:
>>> "login failed for user 'username'"
>>>> I am getting the user with property identity and it is registered
>> identically in the database user list.
>>>> I am pretty much stuck and ran out of ideas to try. So a
> resolution will
>> be greatly apreciated.
>>>> Thanks in advance,
>>>> Reza
>>>>



Relevant Pages

  • Re: crash on virtual dimensions
    ... SQL authentication doesn't work for SQL Server to anywhere. ... It is basically a way for access developers to start writing all of their ...
    (microsoft.public.sqlserver.olap)
  • Re: Failed to connect to SQL express on LAN
    ... Although I wrote that SQL Authentication worked with the sa account, ... I went on the DELL8300 server and tried to enable nore server roles for the ... For SQL Authentication, from your test, I think that SQL Authentication was ...
    (microsoft.public.sqlserver.connect)
  • Re: Permissions Issue
    ... If the problem is permissions, then enabling auditing should let you see the ... If the SQL client is running this application across the network using Named ... Pipes or Multi-Protocol to connect to the SQL server with SQL authentication ...
    (microsoft.public.win2000.security)
  • Re: Problems when trying to build Connection to SQL Server Express from ASP.NET application
    ... Your connection string contains a mix of both SQL authentication and Windows ... It looks like you want to use SQL Authentication so specify 'user01' and the ...
    (comp.databases.ms-sqlserver)
  • RE: [dbi] prepared insert syntax error on exec
    ... > to change the SQL ... Yada, yada, yada... ... sender who is duly authorised to do so on behalf of the Institute. ... > Martin J. Evans ...
    (perl.dbi.users)