Client cannot connect to SQL Server

[shaminda]

Here is a scenario. A client named LONDON is trying to connect to the server named ROME (Windows 2000). The ROME server has SQL Server 2000 running. The user on LONDON is Charles. And Charles is a member of ‘Users’ on the ROME server. And Charles is also the database owner of a database on SQL Server called dbShipping. For some reason Charles cannot connect to the SQL Sever using sequel authentication. Why can’t Charles connect to the SQL Server? If I make Charles an Administrator he might be able to connect because I have done this in the past. But I really don’t want to make Charles an Administrator.

On the domain controller which has active directory Charles is a user. The server ROME is part of the domain.

 

[SQLBill]

Has Charles created an ODBC connection?

Is Charles login on SQL Server set to use SQL Authentication?

Is the SQL Server set to allow SQL Authentication?

-SQLBill

 

[shaminda]

Charles is connecting using .ini file so it does not use ODBC

Yes Charles is trying to login using SQL Authentication

How do I set SQL server to Allow SQL Authentication?

 

[Corran007]

On the server properties under the security tab. radio button for server and windows or windows only.

 

[timscronin]

See if he can download copy of sql client tools and see if he can use qa to connect to server. You may need to add the server to the host file on the local machine if DNS not working properly. See if you can ping the db server name from dos prompt of client

 

[SQLBill]

Check his LOGIN in Enterprise Manager (drill down to Security, click on Logins, right click on Charles' login, select Properties). SQL Server Authentication should be selected. Charles should also have a password entered.

-SQLBill