Re: SQL Management Studio cannot connect remotely

Since you can connect remotely by using ODBC from some other computer, the
server must be correctly configured (remote connections enabled, and
firewall has the TCP port 1433 and UDP port 1434 open). And since you are
connecting to the default instance (MSSQLSERVER) I am assuming that the SQL
Server is listening on TCP port 1433. It might be worth confirming that in
the SQL Server error log.

So I think the problem is on the client computers. One possible problem is
if the clients are not configured to use TCP. Use SQL Server Configuration
Manager on the client computer, and under SQL Native Client Configruation,
Client Protocols check that TCP/IP is enabled. And make sure it's priority
is above the Named Pipes protocol. I suspect the client is trying to connect
using Named Pipes and an IP address.
Also, try forcing a TCP connection by connecting to the IP address and the
port in the format: tcp:*.*.*.*,1433

And there are obvious TCP checks which you have probably done. Can you PING
*.*.*.* from the client?

One other possibility is that the client that does work is not using TCP.
Maybe it's using Named Pipes, and that's the protocol that is working.
SELECT net_transport FROM sys.dm_exec_connections will tell you what
protocol connections are using.
--
Rick Byham, MSFT
(Implies no warranty or rights)


"Lyria" <Lyria@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C101E5DA-2960-43D6-B160-92CE5618D29C@xxxxxxxxxxxxxxxx
No dice on either. Port 1434 was already open, and I have tried
previously
removing the /MSSQLSERVER. Tried again just to make sure tho.

Any other suggestions? As a side note, we are able to connect using ODBC
remotely through remote programs. However, we are also working on setting
up
another program that does not use ODBC to connect, and it is unable to.
Same
error is provided when we run a test with that program as we get with
Management Studio.

"Rick Byham, MSFT" wrote:

That will probably do the trick. If not, on the server computer open UDP
port 1434 for the SQL Server Browser so it can tell the client which port
the SQL Server instance is listening on.
--
Rick Byham, MSFT
(Implies no warranty or rights)

"Linchi Shea" <LinchiShea@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6EAD9840-E79A-452E-AB4F-76C26A2FBADA@xxxxxxxxxxxxxxxx
Remov \MSSQLSERVER from 'XXX.XXX.XXX.XXX\MSSQLSERVER", and try again.

Linchi

"Lyria" wrote:

Hello,

I am using MSSQL Server 2005(not express) and MSSQL Server Management
Studio
2005(also not express). The Management Studio can connect locally,
however
when connecting remotely I get the following error:

Cannot Connect to XXX.XXX.XXX.XXX\MSSQLSERVER

Additional Information:
blah blah blah ... (Provider: SQL Network Interfaces, error: 25 -
Connection
string is not valid) (Microsoft SQL Server, Error: 87).

What I have done:

I have checked my connection info on the server, using the Surface
Area
Browser. Both Named Pipes and TCP/IP are turned on. It is set to
accept
remote connections. Using the SQL Server Management Studio locally I
checked
the server settings, which reflected the same thing(remote connections
allowed).

Next I checked the firewalls. They were configured to allow the port
1433.

I have also checked the services running, and all of the SQL related
services are running, including the Server Browser.

In the Management Studio I am using the following connection
information:

Database Engine
*.*.*.*\MSSQLSERVER
SQL Server Authentication
MYUSERNAME
MYPASSWORD

In the options, I have the network protocol set to default. I have
also
tried each of the other options, each resulting in the error. Encrypt
Connection is turned off.








.

Relevant Pages

  • Re: SQL2005: Cannot connect error 11001
    ... The famous Windows Firewall (turned on my Server from which I'm trying to ... Exception Details: System.Data.SqlClient.SqlException: Login failed for user ... Try starting the SQL Server ... if you changed the port ...
    (microsoft.public.sqlserver.connect)
  • Re: network programming: how does s.accept() work?
    ... The program you contact at Google is a server. ... so, the server will usually assign a new port, say 56399, specifically ... connections to a server remain on the same port, ... sockets is what identifies them. ...
    (comp.lang.python)
  • Nimda.E/unknown memory resident, internet-aware processes
    ... a client's NT 4.0 server was infected with what appeared to be ... network traffic and saw several suspect connections. ... one other connection to port 2787. ... along with about 500 other compromised systems on just that one IRC server. ...
    (Incidents)
  • Re: VB app connect THROUGH proxy to a remote SQL database
    ... The whole "HTTP proxy is way more secure than allowing outgoing ... the client app and the SQL server are on ... incoming connections to the SQL server are not the problem - it's ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... If I cut the maximum number of connections to for ... SQL Server simply blocks any further try to open another table until I close ... This doesn't happen with the SQL Server 2000 but with SQL Server ... No, I think ms-sql-s means that SQL 2000 is using port 1433, which is ...
    (microsoft.public.sqlserver.connect)
Quantcast