> Make sure you have it configured to allow both SQL Server
> and Windows authentication. Looks like it might be set to
> Windows authentication only.
I found an article in MSDN telling how to change authentication
in SQL Server Management Studio. I don't have that.
I removed the password and user from the connection string.
Now it is working. Funny it didn't work to remove it yesterday.
Still not sure what the advantage of SQL Server authentication is.
Thanks.
Ralph
> -Sue
>
[quoted text clipped - 48 lines]
>>Thanks,
>>Ralph
Roger Wolter[MSFT] - 28 Dec 2005 16:48 GMT
Basically, that's because there isn't generally an advantage to SQL Server
authentication. Windows authentication is significantly more secure. There
are some application architectures that requires SQL Server authentication
but in general, if you can avoid using it, your application will be more
secure.

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
>> Make sure you have it configured to allow both SQL Server
>> and Windows authentication. Looks like it might be set to
[quoted text clipped - 62 lines]
>>>Thanks,
>>>Ralph
Sue Hoegemeier - 29 Dec 2005 05:06 GMT
You probably would want to explicitly tell the connection
string use Windows Authentication - include:
Integrated Security=SSPI
in your connection string to use Widows Authentication.
-Sue
>I found an article in MSDN telling how to change authentication
>in SQL Server Management Studio. I don't have that.
[quoted text clipped - 4 lines]
>
>Ralph
jdiego.mail@gmail.com - 29 Dec 2005 12:33 GMT
Hi All,
I had the same problem and I fixed it by enabling "SQL Server and
Windows Authentication Model"
Now I can connect by using SQL Server Management Studio Express in
local, but when I try to remote connect by using SQL Analyzer I get
error 18456.
Well, I am using a new user called 'test' for connecting SQL server. I
don't know the 'sa' password and i am confident about if it is a good
idea to change the 'sa' password.
Is 'sa' used by the system is some way?
The server is not in either: the local network, workgroup nor domain.
Therefore i am using SQL Authentication for login.
I am connecting by typing just the server IP address. It means that I
am not using the instance name (SQLExpress) at all. is that correct?
Since I can connect the SQLServer but the user is being refused, from
my point of view the problem could be:
- SQL Authentication has not been property activated for remote access
- Remote connection is not accessing to the correct instance:
SQLExpress (The only one)
- The user 'test' had not been property initialized.
Obviously I am beginner and I would appreciate you help very much.
Thanks in advance.
Diego