Re: Fix of problem connecting VS2005 to remote Sql 2000 server




"Willy Denoyette [MVP]" <willy.denoyette@xxxxxxxxxx> wrote in message
news:eGr6TOWQGHA.3016@xxxxxxxxxxxxxxxxxxxxxxx
|
|
| "RvGrah" <rvgrahamsevatenein@xxxxxxxxxxxxx> wrote in message
| news:1141677747.168923.145430@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
|| After much hair-pulling, I've finally found the answer to a problem
|| that many are fighting with, difficulty connecting from Sql 2005 Server
|| Management or VS2005 to a remote Sql Server running Sql 2000. In my
|| case the server I couldn't reach was across a vpn connection, behind
|| ISA server 2000, (which had port 1433 open).
||
|| The answer was in this post:
||
|
http://groups.google.com/group/microsoft.public.dotnet.framework.adonet/browse_frm/thread/d892fa3f16af2168/c085545c69936dcf?lnk=st&q=dotnet+vs+2005+connect+sql+2000&rnum=8
||
|| (See the 10th post in the thread, by Pablo Castro).
||
|| Adding the simple prefix "np:" in front of the server name fixed the
|| problem immediately. Why didn't Microsoft hire blimps and sky-writers
|| to publicize this hugely frustrating change?
||
|
| Well, they did.... look at:
|
http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring.aspx
|
| or your local VS2005 MSDN docs.
|
| Willy.
|
|

Just forgot to add that when using named pipes as protocol, something you
shouldn't do on a corporate network, you are using port 445 at the server,
so you need to open this port at the firewal or NAT as well. Anyway your
issue is not related to the ISA sever, it's just that you have set-up your
SQL server to use named pipes as protocol, something that you need to
indicate in your ConnectionString, or by specifying the protocol in your
Server variable (data source=np:...) or your Net variable (...;
net=dbnmpntw).

Willy.



Willy.


.



Relevant Pages

  • Re: Database Server based on SQL database
    ... SQL is a language, not a protocol - they are two different things. ... TDS originated with Sybase and is used by SQL Server (earlier versions were ... both the client and the server side. ...
    (microsoft.public.win32.programmer.networks)
  • RE: Fulltext failure on a 2 node cluster
    ... Server full-text search resource online: "SQL Cluster Resource 'Full Text' ...
    (microsoft.public.sqlserver.clustering)
  • Re: DCOM Error - Event 10009
    ... using SQL Server Management Studio 2005. ... Whenever we first launch SQL ... when connecting to a different registered server, it will hang again for 5 - ... I have checked DCOM Config using dcomcnfg, ...
    (microsoft.public.sqlserver.clients)
  • Re: HELP PLEASE ~ ???
    ... You mentioned that it went ahead and added a SQL ... SQL Server 2000 database for all my data. ... find the connectionString in the newly recreated SQLExpress database. ... The connection string specifies a local Sql Server Express instance ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Getting: "The RPC protocol sequence is not supported."
    ... use a tranport protocol that is not enabled by default in W2K3. ... > the moment I'm using a windows app to test the functionality. ... > this app from the windows 2000 server I'm developing on, ... > When connecting to the local DNS server, ...
    (microsoft.public.win32.programmer.wmi)