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


"RvGrah" <rvgrahamsevatenein@xxxxxxxxxxxxx> wrote in message
news:1141684976.755432.314820@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
| Willy,
|
| I'm not referring to the named pipes vs tcp when I refer to "tools", I
| mean VS2005 and Sql server 2005 tools versus VS2003 and Sql 2000. The
| method that worked in the older version to connect to a server in
| another Lan doesn't work in the 2005 versions without setting the "np:"
| prefix to force named pipes, as Pablo on the Ado.Net team recommended.
|
| I'm also a little confused, because the ISA server at the remote server
| has port 1433 open, and always allowed Vs2003 and Sql 2000 Enterprise
| Manager to funtion fine. I don't see port 445 open anywhere, either in
| IP Packet Filters or in Protocol Definitions, so I'm a little mystified
| as to why adding the np: prefix worked for me instantly both in VS and
| Sql Management Studio, where all attempts to go by just the server name
| (I assumed using tcp) failed.
|
| This is all so deep, and quite hard to master for somone who's handling
| everything from hardware issues to Sql admin and database front-end
| development in addition to many other things... I know the number of
| hats I'm wearing does not constitute emergency on your part, I'm just
| trying to get up to speed with the 2005 tools at least to the extent
| that I was functioning well in 2000/2003 tools.
|
| Regards, Bob
|

"np:servername" is a shortcut for "Net=dbnmpntw", herewith you 'force' the
client to use the named pipe protocol to connect to the SQL server. If you
don't specify np or dbnmpntw, the client will use what is configured as
default client protocol(s) (see SQL2005 - SQL Server Configuration Manager)
to connect with SQL server, I assume the default enabled protocol is shared
memory, the other possible protocols are TCP/IP, Named pipes and VIA.
Now, suppose you have shared mem. and TCP enabled in that order. When a
client tries to connect it will use shared memory is the server name is
local, but it will use TCP/IP when the server is remote (using port 1433),
but this isn't working in your case so my guess is that, or, TCP/IP is not
enabled at the SQL server side, or, that you don't have the TCP/IP enabled
at the client, so what you have done is forced the client to use named pipes
network library, but you could also have enabled TCP/IP or Named pipes at
the client using the "SQL Native client configuration" in SQL Server Config.
manager.
For you port 445 issue, rest assured that named pipes use port 445, you can
check this by issuing a netstat -a command at the server, when a client is
connected you will see that the connection is established. Note that this
same port is used by the File server as well, so make sure no clients are
connected to a share on the server.

Willy.


.

Relevant Pages

  • Re: what type of socket should I use?
    ... Essentially the server just waits till it gets a message ... | from the client and on reciept of a message it send ... sockets, Named Pipes, or Shared Memory ... Unix Domain Sockets is similar to Named Pipes. ...
    (comp.os.linux.networking)
  • Re: what type of socket should I use?
    ... Essentially the server just waits till it gets a message ... | from the client and on reciept of a message it send ... sockets, Named Pipes, or Shared Memory ... Unix Domain Sockets is similar to Named Pipes. ...
    (comp.os.linux.development.apps)
  • Re: Delegation???
    ... EFS in Win2k relies on delegation working over named pipes, ... client and server, where the server can connect to another server as well. ...
    (microsoft.public.platformsdk.security)
  • Re: netbios and named pipes sql replication.
    ... Once the client switched to named pipes, ... > connection with. ... > When we took named pipes support off the SQL server with the MS patch, ... > We had to manually walk thru the ODBC setup and configure the CLIENT ...
    (microsoft.public.sqlserver.replication)
  • Security strategy: Access client/SQL Server
    ... I will be creating an application using MS Access as a client to SQL ... SQL Server resides. ... permissions for group X to open form A, users would need to get a new ...
    (comp.databases.ms-access)