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. General Programming
  3. Windows Forms
  4. VB.Net Application not working in LAN, SQL Server does not allow remote connections

VB.Net Application not working in LAN, SQL Server does not allow remote connections

Scheduled Pinned Locked Moved Windows Forms
csharpdatabasesql-serversysadmin
2 Posts 2 Posters 4 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.
  • F Offline
    F Offline
    Francis K Antony
    wrote on last edited by
    #1

    I developed vb.net application it is windows based, my need is in that application worked in LAN, I run the exe file in client desktop computer it is coming error: A connection was successfully established with the server, but then an error occurred during the per-login handshake. When connecting to SQL server 2005, this failure may be caused by the fact that under the default setting SQL Server does not allow remote connections. (Provider: Named Pipes Provider, error: 0 - No process is the other end of the pipe.)

    Franics K Antony

    L 1 Reply Last reply
    0
    • F Francis K Antony

      I developed vb.net application it is windows based, my need is in that application worked in LAN, I run the exe file in client desktop computer it is coming error: A connection was successfully established with the server, but then an error occurred during the per-login handshake. When connecting to SQL server 2005, this failure may be caused by the fact that under the default setting SQL Server does not allow remote connections. (Provider: Named Pipes Provider, error: 0 - No process is the other end of the pipe.)

      Franics K Antony

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      Check your settings[^] :)

      I are Troll :)

      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