Client Problems

Hello:

I have an instance of SQL Express in my Server with the necesary configurations(enabling TCP/IP connections).

The problem is: with .udl files, I can create a connections very well in other machines, but, I my Win application can′t connect to the server. My connections string is:

"Data Source=192.168.1.106\SQLEXPRESS;Initial Catalog=Products;User ID=sa;Password=sqlsa"

I installed SQL Native Client in the machines where my application is executed (sqlncli.msi).

Thanks

Do you have SQL Browser running on the remote computer and an Exception created in the remote computers firewall? SQL Browser is required to enumerate the named instances on a server. Check out the FAQ at the top of this forum for a pointer to instructions about remote connections.

Mike

|||

Yes I have the SQL Browser running. But, the problem is in the clients. Could be a SQL Native Client?

|||

Hi,

I got the same problem.

I think this is a taff problem when connecting to remote comp from .net application

I use:

Data Source=MYREMOTESVR\SQLEXPRESS;Initial Catalog=microDB;Integrated Security=SSPI;Persist Security Info=True;User ID=micro;Password=micro

OR

Data Source=MYREMOTESVR\SQLEXPRESS;Initial Catalog=microdb;Integrated Security=True;Persist Security Info=True;User ID=micro;Password=micro

And found EROR message when running aplication from client comp.

"... Login failed foruser MYCOMP\Guest... "

Anyone can help us?

regards.

md5

|||

hi,

MD5 wrote:

Data Source=MYREMOTESVR\SQLEXPRESS;Initial Catalog=microdb;Integrated Security=True;Persist Security Info=True;User ID=micro;Password=micro

And found EROR message when running aplication from client comp.

"... Login failed foruser MYCOMP\Guest... "

actually you pass to much info to your connection string.. the connection can be "trusted" or "not", but not both.. in this case, as you pass both, SQLExpress uses integrated security, and the "guest" (Windows OS based) login is (fortunately) not granted access to the SQLExpress instance..

so you have to choose waht you want..

integrated security (Integrated Security=True

OR

standard SQL Server authentication (User ID=micro;Password=micro

?

regards