Post reply

Why remotely connecting to SQL 2005 express failed?

  • February 6, 2012 at 2:01 pm

    #264039

    Hi Folks,

    I have a server installed SQL 2005 Express, I have no problem remote into that machine and start SSMS there, however, when I try to use SSMS to remotely connect to the SQL Express server, it throws the following error:

    Cannot connect to TISMJPVV62\SQLEXPRESS.

    ===================================

    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) (.Net SqlClient Data Provider)

    I already checked SQL browing and TCP/IP connection, both enabled and running.

    What could be wrong?

    I am using VPN to connect to my company's network, TISMJPVV62 is the machine's name. I have no issue when connecting to other SQL server (non-express) same way as I did to express

  • February 7, 2012 at 8:03 am

    #1443801

    Too bad, still no one can give a possible solution.

    Any clue is appreciated. Thanks in advance.

  • February 7, 2012 at 8:18 am

    #1443818

    Look in SQL Server Surface Area Configuration. Connect by Instance and see the property for Remote connections. see if the option is set to Local and remote connections?

    I am not sure if you have already done this..

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • February 7, 2012 at 8:35 am

    #1443841

    it's gotta start with the basics, i think:

    since its an express instance, is the checkbox for allow remote connections checked? maybe via the Configuration?

    next, and probably the most important, did you open the windows firewall on the specific host machine to allow the instance to be accessed remotely?

    I assigned a static port to my instance, then made sure i browsed to the executable in my .MSSQL.1 folder where the instance's sqlsrvr.exe sits.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • February 7, 2012 at 8:41 am

    #1443848

    Bru Medishetty (2/7/2012)

    Look in SQL Server Surface Area Configuration. Connect by Instance and see the property for Remote connections. see if the option is set to Local and remote connections?

    I am not sure if you have already done this..

    I did this check already, thanks anyway

  • February 7, 2012 at 8:43 am

    #1443850

    Lowell (2/7/2012)

    it's gotta start with the basics, i think:

    since its an express instance, is the checkbox for allow remote connections checked? maybe via the Configuration?

    next, and probably the most important, did you open the windows firewall on the specific host machine to allow the instance to be accessed remotely?

    I assigned a static port to my instance, then made sure i browsed to the executable in my .MSSQL.1 folder where the instance's sqlsrvr.exe sits.

    For the first two items, I already enabled them.

    I was also doubting the firewall might prevents the connection request but not sure how to configure it, with your screenshot, I will try again now. Thanks.

  • February 7, 2012 at 8:43 am

    #1443851

    What about named pipes? have you enabled that?

    Alternately have you tried logging to that instance using IPAddress\Instance name..

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • February 7, 2012 at 8:44 am

    #1443853

    Maybe because of windows firewall blocking the application.

    YOu can try to disable windows firewall for the particular application and then check it.

    Regards

    Skybvi

    Regards
    Sushant Kumar
    MCTS,MCP

  • February 7, 2012 at 8:45 am

    #1443855

    SKYBVI (2/7/2012)

    Maybe because of windows firewall blocking the application.

    YOu can try to disable windows firewall for the particular application and then check it.

    Regards

    Skybvi

    I would recommend that idea, just to make sure if Firewall is the culprit..

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • February 7, 2012 at 8:56 am

    #1443868

    I did some configuration on Windows Firewall, not sure if I did it correctly, it is still not working, please see the attachments for the screenshots.

    Thanks.

  • February 7, 2012 at 9:34 am

    #1443913

    halifaxdal (2/7/2012)

    I did some configuration on Windows Firewall, not sure if I did it correctly, it is still not working, please see the attachments for the screenshots.

    Thanks.

    Can you do this from cmd :-

    telnet server name 1433

    Regards,

    Skybvi

    Regards
    Sushant Kumar
    MCTS,MCP

  • February 7, 2012 at 10:21 am

    #1443954

    Might be worth a shot, have you tried square brackets around the server name when you try to connect via SSMS? I am sure I have had something similar in the past.

    Edit: Actually I think that was probably connecting via SqlCmd, so ignore that.

    'Only he who wanders finds new paths'

  • February 7, 2012 at 10:55 am

    #1443984

    As mentioned by previous user, did you disable firewall and test..

    Bru Medishetty

    Blog -- LearnSQLWithBru

    Join on Facebook Page Facebook.comLearnSQLWithBru

    Twitter -- BruMedishetty

  • February 7, 2012 at 11:26 am

    #1444005

    SKYBVI (2/7/2012)

    halifaxdal (2/7/2012)

    I did some configuration on Windows Firewall, not sure if I did it correctly, it is still not working, please see the attachments for the screenshots.

    Thanks.

    Can you do this from cmd :-

    telnet server name 1433

    Regards,

    Skybvi

    I think you got the point: 1433 is blocked.

    To Bru: In my environment, I cannot arbitrarily turn the firewall on or off, I sent the request to our admin and am waiting for further answer. Thanks for your suggest, I believe the firewall is preventing the port being used.

    However, the problem is: I already added 1433 in the exception list in Firewall, why it is still being blocked?

  • February 7, 2012 at 11:51 am

    #1444023

    halifaxdal (2/7/2012)

    SKYBVI (2/7/2012)

    halifaxdal (2/7/2012)

    I did some configuration on Windows Firewall, not sure if I did it correctly, it is still not working, please see the attachments for the screenshots.

    Thanks.

    Can you do this from cmd :-

    telnet server name 1433

    Regards,

    Skybvi

    I think you got the point: 1433 is blocked.

    To Bru: In my environment, I cannot arbitrarily turn the firewall on or off, I sent the request to our admin and am waiting for further answer. Thanks for your suggest, I believe the firewall is preventing the port being used.

    However, the problem is: I already added 1433 in the exception list in Firewall, why it is still being blocked?

    maybe, u r not using 1433 as sql server port, u might be using some other port for sql server.

    Regards,

    Skybvi

    Regards
    Sushant Kumar
    MCTS,MCP

Viewing 15 posts - 1 through 15 (of 35 total)

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