unable to connect to sql server remotely

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Matt - 28 Nov 2007 16:03 GMT

Here is my issue. I installed SQL 2005 on one of my servers. Up until 10 minutes ago I was able to connect to the server remotely using SQL Server Management Studio but I was unable connect to the SQL server from the actual server that the SQL 05 instance resides on. Now, I restarted the SQL Server, and DB engine service and now I can connect to the SQL database from the actual server but not remotely. I have it configured to allow remote connections and have it setup to use TCP/IP or Named Pipes and still nothing. I've restarted the db engine service and all of the other SQL services and I still can't connect to it remotely.

Any suggestions on what could be causing this? I get this error when I try to connect remotely:

'An error has occurred while establishing a connection to the server. When connecting SQL Server 2005, this failure may be caused by the fact that under the default settign SQL does not allow remote connections....'

Now I also got that same error message when I logged onto the actual server that the SQL 2005 instance resides. I did fix that and now I'm able to log in to SQL SMS from the actual server but not remotely.

Reply to this Message

Andrew J. Kelly - 28 Nov 2007 17:54 GMT

Did you change the tcpip address or the port sql server is using? Is it a default or named instance?

Signature

Andrew J. Kelly SQL MVP
Solid Quality Mentors

Reply to this Message

Ekrem Önsoy - 28 Nov 2007 18:06 GMT

As far as I understand Matt says that he can not connect to his SQL Server instance from the SQL Server server itself either if I understand him correctly.

If this is the case, I suggest you to forget about the remote connection for this moment and ensure that SQL Server service runs or not. Check out the Event Logs if there is any related error messages. After solving this problem, we can go further.

Let me know if I'm wrong.

Signature

Ekrem Önsoy

Did you change the tcpip address or the port sql server is using? Is it a default or named instance?

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors

"Matt" <Matt@community.nospam.com> wrote in message news:uoLB5gdMIHA.4912@TK2MSFTNGP06.phx.gbl...
Here is my issue. I installed SQL 2005 on one of my servers. Up until 10 minutes ago I was able to connect to the server remotely using SQL Server Management Studio but I was unable connect to the SQL server from the actual server that the SQL 05 instance resides on. Now, I restarted the SQL Server, and DB engine service and now I can connect to the SQL database from the actual server but not remotely. I have it configured to allow remote connections and have it setup to use TCP/IP or Named Pipes and still nothing. I've restarted the db engine service and all of the other SQL services and I still can't connect to it remotely.

Any suggestions on what could be causing this? I get this error when I try to connect remotely:

'An error has occurred while establishing a connection to the server. When connecting SQL Server 2005, this failure may be caused by the fact that under the default settign SQL does not allow remote connections....'

Now I also got that same error message when I logged onto the actual server that the SQL 2005 instance resides. I did fix that and now I'm able to log in to SQL SMS from the actual server but not remotely.

Reply to this Message

Matt - 28 Nov 2007 18:48 GMT

I'm able to connect to the SQL Server when I log onto the server directly. I open up SMS and I'm able to connect. There are no errors in the event viewer on the server for this issue.

Now when I open up SMS on my computer and try to connect to the SQL server such as (SQLServer1\Development) I get the error message that I posted in my first post.

As far as I understand Matt says that he can not connect to his SQL Server instance from the SQL Server server itself either if I understand him correctly.

If this is the case, I suggest you to forget about the remote connection for this moment and ensure that SQL Server service runs or not. Check out the Event Logs if there is any related error messages. After solving this problem, we can go further.

Let me know if I'm wrong.

--
Ekrem Önsoy

"Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:O9SF2eeMIHA.3940@TK2MSFTNGP05.phx.gbl...
Did you change the tcpip address or the port sql server is using? Is it a default or named instance?

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors

"Matt" <Matt@community.nospam.com> wrote in message news:uoLB5gdMIHA.4912@TK2MSFTNGP06.phx.gbl...
Here is my issue. I installed SQL 2005 on one of my servers. Up until 10 minutes ago I was able to connect to the server remotely using SQL Server Management Studio but I was unable connect to the SQL server from the actual server that the SQL 05 instance resides on. Now, I restarted the SQL Server, and DB engine service and now I can connect to the SQL database from the actual server but not remotely. I have it configured to allow remote connections and have it setup to use TCP/IP or Named Pipes and still nothing. I've restarted the db engine service and all of the other SQL services and I still can't connect to it remotely.

Any suggestions on what could be causing this? I get this error when I try to connect remotely:

'An error has occurred while establishing a connection to the server. When connecting SQL Server 2005, this failure may be caused by the fact that under the default settign SQL does not allow remote connections....'

Now I also got that same error message when I logged onto the actual server that the SQL 2005 instance resides. I did fix that and now I'm able to log in to SQL SMS from the actual server but not remotely.

Reply to this Message

Matt - 28 Nov 2007 19:35 GMT

