Post reply

Can't connect remotely via SSMS but works when I try locally

  • March 28, 2011 at 11:01 am

    #233780

    I have a unique problem when I try to connect via SSMS on my workstation to a SQL Named Instance. However when I log on the server locally and open up SSMS, it works fine.

    Is there anything I should check for? I know the sql server is allowing network connections because our crm reports (rdl/ssrs) are running fine off it.

    The box has a named instance and is running sql service, ssrs, agent.

    sql server 2008 r2

  • March 28, 2011 at 1:12 pm

    #1304537

    Some random thoughts...

    How are you trying to connect from your workstation? TCP/IP?

    - Check the "SQL Server Configuration Manager" to see which protocols are enabled on the DB server.

    Is SSRS running on a remote server too?

    - If yes then how is it connecting? TCP/IP or Named Pipes?

    - If yes then you may be having a firewall issue. If Windows Firewall is enabled on the DB server and it is filtering IPs your workstation may be blocked while the SSRS server may not be.

    - If SSRS is running locally then make sure that remote connections are enabled on the SQL Server instance.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • March 28, 2011 at 1:34 pm

    #1304546

    Both SSRS and SQL Service are on the same remote box

    1 server and instance: HOU-RPT02\NEWREPORTSVRINST

    I notice if I try to connect to the HOU-RPT02\NEWREPORTSVRINSTr's database engine via SSMS on my workstation then it says:

    "A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)"

    But if I change it from database engine to reporting services then it connects fine. Both work when I'm using SSMS on the server locally.

    Here are some configs:

  • March 28, 2011 at 1:39 pm

    #1304549

    Try connecting remotely after starting the SQL Server Browser service.

    edit: I noticed it was not Disabled, just set to a startup type of Manual...so all that is needed it to start the service to test. If remote connections start working then you can set the startup type to automatic.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

  • March 28, 2011 at 1:46 pm

    #1304552

    that fixed it!

    you're awesome

  • March 28, 2011 at 1:49 pm

    #1304555

    master.dbo (3/28/2011)

    that fixed it!

    you're awesome

    Cool, I am happy I could help 😀

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply