Post reply

MSSQL Server 2008 R2 not being connected via ip address.

  • December 30, 2011 at 4:57 am

    #248915

    I am using MSSQL 2008 R2

    Operation System :- Windows server 2008

    When i write B0-C2\SQLEXPRESS in servername the SQL connected

    but if i try to connect SQL with ip address.. it shows following error:

    named pipe provider error 40 could not open connection to sql server

    i enabled all services of MSSQL 2008

    one service is not started :- SQL server agent(Getting automatically stopped)

    even in Services list of windows server 2008 i tried to start ICS service but same

    it's not started

    Error :- ICS Service on local computer started and stopped. some services stop automatically if they are not in use by other services or program.

    ICS translate the name of computer into ip-address.

    Thanks & Regards,
    Pallavi

  • December 30, 2011 at 4:59 am

    #1426883

    Do you have two or more instances installed on that server? Are you connecting to right IP address?

  • December 30, 2011 at 5:12 am

    #1426892

    Yes i am connecting to right ip address......

    actually when i was working on MSSQL2005 ..

    ICS started after setting.

    don't know why 2008R2 giving a problem...!!!!!!!!!!!

    Thanks & Regards,
    Pallavi

  • December 30, 2011 at 5:21 am

    #1426896

    pallavi.unde (12/30/2011)

    Yes i am connecting to right ip address......

    actually when i was working on MSSQL2005 ..

    ICS started after setting.

    don't know why 2008R2 giving a problem...!!!!!!!!!!!

    In the article below Pinal has given steps to troubleshoot & fix the issue. Please follow him.http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipes-provider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/

  • December 30, 2011 at 5:22 am

    #1426897

    its not R2 that is the problem, its connecting to the instance.

    since you can connect via name, we know you already allowed remote connections.

    to get to an instance, instead of the default, you need to either specify the instance or the port to get to it:

    192.168.1.55\SQLEXPRESS

    or change your instance to listen to a specific port, and connect like this this 127.0.0.1[comma][port]:

    192.168.1.55,1711

    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!

  • December 30, 2011 at 5:24 am

    #1426898

    When you use an IP address instead of the server name, SQLNCLI assumes TCP/IP is enabled.

    Is there any particular reason why you're using Named Pipes and not TCP/IP?

    -- Gianluca Sartori

  • December 30, 2011 at 6:02 am

    #1426912

    Yes .... Problem get solved by adding port ...:)

    Thank u very much

    Thanks & Regards,
    Pallavi

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

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