OK, now I'm a little confused. I still cannot connect to my SQL 05 instance using a remote connection, however, I am able to connect to the integration service on the SQL server I'm trying to connect to.

Does the SSIS process run under a process outside of SQL Server itself?
As far as I understand Matt says that he can not connect to his SQL Server instance from the SQL Server server itself either if I understand him correctly.

If this is the case, I suggest you to forget about the remote connection for this moment and ensure that SQL Server service runs or not. Check out the Event Logs if there is any related error messages. After solving this problem, we can go further.

Let me know if I'm wrong.

--
Ekrem Önsoy

"Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:O9SF2eeMIHA.3940@TK2MSFTNGP05.phx.gbl...
Did you change the tcpip address or the port sql server is using? Is it a default or named instance?

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors

"Matt" <Matt@community.nospam.com> wrote in message news:uoLB5gdMIHA.4912@TK2MSFTNGP06.phx.gbl...
Here is my issue. I installed SQL 2005 on one of my servers. Up until 10 minutes ago I was able to connect to the server remotely using SQL Server Management Studio but I was unable connect to the SQL server from the actual server that the SQL 05 instance resides on. Now, I restarted the SQL Server, and DB engine service and now I can connect to the SQL database from the actual server but not remotely. I have it configured to allow remote connections and have it setup to use TCP/IP or Named Pipes and still nothing. I've restarted the db engine service and all of the other SQL services and I still can't connect to it remotely.

Any suggestions on what could be causing this? I get this error when I try to connect remotely:

'An error has occurred while establishing a connection to the server. When connecting SQL Server 2005, this failure may be caused by the fact that under the default settign SQL does not allow remote connections....'

Now I also got that same error message when I logged onto the actual server that the SQL 2005 instance resides. I did fix that and now I'm able to log in to SQL SMS from the actual server but not remotely.

Reply to this Message

Ekrem Önsoy - 28 Nov 2007 20:06 GMT

SSIS has its own service and it's an independent service.

If my prior story does not fit you, then follow the path as Andrew suggested. Go to Configuration Manager and check out protocols you use.

Signature

Ekrem Önsoy

OK, now I'm a little confused. I still cannot connect to my SQL 05 instance using a remote connection, however, I am able to connect to the integration service on the SQL server I'm trying to connect to.

Does the SSIS process run under a process outside of SQL Server itself?
"Ekrem Önsoy" <ekrem@btegitim.com> wrote in message news:96F10383-CD75-468C-A808-A47A37EE9E85@microsoft.com...
As far as I understand Matt says that he can not connect to his SQL Server instance from the SQL Server server itself either if I understand him correctly.

If this is the case, I suggest you to forget about the remote connection for this moment and ensure that SQL Server service runs or not. Check out the Event Logs if there is any related error messages. After solving this problem, we can go further.

Let me know if I'm wrong.

--
Ekrem Önsoy

"Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:O9SF2eeMIHA.3940@TK2MSFTNGP05.phx.gbl...
Did you change the tcpip address or the port sql server is using? Is it a default or named instance?

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors

"Matt" <Matt@community.nospam.com> wrote in message news:uoLB5gdMIHA.4912@TK2MSFTNGP06.phx.gbl...
Here is my issue. I installed SQL 2005 on one of my servers. Up until 10 minutes ago I was able to connect to the server remotely using SQL Server Management Studio but I was unable connect to the SQL server from the actual server that the SQL 05 instance resides on. Now, I restarted the SQL Server, and DB engine service and now I can connect to the SQL database from the actual server but not remotely. I have it configured to allow remote connections and have it setup to use TCP/IP or Named Pipes and still nothing. I've restarted the db engine service and all of the other SQL services and I still can't connect to it remotely.

Any suggestions on what could be causing this? I get this error when I try to connect remotely:

'An error has occurred while establishing a connection to the server. When connecting SQL Server 2005, this failure may be caused by the fact that under the default settign SQL does not allow remote connections....'

Now I also got that same error message when I logged onto the actual server that the SQL 2005 instance resides. I did fix that and now I'm able to log in to SQL SMS from the actual server but not remotely.

Reply to this Message

Matt - 28 Nov 2007 18:46 GMT

Its a named instance
Did you change the tcpip address or the port sql server is using? Is it a default or named instance?

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors

"Matt" <Matt@community.nospam.com> wrote in message news:uoLB5gdMIHA.4912@TK2MSFTNGP06.phx.gbl...
Here is my issue. I installed SQL 2005 on one of my servers. Up until 10 minutes ago I was able to connect to the server remotely using SQL Server Management Studio but I was unable connect to the SQL server from the actual server that the SQL 05 instance resides on. Now, I restarted the SQL Server, and DB engine service and now I can connect to the SQL database from the actual server but not remotely. I have it configured to allow remote connections and have it setup to use TCP/IP or Named Pipes and still nothing. I've restarted the db engine service and all of the other SQL services and I still can't connect to it remotely.

