Article View: bit.databases.mssql-l
Article #2002wfwg and SQL Server
From: Chris Gadsby
Date: Sun, 02 Apr 1995 00:00
Date: Sun, 02 Apr 1995 00:00
21 lines
1248 bytes
1248 bytes
We had the same problem - win 3.1 worked fine but windows for work groups failed. The problem is that wfwg doesn't support dosnp! In order to communicate you will have to run the Network Integration Kit (that comes with SQL Server) on the server and converts named pipes calls to SPX. On the client you need to run the appropriate .dll which is set using the Client Configuration Tool in the client setup disk. I can't remember the exact files names now. For more information you could try the microsoft knowledge base on http://www.microsoft.com or gopher://gopher.microsoft.com. PS - In the end having set this up we never found the Network Integration Kit ot be as robust as Named Pipes (dispite microsofts claims) and went replaces wfwg by win 3.1. Hope this helps Chris Gadsby cjg2@student.open.ac.uk
Technical Details
Message-ID:
<memo.27451@cosy.open.ac.uk>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f6611,98f7f337225effab,start X-Google-Attributes: gidf6611,public From: Chris Gadsby <cjg2@STUDENT.OPEN.AC.UK> Subject: wfwg and SQL Server Date: 1995/04/02 Message-ID: <memo.27451@cosy.open.ac.uk> X-Deja-AN: 100734951 sender: Microsoft SQL Server Discussion List comments: Gated by NETNEWS@AUVM.AMERICAN.EDU newsgroups: bit.databases.mssql-l