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. Database & SysAdmin
  3. Database
  4. SQL Server 2000 connectivity issue [fixed]

SQL Server 2000 connectivity issue [fixed]

Scheduled Pinned Locked Moved Database
helpdatabasesql-serversysadminsecurity
2 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.
  • S Offline
    S Offline
    SarahMcM
    wrote on last edited by
    #1

    I have a SQL Server 2000 server that I have been accessing happily via SQL Server Management Studio (the 2005 version 9.00.3042.00) for ~16 months. Last week I started getting this error message: "Cannot connect to <>. Additional information: A connection was successfully established with the server, but then an error occured during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)" Some important notes: - I'm a SQL Server admin on the box .. and my rights still exist - SSMS = SQL Server Management Studio Here is what I've tried: - accessing from my PC using Windows Authentication = error message thrown - accessing from another box (remote desktop'd onto another server) using SSMS using Windows Authentication = error message thrown - accessing SQL Server 2005 databases (on a different server) from my PC using Windows Authentication = successful connection - accessing from my PC using SQL Server Authentication = successful connection - remote desktop onto the server in question, then open Enterprise Manager and access a database = successful connection - accessing from another PC as someone else via WIndows Authentication = successful connection As far as I know the only thing to change on my PC is that I installed a MS patch (KB972270). This patch is also on the other PC that works for other people so I'm guessing that it isn't the problem ... Any ideas would be gratefully accepted ... Thanks! [edit] Seems some tinkering in the corporate firewall was the culprit - all fixed now.

    C 1 Reply Last reply
    0
    • S SarahMcM

      I have a SQL Server 2000 server that I have been accessing happily via SQL Server Management Studio (the 2005 version 9.00.3042.00) for ~16 months. Last week I started getting this error message: "Cannot connect to <>. Additional information: A connection was successfully established with the server, but then an error occured during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)" Some important notes: - I'm a SQL Server admin on the box .. and my rights still exist - SSMS = SQL Server Management Studio Here is what I've tried: - accessing from my PC using Windows Authentication = error message thrown - accessing from another box (remote desktop'd onto another server) using SSMS using Windows Authentication = error message thrown - accessing SQL Server 2005 databases (on a different server) from my PC using Windows Authentication = successful connection - accessing from my PC using SQL Server Authentication = successful connection - remote desktop onto the server in question, then open Enterprise Manager and access a database = successful connection - accessing from another PC as someone else via WIndows Authentication = successful connection As far as I know the only thing to change on my PC is that I installed a MS patch (KB972270). This patch is also on the other PC that works for other people so I'm guessing that it isn't the problem ... Any ideas would be gratefully accepted ... Thanks! [edit] Seems some tinkering in the corporate firewall was the culprit - all fixed now.

      C Offline
      C Offline
      Corporal Agarn
      wrote on last edited by
      #2

      Thank you for the update.

      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