Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Database & SysAdmin
  3. Database
  4. Connect to Remote Server [modified]

Connect to Remote Server [modified]

Scheduled Pinned Locked Moved Database
sysadmindatabasesql-serverhelp
7 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • realJSOPR Offline
    realJSOPR Offline
    realJSOP
    wrote on last edited by
    #1

    I'm on a WORKGROUP LAN at home, and I want to connect to an instance of SQL Server 2005 Express on one of the other boxes on the network. I have already enabled remote connections on that instance of SQL Server and restarted the service. When I try to connect, it tells me this: TITLE: Connect to Server ------------------------------ Cannot connect to HTPC. ------------------------------ ADDITIONAL INFORMATION: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

    .45 ACP - because shooting twice is just silly
    -----
    "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
    -----
    "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

    modified on Saturday, March 27, 2010 11:52 AM

    I 1 Reply Last reply
    0
    • realJSOPR realJSOP

      I'm on a WORKGROUP LAN at home, and I want to connect to an instance of SQL Server 2005 Express on one of the other boxes on the network. I have already enabled remote connections on that instance of SQL Server and restarted the service. When I try to connect, it tells me this: TITLE: Connect to Server ------------------------------ Cannot connect to HTPC. ------------------------------ ADDITIONAL INFORMATION: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) (Microsoft SQL Server, Error: 2)

      .45 ACP - because shooting twice is just silly
      -----
      "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
      -----
      "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

      modified on Saturday, March 27, 2010 11:52 AM

      I Offline
      I Offline
      i j russell
      wrote on last edited by
      #2

      Have you also enabled Named Pipes through the Configuration Manager?

      realJSOPR 1 Reply Last reply
      0
      • I i j russell

        Have you also enabled Named Pipes through the Configuration Manager?

        realJSOPR Offline
        realJSOPR Offline
        realJSOP
        wrote on last edited by
        #3

        Yeah. Could it be a user account problem? When I try to connect (using Windows Auth), it uses my local box's user account.

        .45 ACP - because shooting twice is just silly
        -----
        "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
        -----
        "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

        I 1 Reply Last reply
        0
        • realJSOPR realJSOP

          Yeah. Could it be a user account problem? When I try to connect (using Windows Auth), it uses my local box's user account.

          .45 ACP - because shooting twice is just silly
          -----
          "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
          -----
          "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

          I Offline
          I Offline
          i j russell
          wrote on last edited by
          #4

          Have you got Mixed Authentication set in the Sql Server Express instance? If so, can you connect using non-windows authentication? I noticed that the message said that it can't find instance HTPC; Is that the name of the instance or is it HTPC\SQLEXPRESS?

          realJSOPR 1 Reply Last reply
          0
          • I i j russell

            Have you got Mixed Authentication set in the Sql Server Express instance? If so, can you connect using non-windows authentication? I noticed that the message said that it can't find instance HTPC; Is that the name of the instance or is it HTPC\SQLEXPRESS?

            realJSOPR Offline
            realJSOPR Offline
            realJSOP
            wrote on last edited by
            #5

            i.j.russell wrote:

            Have you got Mixed Authentication set in the Sql Server Express instance? If so, can you connect using non-windows authentication?

            No, but do I want to use non-windows authentication?

            i.j.russell wrote:

            I noticed that the message said that it can't find instance HTPC; Is that the name of the instance or is it HTPC\SQLEXPRESS?

            HTPC is the machine name. The server is HTPC\SQLEXPRESS.

            .45 ACP - because shooting twice is just silly
            -----
            "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
            -----
            "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

            I 1 Reply Last reply
            0
            • realJSOPR realJSOP

              i.j.russell wrote:

              Have you got Mixed Authentication set in the Sql Server Express instance? If so, can you connect using non-windows authentication?

              No, but do I want to use non-windows authentication?

              i.j.russell wrote:

              I noticed that the message said that it can't find instance HTPC; Is that the name of the instance or is it HTPC\SQLEXPRESS?

              HTPC is the machine name. The server is HTPC\SQLEXPRESS.

              .45 ACP - because shooting twice is just silly
              -----
              "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
              -----
              "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

              I Offline
              I Offline
              i j russell
              wrote on last edited by
              #6

              The reason for asking about mixed mode authentication is that if you can connect using a connectionstring like this; Server=myServerAddress;Database=myDataBase;User ID=myUsername;Password=myPassword; but not like this; Server=myServerAddress;Database=myDataBase;Trusted_Connection=True; then you do have a permissions issue. However, most connection problems are due to incorrectly naming the server or database. The more things we can discount, the easier it will be to fix.

              realJSOPR 1 Reply Last reply
              0
              • I i j russell

                The reason for asking about mixed mode authentication is that if you can connect using a connectionstring like this; Server=myServerAddress;Database=myDataBase;User ID=myUsername;Password=myPassword; but not like this; Server=myServerAddress;Database=myDataBase;Trusted_Connection=True; then you do have a permissions issue. However, most connection problems are due to incorrectly naming the server or database. The more things we can discount, the easier it will be to fix.

                realJSOPR Offline
                realJSOPR Offline
                realJSOP
                wrote on last edited by
                #7

                This is almost a non-issue, as I have halfway decided to use SqlLite instead. Thanks anyway. :)

                .45 ACP - because shooting twice is just silly
                -----
                "Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
                -----
                "The staggering layers of obscenity in your statement make it a work of art on so many levels." - J. Jystad, 2001

                1 Reply Last reply
                0
                Reply
                • Reply as topic
                Log in to reply
                • Oldest to Newest
                • Newest to Oldest
                • Most Votes


                • Login

                • Don't have an account? Register

                • Login or register to search.
                • First post
                  Last post
                0
                • Categories
                • Recent
                • Tags
                • Popular
                • World
                • Users
                • Groups