Any suggestions on what could be causing this? I get this error when I try to connect remotely:

'An error has occurred while establishing a connection to the server. When connecting SQL Server 2005, this failure may be caused by the fact that under the default settign SQL does not allow remote connections....'

Now I also got that same error message when I logged onto the actual server that the SQL 2005 instance resides. I did fix that and now I'm able to log in to SQL SMS from the actual server but not remotely.

Reply to this Message

Andrew J. Kelly - 28 Nov 2007 19:50 GMT

It is possible the port has changed and the remote connections are either using a fixed value or the value is cached and is now wrong. The local session is most likely using shared memory so it can connect.

Signature

Andrew J. Kelly SQL MVP
Solid Quality Mentors

Its a named instance
"Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message news:O9SF2eeMIHA.3940@TK2MSFTNGP05.phx.gbl...
Did you change the tcpip address or the port sql server is using? Is it a default or named instance?

--
Andrew J. Kelly SQL MVP
Solid Quality Mentors

"Matt" <Matt@community.nospam.com> wrote in message news:uoLB5gdMIHA.4912@TK2MSFTNGP06.phx.gbl...
Here is my issue. I installed SQL 2005 on one of my servers. Up until 10 minutes ago I was able to connect to the server remotely using SQL Server Management Studio but I was unable connect to the SQL server from the actual server that the SQL 05 instance resides on. Now, I restarted the SQL Server, and DB engine service and now I can connect to the SQL database from the actual server but not remotely. I have it configured to allow remote connections and have it setup to use TCP/IP or Named Pipes and still nothing. I've restarted the db engine service and all of the other SQL services and I still can't connect to it remotely.

Any suggestions on what could be causing this? I get this error when I try to connect remotely:

'An error has occurred while establishing a connection to the server. When connecting SQL Server 2005, this failure may be caused by the fact that under the default settign SQL does not allow remote connections....'

Now I also got that same error message when I logged onto the actual server that the SQL 2005 instance resides. I did fix that and now I'm able to log in to SQL SMS from the actual server but not remotely.

Reply to this Message

Matt - 28 Nov 2007 19:39 GMT

I figured it out. Once I started the SQL Browser service, I was able to connect to my SQL05 instance using a remote connection. My question is, what does the SQL Browser service have to do with connecting to the SQL 05 instance remotely?

Here is my issue. I installed SQL 2005 on one of my servers. Up until 10 minutes ago I was able to connect to the server remotely using SQL Server Management Studio but I was unable connect to the SQL server from the actual server that the SQL 05 instance resides on. Now, I restarted the SQL Server, and DB engine service and now I can connect to the SQL database from the actual server but not remotely. I have it configured to allow remote connections and have it setup to use TCP/IP or Named Pipes and still nothing. I've restarted the db engine service and all of the other SQL services and I still can't connect to it remotely.

Any suggestions on what could be causing this? I get this error when I try to connect remotely:

'An error has occurred while establishing a connection to the server. When connecting SQL Server 2005, this failure may be caused by the fact that under the default settign SQL does not allow remote connections....'

Now I also got that same error message when I logged onto the actual server that the SQL 2005 instance resides. I did fix that and now I'm able to log in to SQL SMS from the actual server but not remotely.

Reply to this Message

Andrew J. Kelly - 28 Nov 2007 21:37 GMT

Because that is the only way by default that the clients can know what port to talk to. Since each named instance will get a random port number the browser service returns that to the client when they ask by instance name. To get around that you can fix the port number and hard code that into the connection string.

Signature

Andrew J. Kelly SQL MVP
Solid Quality Mentors

I figured it out. Once I started the SQL Browser service, I was able to connect to my SQL05 instance using a remote connection. My question is, what does the SQL Browser service have to do with connecting to the SQL 05 instance remotely?

"Matt" <Matt@community.nospam.com> wrote in message news:uoLB5gdMIHA.4912@TK2MSFTNGP06.phx.gbl...
Here is my issue. I installed SQL 2005 on one of my servers. Up until 10 minutes ago I was able to connect to the server remotely using SQL Server Management Studio but I was unable connect to the SQL server from the actual server that the SQL 05 instance resides on. Now, I restarted the SQL Server, and DB engine service and now I can connect to the SQL database from the actual server but not remotely. I have it configured to allow remote connections and have it setup to use TCP/IP or Named Pipes and still nothing. I've restarted the db engine service and all of the other SQL services and I still can't connect to it remotely.

Any suggestions on what could be causing this? I get this error when I try to connect remotely:

'An error has occurred while establishing a connection to the server. When connecting SQL Server 2005, this failure may be caused by the fact that under the default settign SQL does not allow remote connections....'

Now I also got that same error message when I logged onto the actual server that the SQL 2005 instance resides. I did fix that and now I'm able to log in to SQL SMS from the actual server but not remotely.

Reply to this Message