Re: unable to connect to sql server remotely

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@xxxxxxxxxxxx> wrote in message news:96F10383-CD75-468C-A808-A47A37EE9E85@xxxxxxxxxxxxxxxx
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@xxxxxxxxxxxx> wrote in message news:O9SF2eeMIHA.3940@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxx> wrote in message news:uoLB5gdMIHA.4912@xxxxxxxxxxxxxxxxxxxxxxx
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.

Relevant Pages

  • Re: provider: Named Pipes Provider, error: 40 - Could not open a c
    ... I have tried connecting to Sql Management Studio and it worked pretty much ... An error has occurred while establishing a connection to the server. ... under the default settings SQL Server does not allow remote connections. ... I have a sql server install / database on the web server. ...
    (microsoft.public.sqlserver.connect)
  • RE: Logging in in background
    ... wold take all kinds of modifictions as I'd need to be checking that each SQL ... my database and all have connection strings associated with them. ... I suspect that there is also an issue on the SQL Server side as I keep ...
    (microsoft.public.access.modulesdaovba)
  • Re: SQL Server uses Windows authentication
    ... > With Windows Authentication you do not put any credentials in the ... The connection uses the credentials of whatever ... >> 1 remote web server to connect to an SQL db on a completely different ...
    (microsoft.public.inetserver.asp.db)
  • Re: Port 1433 access
    ... your next best option is to use a VPN and access the SQL server ... than using RWW. ... You may have a slow workstation that you are using for remote desktop. ...
    (microsoft.public.windows.server.sbs)
  • Re: Connecting to SQL w/ADO
    ... Again, I suggest picking up ... I would not use the ODBC provider to access SQL Server. ... but the SQL connection is new territory for me. ...
    (microsoft.public.vb.database)