Re: unable to connect to sql server remotely

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.


"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: Failed to get a SQL Server connection
    ... remote SQL Server device. ... check that you have installed the SMS SQL database on the default ... Use the output to verify that the account is enabled, ... SMS Site Component Manager failed to reinstall this component on this site ...
    (microsoft.public.sms.setup)
  • Http verification .sms_aut (port 80) failed
    ... I noticed I couldn't get SMS reports to work.... ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ...
    (microsoft.public.sms.admin)
  • Re: Http verification .sms_aut (port 80) failed
    ... I noticed I couldn't get SMS reports to work.... ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ... SMS_SITE_COMPONENT_MANAGER service to immediately apply the new configuration. ...
    (microsoft.public.sms.admin)
  • Re: SMS Component errors after installing SP2
    ... MVP Windows Server System - SMS ... MP encountered an error when connecting to SQL Server. ... If using a standard SQL security account, ... is used to publish fully qualified host names in Active Directory. ...
    (microsoft.public.sms.setup)
  • Re: Does anyone know how to fix this??
    ... > Inside the Active Directory Users and Computers in the folder of SYSTEM I ... Give the site's SMS Service account full control rights to the ... MP encountered an error when connecting to SQL Server. ...
    (microsoft.public.sms.setup)