Re: Windows 2000 - MS Access XP and Sql Server 2005.

The [DBNMPNTW] library is the library for the named pipes protocol; so the
first thing to do would be to try with the TCP/IP protocol instead: try
adding tcp: before the name of the server. If necessary, add the port
number «,1433 » (with the comma, without the «», change 1433 if this is not
the right port to use) at the end. Installing the latest MDAC could also
help in your case:

http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=en

In your case, if changing for the tcp/ip doesn't work, we must look into a
variety of possibilities. First, what kind of stuff are you using: are you
using an Alias for the server; which protocol (tcp or np); if tcp or np, if
there is a blocking firewall for the relevant port(s) (the ports used by tcp
or np are not the same); static or dynamic ports; is tcp and/or np
configured for reception on the SQL-Server; are you trying to access the
default instance or a named instance; is the browser service or the
discovery service activated, what kind of authentification (Windows or
sql-server) are you using; etc, etc., etc.

Here a some more info to help you with your problem:

http://blogs.msdn.com/sql_protocols/archive/2007/07/19/tcp-provider-no-connection-could-be-made-because-the-target-machine-actively-refused-it.aspx

http://blogs.msdn.com/sqlexpress/archive/2005/05/05/415084.aspx

http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx

http://msdn2.microsoft.com/en-us/library/ms345318.aspx

http://www.datamasker.com/SSE2005_NetworkCfg.htm

--
Sylvain Lafontaine, ing.
MVP - Technologies Virtual-PC
E-mail: sylvain aei ca (fill the blanks, no spam please)


"tf85" <tf850@xxxxxxxxxxx> wrote in message
news:4794a421$0$24701$426a34cc@xxxxxxxxxxxxxxx
Hi

I can't connect a client computer with windows 2000 to sql server 2005 :
I have 2 kinds of PC clients : with Widows XP Pro (every thing is OK), and
Windows 2000 Pro (no connection to Sql Server)
My problem is only with 2 computers turn with Windows 2000 :
The client turns with Windows 2000, MS Access XP-SP3 (with ADP project)
The Server : Windows 2003 server + Sql Server 2005.
I have this message :
"Test connection failed because of an error in initializing provider.
[DBNMPNTW]connection broken."

Can I do some thing to resolve this problem ?
Thanks for help





.

Relevant Pages

  • Re: VPN Error 720
    ... The Zywall is configured for passthrough of port 1723 and GRE ... I got other error messages before that was done. ... avoidance of client/server terminology) makes a TCP (IP protocol 6) call to ... TCP Port 1723 on the other endpoint. ...
    (microsoft.public.windows.server.sbs)
  • Re: RMI binding to SAME port but DIFFERENT IP address on SAME host
    ... >> The host computer simply knows which protocol it is hosting on each ... >> You can't have two different protocols hosted on the same port, ... At the TCP level the host neither knows nor cares about ...
    (comp.lang.java)
  • Re: RMI binding to SAME port but DIFFERENT IP address on SAME host
    ... >> The host computer simply knows which protocol it is hosting on each ... >> You can't have two different protocols hosted on the same port, ... At the TCP level the host neither knows nor cares about ...
    (comp.lang.java.programmer)
  • Re: Ports other than 53 required for proper DNS operation????
    ... DNS should be straight TCP/IP on port 53, ... UDP first, then TCP. ... With Windows communication within a network, or even on the local server, ...
    (microsoft.public.windows.server.dns)
  • Re: W2K VPN Setup
    ... GRE is as IP protocol, just like TCP or UDP. ... because it is not a port. ...
    (microsoft.public.win2000.ras_routing)