I am trying to connect to a remote 2005 SQL server “A” from my 2005 SQL Server Management Studio on a different network. I have opened up port 1433 on the remote server A. I have made sure that “Allow remote connections to this server” is checked on the remote server properties under connections. I have also chosen “Using both TCP/IP and named pipes” under Remote Connections in the SQL Server 2005 Surface Area Configuration.
I am using \\xxx.xxx.xxx.xxx\sqlservername and user sa to connect. I get the following error: “An error has occurred while establishing a connection to the server. When connecting to the SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 5 – Invalid parameter(s) found) (Microsoft SQL Server, Error:87)”
If I take out the \\ from the server path I get an error that the server not found. So I think I am getting to the server.
I have run SQL profiler and there is no event or failed login on the remote server when I try to connect to SQL server A. SQL Server A is on Windows2003 with all current patches. I have tried connecting from Windows XP pro and Windows2003 server.
Is this a network issue, Windows2003 issue, or a SQL issue?
If the server path starts with \\ the client stack assumes the connection is intended over Named Pipes, which requires the full pipe name specification, which is not the case in the above example, hence, the error "Invalid parameter(s) found".
The solution depends on whether the SQL Server is installed as a "default" or a "named" instance:
(1) For a default instance: specify the server by either (a) the server's machine name only (no \\ or \), or (b) the server machine's IP address only (again, no \\ or \).
(2) For a "named" instance:
- specify the server as either (a) machineName\instanceName, or (b) ipAddress\instanceName. Note that if you installed the Express edition it is installed as named instance with name SQLEXPRESS by default.
- grant firewall expection for the sqlservr.exe processes.
- start SQL Browser service on the server's machine.
- grant firewall expection for the sqlbrowser.exe processes.
|||This worked! Thank you!|||
I also can't connect to my SQL Server Express, running on xxx.xxx.xxx.xxx. I tryed out everything! F***
Could you write out a complete connection string, pls? I tryed:
string strConn = "Data Source=xxx.xxx.xxx.xxx; Initial Catalog=table; Connect Timeout=30; User ID=xxxxxxx; Password=xxxxxxx;";
string strConn = "Data Source=servername; Initial Catalog=table; Connect Timeout=30; User ID=xxxxxxx; Password=xxxxxxx;";
|||
I am facing a similar problem.
I have Microsoft SQL Server 2005 Express (Named Instance:=01HW050876\SQLEXPRESS) in my machine (OS : Windows XP). I am using ADO in Visual Basic 6 to connect to the database. I use SQL Server Authentication to connect to ther server. It works fine if I connect from my machine. However, if i try to connect from a different machine I get the following error:
Unhandled Error [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
Here is my connection string:
Public Const CONNECT_STRING_SQL As String = "PROVIDER=SQLOLEDB.1;SERVER=01HW050876\SQLEXPRESS;UID=user;PWD=sqlpwd;DATABASE=SalesWindow"
I have also used the Ip address
Public Const CONNECT_STRING_SQL As String = "PROVIDER=SQLOLEDB.1;SERVER=xxx.xxx.xxx.xxx\SQLEXPRESS;UID=user;PWD=sqlpwd;DATABASE=SalesWindow"
The other computer is also in the same network and I was able to ping my machine from there. I have also set the login mode of the SQLServer to Mixed mode in the registry and have added the user from the other machine to the database and have given access rights.
Could you help me to track down the problem
|||Shasur
This blog can help you.
http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
No comments:
Post a Comment