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
  1. Home
  2. General Programming
  3. C#
  4. Remote connection

Remote connection

Scheduled Pinned Locked Moved C#
helpdatabasesql-serversysadmintutorial
5 Posts 3 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.
  • P Offline
    P Offline
    phantanagu
    wrote on last edited by
    #1

    Hi everybody, I have a following problem. My computer uses SQL Server 2000. I write my project on my local machine. I use Dataset to retrieve data from QLNS database. When I set up my project to other machine in LAN. I encounter this error while running exe file. "An error has occured while establishing a connection to the server. When connecting to SQL Server 2000, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections (provider: Name Pipes Provider, error: 40 - Could not open a connection to SQL Server". Please kindly teach me how to solve this. Thank you very much. Hope your help.

    It seem to be a solution or an answer.

    L V 2 Replies Last reply
    0
    • P phantanagu

      Hi everybody, I have a following problem. My computer uses SQL Server 2000. I write my project on my local machine. I use Dataset to retrieve data from QLNS database. When I set up my project to other machine in LAN. I encounter this error while running exe file. "An error has occured while establishing a connection to the server. When connecting to SQL Server 2000, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections (provider: Name Pipes Provider, error: 40 - Could not open a connection to SQL Server". Please kindly teach me how to solve this. Thank you very much. Hope your help.

      It seem to be a solution or an answer.

      L Offline
      L Offline
      Laddie
      wrote on last edited by
      #2

      Is this server accessiable from your system. Try telnetting to port 1433 to confirm the same.

      Thanks Laddie Kindly rate if the answer was helpful

      P 1 Reply Last reply
      0
      • L Laddie

        Is this server accessiable from your system. Try telnetting to port 1433 to confirm the same.

        Thanks Laddie Kindly rate if the answer was helpful

        P Offline
        P Offline
        phantanagu
        wrote on last edited by
        #3

        I have checked port 1433.It is available in Client Network Utility. Maybe some security policies cause the problem. I'm so confused ...

        It seem to be a solution or an answer.

        L 1 Reply Last reply
        0
        • P phantanagu

          Hi everybody, I have a following problem. My computer uses SQL Server 2000. I write my project on my local machine. I use Dataset to retrieve data from QLNS database. When I set up my project to other machine in LAN. I encounter this error while running exe file. "An error has occured while establishing a connection to the server. When connecting to SQL Server 2000, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections (provider: Name Pipes Provider, error: 40 - Could not open a connection to SQL Server". Please kindly teach me how to solve this. Thank you very much. Hope your help.

          It seem to be a solution or an answer.

          V Offline
          V Offline
          Vikram A Punathambekar
          wrote on last edited by
          #4

          1. I don't mean to be condescending, but are you sure you aren't connecting to localhost? 2. Are you able to connect to this database from Query Analyzer on the second machine? 3. Check your SQL Server settings.

          Cheers, Vikram.


          The hands that help are holier than the lips that pray.

          1 Reply Last reply
          0
          • P phantanagu

            I have checked port 1433.It is available in Client Network Utility. Maybe some security policies cause the problem. I'm so confused ...

            It seem to be a solution or an answer.

            L Offline
            L Offline
            Laddie
            wrote on last edited by
            #5

            You may also check if the server has an inernal ip which may allow connections from your cllient network.

            Thanks Laddie Kindly rate if the answer was helpful

            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