The Client Network Utility is a configuration tool that tells ADO which network protocols to use when connecting to SQL Server and MSDE. Since Microforge.net Enterprise Server (ENT Server) uses ADO to connect to and work with databases on your MS SQL Server, you may need to make use of the Client Network Utility if you are having difficulty configuring ENT Server to connect to your databases (in the Database Setup Wizard).
As of Windows XP Service Pack 2, Microsoft do not recommend the use of the Named Pipes protocol (which is basically RPC) to connect to MSDE or MS SQL Server, and if you have all the latest service packs installed on the machine where your SQL Server is running then Named Pipes will most likely be disabled.
However, Microsoft Windows operating systems that are running older versions of ADO may be configured to use Named Pipes by default. As such, if you have installed Microforge.net Enterprise Server on an operating system prior to Windows XP Service Pack 2 and your MSSQL/MSDE database server is running on an operating system subsequent to this then you may have problems (the client wants to use Named Pipes and the server doesn’t)
The solution to this is fairly simple. You simply have to
To open the Client Network Utility simply:
Click on Start->Run and type cliconfg.exe then click OK.
You should now see the Client Network Utility which you can use to view/modify the Default network library used by ADO. You should set this to TCP/IP.
You may also want to run the Server Network Utility on the machine where your MSDE or MSSQL Server is installed, to ensure that the default protocol on your server is also set to TCP/IP.
To open the Server Network Utility on the machine where your SQL Server is installed:
Click on Start->Run and type svrnetcn.exe then click OK.
