Unable to access MSSQLSERVER from client

Hot Topic

logging DDL Stmts
Setting Passwords In Connections Using Script Task
how can I deal with character of hard return?
sql server 2000
Buffer Leaks
Problem with Client Side Printing
Problem with ODBC Source
Printing Problem
Editor
Add a column to a table.

SQL Server

Returning results to MSMQ from SSIS Package
Advenced select
Need Help For SSIS Package Creation With INSERT,UPDATE Large Amount of Records Through Business Intelligence studio
Appending to a recordset destination
Custom connection manager development sample?
Calculated Measures using AMO
What accounts for this performance difference?
rename a file without xp_cmdshell
Problem with select into querry
Exception of type 'System.OutOfMemoryException' was thrown. (Microsoft.SqlServer.SmoEnum)

Unable to access MSSQLSERVER from client

Hi,

I have SQL Server 2005 installed and functioning (it does everything I've asked it to do locally). I also have the Express and Standard Editions installed on a computer running WinXPPro SP2 with all the WinUpdates applied. I also have VS2005 installed on this computer. I've done some development work on this computer, using VS2005 to create a SQLDB, connect to it, add data, etc. This is all okay.

The problem is I cannot connect to the SQL Server from the client computer. I installed the client tools on this XP Pro box along with all the WinUpdates. Here's what I can do...

I can ping the SQL Server by name (the name gets resolved).
I can copy files between the two computers using Explorer.
I enabled "Allow remote connections to this server" in the Server Properties / Connections page.
I did not change the default port of 1433.
The TCP/IP protocal is enabled in the Configuration Manager.
The Surface Area has been configured to allow local and remote connections using TCP/IP and named pipes.
SQLBrowser surface is running as is the MSSQLSERVER service.

So what's going on I am new to SQL Server to it may be something very simple / obvious.

Thanks for your help,
Scott

 

Answer this question

Unable to access MSSQLSERVER from client

  • NehaRahul

     WesleyB wrote:
    It looks like you are using Integrated Security
    My best guess is that the client you are trying to connect with is using a user that has no rights on the SQL Server.

    uhh ... OK, sure makes sense.  Can we fix that   Don't all clients connect as the 'guest' account



  • Chubbly Geezer

    when logging in from the client, I get the following message. "Cannot connect to tcp:Precision_m70. Additional information: Login failed for user. The user is not associated with a trusted SQL server connection. (Microsoft SQL Server, Error: 18452)"

    I tried connecting using the following; tcp:precision_m70,1433... I also tried withour entering the port number since 1433 is the default. I tried uppercase and lowercase but no luck.

    Thanks,
    Scott

  • kent_

    Everything depends on how the application is connecting to the SQL Server.

    When using Integrated Security you are passing the Domain User of the workstation to SQL Server. You can give permissions to the Domain User(s) to your target database. Or you can enable Mixed Mode authentication to be able to work with a SQL user. But keep in mind that Windows Only authentication is the preferred method.

    hth

  • Phluxed

    It looks like you are using Integrated Security
    My best guess is that the client you are trying to connect with is using a user that has no rights on the SQL Server.

    Or you are trying to use a SQL user while Windows Only is enabled on the SQL Server.
  • Unable to access MSSQLSERVER from client
Answer this question