Copyright: Copyright © 1997 Pervasive Software


Add Components Dialog Box

In this dialog, you can add DLLs that you want SmartScout to look for every time a component check is done.

To add a component, type the name of the component in the text box at the top of the dialog and click Add. The component should then appear in the list as shown in the following screen.:

Your component will then be displayed in the Components grid.

You can remove components from the list one at a time by selecting the item and clicking Remove. If you want to remove all the entries, click Clear List.

If you make an error, click Restore and the previous entries will be displayed.

To save this list of components between sessions, click Save.


Add Directories Dialog Box

In this dialog, you can add directories that are searched for Pervasive components before others. Click Add to display a file dialog, with which you can specify an application directory. The directory should then appear in the list as shown in the figure that follows.

You can remove directories from the list one at a time by selecting the item and clicking Remove. If you want to remove all the entries, click Clear List.

If you make an error, click Restore and the previous entries will be displayed.

To save this list of directories between sessions, click Save.


Applies To NT & NetWare
Windows NT

Novell NetWare


Applies To NT Only
Windows NT Server

Windows NT Workstation acting as a server


Applies to NetWare
Novell NetWare


BTI Registry Entries
This button displays registry entries that pertain to Btrieve Technologies.


BTI.INI Button
BTI.INI is the configuration file for 16-bit Pervasive software. You do not have to edit this file directly - you can use the Win16 Setup utility to do this for you.

1.	Click Start, point to Programs, then to the Pervasive folder

2.	Select Setup (Win16).


Btrieve
Pervasive Software's navigational database engine.


Btrieve Requester DLLs
Required DLLs for Btrieve Client-Server Access	See Also

These DLLs are typically found in the Windows\System or WinNT\System32 subdirectory.  You should have one and only one copy of the DLLs installed on your workstation.

Note that the DLLs below are list with a "100" or a "101" in the filename.  This is the Version of the DLL.  The 100 and 101 version is the initial release of this DLL.  Future updated versions will have names like 102, 103, or 200 etc. etc.  Only the latest version of the DLL should be needed.

Btrieve version 7.00

16-bit application on Windows 3.1 or Windows for Workgroups

WBTRCALL.DLL	(used only by 6.x applications)

W1AIF101.DLL

W1BTRV7.DLL

W1BIF101.DLL

W1MIF101.DLL

W1CRS100.DLL

W1NSL101.DLL

16-bit application on Windows 95 or Windows NT workstation

WBTRCALL.DLL	(used only by 6.x applications)

W1AIF101.DLL

W1BTRV7.DLL

W1BIF101.DLL

W1MIF101.DLL	(thunking done here)

W3AIF101.DLL

W3BIF101.DLL

W3MIF101.DLL

W3CRS100.DLL

W3NSL101.DLL

W16NR.DLL

W32NR.DLL

32-bit application on Windows 95 or Windows NT workstation

WBTRV32.DLL	(used only by 6.x applications)

W3AIF101.DLL

W3BTRV7.DLL

W3BIF101.DLL

W3MIF101.DLL

W3CRS100.DLL

W3NSL101.DLL

Btrieve version 6.15

16-bit application on Windows 3.1 or Windows for Workgroups

WBTRCALL.DLL

WBTRVRES.DLL

WBTICOMM.DLL

NWLOCALE.DLL

NWIPXSPX.DLL	(for NetWare server)

NWCALLS.DLL	(for NetWare server)

16 bit application on Windows 95 or Windows NT workstation

WBTRCALL.DLL

WBTRVRES.DLL

WBTRTHNK.DLL

WBTRV32.DLL

W32BTICM.DLL

W32NR.DLL

W16NR.DLL

NWLOCALE.DLL

32-bit application on Windows 95 or Windows NT workstation

WBTRV32.DLL

W32BTICM.DLL


CLIB
CLIB is a set of libraries for NetWare.  The latest package can be downloaded from http://www.novell.com and has a filename of LIBUPx.ZIP where "x" is the latest revision letter.

Note that CLIB contains several NLMs to be installed - these all need to be installed together.  That is, you cannot install portions of the LibUp package.


Communications Problems

Communications problems are operating system and network dependent.  These are not errors caused by your Pervasive Software product, but rather from your operating system or network.  However, since your product is dependent on communications and your network to function, the following basic information is provided to assist you in correcting problems in these areas.  Further information can be found in your operating system and network help files and documentation.

Common Causes of Communication Problems

Old workstation drivers for the network

Old LAN card drivers at the workstation or server

Bad hardware (usually the LAN cards at the workstations or server)

Configuration problems in the routers and/or bridges between the workstation and the server.

An incorrect configuration in a server with more than one network card (multi-homed server). See Getting Started for information on how to correct this.

Always make sure your system is using the latest workstation drivers (such as Novell Client 32 for Windows 95 or Windows for Workgroups NDIS drivers from Microsoft), as well as the latest LAN card drivers from the LAN card manufacturer. If possible, check with the OS vendor to see if they have any known reported conflicts with the cards and drivers you are using; you can typically check Novell’s or Microsoft’s web site for this type of information.

Related Topics

Required Networking DLLs


Component Display Options

This dialog controls the display of components on the Components Page.

Select or clear the options you want and click OK. The grid will be updated to include your revised information.

If you want to return to the original configuration, click Defaults.

Click Save to retain your selections on this dialog between sessions.


Components Page Components
The Components button displays the Add Components dialog, which allows you to add a component that does not appear in the grid to the list of components normally searched for by SmartScout.


Components Page Configure
The Configure button invokes the Component Display option dialog box, which allows you to choose which components are displayed in the Components page grid.


Components Page Directories
This button displays the Add Directories dialog, which allows you to add directories where Btrieve or Scalable SQL applications reside so that the components located in these directories appear in the list of components. In a typical Pervasive installation, you do not need to add directories using this method.


Components Page Grid

The grid on this panel shows the network and Pervasive modules that are used by your engine and requesters. You can view information about the components such as the location, date, size, and usage.

You can rearrange the order of the grid by clicking on a column heading, dragging the column to its new location, and then releasing the mouse button. You can resize the columns by clicking on the divider and dragging the column to its new width.

See the overview of the Components Page for more information.


Components Page Overview

This page shows the program and networking components used by your Pervasive software.

You can use the information shown on this page to determine which components Pervasive is using when operating.

For more information about the elements on this dialog, see the following topics:

Refresh button

Directories button

Components button

Configure button


Components Page Refresh
The Refresh button rescans the directories for updated information on the components. Use this button if you added or replaced a component while SmartScout was loaded.


Customer Support

1-800-287-4383 (USA and Canada)

 011-353-1-612-7440 (European support center - Dublin)


Getting Started
SmartScout Overview


How to Get Additional Help
Status Codes Help File

How to Reach Customer Support


IPX/SPX
IPX/SPX	See Also	Applies To

IPX/SPX is a protocol that allows network access to NetWare or Windows NT servers (more commonly used on NetWare).  In order to use this protocol to run your Pervasive Software product, it must be installed and configured correctly on both the workstation and server.  For further information on installing and configuring the IPX/SPX protocol, consult your operating system documentation and help.

IPX and SPX are actually two different layers of protocols.  IPX is the more typical implementation because of its speed and routability.  It is capable of functioning on its own.  However, it has no guarantees that the information from one computer will reach another computer.

SPX sits on top of IPX and sacrifices a small amount of speed for the ability to verify that the server receives information sent from a workstation.  Because of the important nature of your data, Btrieve  and Scalable SQL both use SPX.

Since most applications rely solely on IPX, your network may appear to be working.  However, this does not mean that SPX is functioning.


InstallScout Help File


Network Clients Defined

Network clients are the workstation API's (application programming interfaces) that 'talk' to protocols and allow access from the workstation to your network.  The Microsoft network client or the NetWare network client can be used with your software product.  For information on installing and configuring network clients, consult your operating system help and documentation.  The following is list of network clients supported by Btrieve.

Microsoft Client for Microsoft Networks

Microsoft Client for NetWare Networks

Novell Client for NetWare Networks

Novell Client32 for NetWare Networks


Network Number Incorrectly Set

The Network Number for each frame type must be the same on network devices connected to the same network segment.

To Check Your Network Number

1.	Run "ipxroute config" from a DOS box on the workstation.  Note the network number (NOT internal network number).

2.	Run "ipxroute config" from a DOS box on the server.  Note the network number (NOT internal network number).

To Change Your Network Number:

Change the network number in the registry to zero on the workstation.  This allows the workstation to pick the network number up from the wire, ensuring it will always be right.


Networking Topics
TCP/IP

IPX/SPX

Communications Problems

Required Files for Network Communication


Packet Size
Determines the size of IPX/SPX packets sent across the network.

For information on packets and setting the size for your operating system, you should consult your operating system help, documentation or vendor.

Btrieve also has an internal Receive Packet Size that can be set (see the User's Guide).


Pervasive Software Registry Entries
This button displays the registry entries that pertain to Pervasive Software.


Ping
Ping	See Also

Overview

Ping is a command line utility that comes with TCP/IP based server operating systems to allow connectivity testing between machines running the TCP/IP protocol and connected via the network. In simple terms, Ping verifies that you can communicate with the server by using the protocol (language) that your client normally uses to communicate with the server. Instead of performing a database operation, however, Ping answers the simple question of whether you can connect to the server at all using TCP/IP.

To understand the concept of ping, you can think of it as being similar to RADAR. You initiate a ping signal and wait to see if any signal bounces back and shows on your screen, indicating that your target is out there.

In a TCP/IP ping, you send a signal to a specific server (either by name or by Internet IP address). If the ping is successful, you receive a series of replies from the remote server with some additional information such as the time it took for the reply. If you receive the reply, you can be assured that the two-way TCP/IP communication between your client and the server is functioning, and you can eliminate that as a cause for any software functionality problems you are having.

How to Use Ping in Windows 95/NT:

1.	Click Start and select Run.

2.	Type Ping MachineName at the prompt and press Enter.

What You Should See if the Ping is Successful

If successful, you should see a return message such as:

Pinging YourServerName [192.168.1.207] with 32 bytes of data:

Reply from 192.168.1.207: bytes=32 time=1ms TTL=128

Reply from 192.168.1.207: bytes=32 time=1ms TTL=128

Reply from 192.168.1.207: bytes=32 time=1ms TTL=128

Reply from 192.168.1.207: bytes=32 time=1ms TTL=128

If you do not get a reply, you probably have a network communication problem.

For Pervasive software to function, you must be able to use Ping using the name of the machine.


Protocols
Your software product can use one of 2 protocols -- IPX/SPX  or  TCP/IP.

These protocols allow your workstation to communicate with your server.

One or both of these protocols is required to be installed and functioning correctly before your client-server product will function.

Also note that the Btrieve and Scalable SQL Engines must be started on the targeted server.


Protocols Defined
Protocols are the transport that transfer packets (data) to and from systems on a network.  Your Pervasive Software product can use the TCP/IP protocol or the IPX/SPX protocol.


RCONSOLE
A NetWare utility that allows a user to control the NetWare console from a remote workstation.

For RCONSOLE to work, the server must have RSPX.NLM and REMOTE.NLM loaded.


Report Generation Dialog Box

This dialog allows you to generate a report that can be used by Customer Support to diagnose the cause of a problem with your communication or software.

If you click Report from the Workstation tab, you generate a report which contains the following items:

Contents of BTI.INI (if checked)

Contents of Windows Registry pertaining to Pervasive (if checked and running 32-bit version of SmartScout)

If you click Report from the System Tests tab after you have run a test, the output of the test as shown in the testing window is also contained in the report.

How to Generate a Report

You can either send the report to your default printer or save the report as a text file. If you choose to save as a text file, enter a fully-qualifed name for the file in the Filename field. Click OK to save or print the report.


Required Files for Network Communications

Start by choosing which Operating system your Workstation is running.

Win16  (Windows 3.x and Windows for Workgroups)

Win32  (Windows 95 and Windows NT)


Scalable SQL
Pervasive Software's relational database engine.


Scalable SQL Requested DLLs
Required DLLs for Scalable SQL Client-Server Access	See Also

These DLLs are typically found in the Windows\System or WinNT\System32 subdirectory.  You should have one and only one copy of the DLLs installed on your workstation.

Scalable SQL version 7.00

16-bit application on Windows 3.1 or Windows for Workgroups

16-bit application on Windows 95 or Windows NT workstation

32-bit application on Windows 95 or Windows NT workstation

Btrieve version 6.15

16-bit application on Windows 3.1 or Windows for Workgroups

16 bit application on Windows 95 or Windows NT workstation

32-bit application on Windows 95 or Windows NT workstation


See Also Required DLLs
Recommended Winsock DLLs

Required Files for Network Communications


See Also SPX
IPX/SPX

Protocols


See Also TCPIP
TCP/IP

Protocols

Packet Size


SmartScout Contents

Getting Started

Using SmartScout

Networking Topics

How to Get Additional Help


SmartScout Overview
SmartScout Overview	Status Code List

SmartScout is a utility that you run in order to diagnose component or networking problems that occur after the initial installation.

When To Use SmartScout

SmartScout is a utility that is similar to the InstallScout application that tested your network and software during the installation of your Pervasive software components.

SmartScout Prerequisites

To run SmartScout, the following must be true:

Both the Btrieve and Scalable SQL server engines must be running (they are started automatically if you chose the Typical install).

Network client software and protocol must be installed on your workstation (either SPX or TCP/IP)

The machine on which you installed your Pervasive server must be accessible from your workstation. To do this, you must map a drive to the remote server as discussed in the installation chapters of Getting Started.

Using SmartScout

SmartScout's user interface contains three tabs that control its operation. Click the right arrow button at the top of the screen or follow these links for more information about each page.

Workstation Tab

Components Tab

System Tests Tab

Types of Errors That Can Be Received During SmartScout

SmartScout can detect two types of errors - those that arise from a problem with your network or communication setup, and those that indicate a problem with your Pervasive software setup, which usually manifest themselves as a status code.

Communications/Network Problems

Pervasive Software Status Codes

How to Get Additional Help

Additional information on these topics is available on the Pervasive Web site: http://www.pervasive.com

Consult your operating system and network help files and documentation.

How to Contact Customer Support


System Tests - Browse button
Browse Button

This button displays a dialog that allows you to choose a location for the target database. Enter the path to the Pervasive server engine and click OK.


System Tests - Clear List button
Clear List Button

This button clears the display of the Test output window.


System Tests - Enabling Named Databases
Named Database Check box

This check box is only available when Scalable SQL is selected as the engine to test.

Scalable SQL supports the use of logical named databases instead of paths to find a database.

When you select the Named Database check box, the System Tests dialog changes the Target Name area to display a drop down list from which you can select the database you want.

When you clear the Named Database check box, the System Tests dialog changes the Target Name area to accept a path where a Btrieve or Scalable SQL database resides.

For more information on Named Database support, see Getting Started.

If you have a 32-bit client using Microsoft Client Service for NetWare, see the troubleshooting note in the Named Database selection topic.


System Tests - Engine Choices
Engine Choices for Testing

The Pervasive 7.0 package contains two engines - the Btrieve transactional engine and the Scalable SQL relational engine. You can test one engine at a time during a SmartScout test.

If you select Scalable SQL, the Named Database check box under Target Name becomes available.

The engine you want to test must be running on the machine on which your Pervasive server is installed.


System Tests - Entering a Named Database
Named Database Selection

This selection box is only available when Scalable SQL is selected as the engine to test.

Scalable SQL supports the use of logical named databases instead of paths to find a database.

When you select the Named Database check box, the System Tests dialog changes the Target Name area to display a list from which you can select the database you want. After you select the correct database, click Run Tests to begin.

Named Databases Troubleshooting

If you have a 32-bit client using the Microsoft Client Service for NetWare (instead of the Novell IntranetWare client) to connect to NetWare servers, you must add the servers on which your databases reside to the Scalable SQL servers setting in the Setup utility. If you do not, you may receive the message "No Named Databases Found" on your client machine. This is caused by a limitation of the NetWare support of the Microsoft client.

If you receive a "No Named Databases Found" message, perform the following steps at your 32-bit Pervasive client machine:

1.	Click Start, point to Programs, then to the Pervasive folder.

2.	Select Setup (Win32).

3.	Select the DBNames Interface component.

4.	Select the Scalable SQL Servers setting.

5.	In the Add Server Name field, enter the name of a server on which your databases reside and click Add.

6.	Repeat the previous step as necessary so that all the servers containing SQL databases are listed.

For more information about the Setup utility, see the User's Guide.


System Tests - Protocol Choices
Protocol Choices

This area of the System Tests dialog allows you to choose the protocols that you have on your system.

All available

Tests TCP/IP and SPX if both protocols are available.

First available

Tests the default protocol on the system. For Windows NT and NetWare, the default protocol is TCP/IP.

TCP/IP

Tests only TCP/IP.

SPX

Tests only SPX.


System Tests - Target Name
Target Name

The target name is one of the logical database names that you can use to access Btrieve or Scalable SQL data.

Enter either a path to a Btrieve or Scalable SQL database in this field.

To select a named database instead, select the Named database check box, click the arrow of the drop down list and select the database you want from the list. For a detailed explanation of named databases, see Getting Started.


System Tests Page Overview

This dialog can assist you in diagnosing communication and software problems that can arise after installation of your Pervasive software.

For more information about the elements of this dialog, see the following topics:

Engine to Test

Protocol Choices

Testing Levels

Target directory

Enabling Named Databases

Choosing a Named Database

When you are ready to begin the tests, click Run Tests.

To save the output from the tests, click Report.


System Tests Run Test
Run Tests Button

This button begins a test using the parameters you selected in the System Tests window.


System Tests Testing Level
Testing Level

There are two levels of testing for SmartScout

Basic Communication Tests

The Basic tests perform tests of the network connectivity and also of the software functionality. The results of the tests displays in the window at the bottom of the System Tests dialog. You can save the results of this report by clicking Report.

Communication Stress Tests

The Communication Stress Tests are a superset of the Basic Communications Tests. If you select this level of testing, the Basic Communications Tests run first. Then, the communications stress tests begin, which send multiple data packets through the network to ensure that the server can handle multiple data packet sizes. These tests run continually until you click Cancel. You can save the results of this report by clicking Report.


TCP/IP
TCP/IP	See Also

TCP/IP is a protocol that allows network access to Windows NT and NetWare servers (more often Windows NT).  In order to use this protocol to run your Pervasive Software product, it must be installed and configured correctly on both the workstation and server.

Under Windows NT (workstation or server edition) the NetBIOS protocol must also be installed.  Windows 95 does this automatically (even though you do not see it).

For further information on installing and configuring the TCP/IP protocol, consult your operating system documentation and help.

For TCP/IP to function properly, your workstation must be able to Ping the server by name and the server must be able to Ping the workstation by name.


Using SmartScout
Workstation Window

Components Window

System Tests Window


WIN.INI Button
WIN.INI is a configuration file for 16-bit Pervasive software. You do not have to edit this file directly - you can use the Win16 Setup utility to do this for you.

1.	Click Start, point to Programs, then to the Pervasive folder.

2.	Select Setup (Win16).


Winsock Defined

An operating system DLL that controls access to socket services to make calls to the network.  You should consult your operating system help documentation or vendor to ensure the version of winsock.dll (for 16-bit) or wsock32.dll (for 32-bit) you have is correct.  The following versions are known to work.  There may be other versions that will work, but these are recommended:

Windows for Workgroups

winsock.dll

Windows 95A

winsock.dll	42080	7/11/95

wsock32.dll	66560	7/11/95

Windows 95B

winsock.dll	42080	8/24/96

wsock32.dll	66560	8/24/97

Windows NT Workstation 3.51

winsock.dll	2880	5/26/95

wsock32.dll	100656	5/26/95

Windows NT Workstation 4.0

winsock.dll	2880	8/3/96

wsock32.dll	20240	8/9/96


Workstation Page Overview

This is the first window displayed when you run SmartScout. The program displays basic information about your workstation in areas of this dialog. To perform a communications and software test, click the System Tests tab.

The following information is displayed on this page:

Local System

Under Local System, SmartScout displays information about your operating system and the amount of free memory currently available on your workstation or server.

Pervasive Products Setup Information

Under Pervasive Products Setup Information, you can edit the 16-bit Pervasive setup files BTI.INI and WIN.INI to check the settings.

Editing BTI.INI

Editing WIN.INI

For Windows NT and Windows 95 systems, you can also view the Btrieve Technologies and Pervasive Software registry entries.

Viewing BTI Registry entries

Viewing Pervasive Software Registry entries

Saving Information

Click Report to display the Report Generation dialog. Using this dialog, you can save or print a report of the information contained on this page.

Exiting SmartScout

Click Done to exit SmartScout and return to Windows.


WpBTRV7.DLL not Found
W1BTRV7.DLL / W3BTRV7.DLL Not Found

W1BTRV7 and W3BTRV7 (AKA "Glue" DLLs) are the Btrieve 7.0 Application Interface DLLs -- the DLLs that all Btrieve 7.0 applications depend upon.

Btrieve 6.15 applications where linked to WBTRCALL and WBTRV32.  These two DLLs are still supplied with Btrieve version 7 for 6.15 applications; however, the DLLs supplied merely pass the application's requests to the appropriate version 7 DLLs. Thus, a 6.15 application will still function with the 7.0 engine and requesters in place.


rfncWin16
Required Files for Network Communication  --  Win16	Required Network DLLs

Now select which server you are targeting:

NetWare

Windows NT


rfncWin16_NT
Required Files for Network Communication  --  Win16  --  NT	Required Network DLLs

Which Protocol do you want to use?

IPX/SPX

TCP/IP


rfncWin16_NT_SPX
Required Files for Network Communication  --  Win16  --  NT  --  SPX	Required Network DLLs

Name Resolution

NETAPI.DLL

Protocol

NWIPXSPX.DLL	(on Windows 3.x workstation)

WINSOCK.DLL	(on WinNT or Win95 workstation)


rfncWin16_NT_TCP
Required Files for Network Communication  --  Win16  --  NT  --  TCP/IP	Required Network DLLs

Name Resolution

NETAPI.DLL

Protocol

WINSOCK.DLL


rfncWin16_NetWare
Required Files for Network Communication  --  Win16  --  NetWare	Required Network DLLs

Which Protocol do you want to use?

IPX/SPX

TCP/IP


rfncWin16_NetWare_SPX
Required Files for Network Communication  --  Win16  --  NetWare  --  IPX/SPX	Required Network DLLs

Which Client service do you use?

Microsoft's Client

Novell's Client


rfncWin16_NetWare_SPX_MSClient
Required Files for Network Communication  --  Win16  --  NetWare  --  IPX/SPX  --  MS Client	Required Network DLLs

Name Resolution

NWCALLS.DLL

Protocol

NWIPXSPX.DLL	(on Windows 3.x workstation)

WINSOCK.DLL	(on WinNT or Win95 workstation)


rfncWin16_NetWare_SPX_NWClient
Required Files for Network Communication  --  Win16  --  NetWare  --  IPX/SPX  --  Novell Client	Required Network DLLs

Name Resolution

NWCALLS.DLL

Protocol

NWIPXSPX.DLL	(on Windows 3.x workstation)

WINSOCK.DLL	(on WinNT or Win95 workstation)


rfncWin16_NetWare_TCP
Required Files for Network Communication  --  Win16  --  NetWare  --  TCP/IP	Required Network DLLs

Which Client service do you use?

Microsoft's Client

Novell's Client


rfncWin16_NetWare_TCP_MSClient
Required Files for Network Communication  --  Win16  --  NetWare  --  TCP/IP  --  MS Client	Required Network DLLs

Name Resolution

WINSOCK.DLL

Protocol

WINSOCK.DLL


rfncWin16_NetWare_TCP_NWClient
Required Files for Network Communication  --  Win16  --  NetWare  --  TCP/IP  --  Novell Client	Required Network DLLs

Name Resolution

WINSOCK.DLL

Protocol

WINSOCK.DLL


rfncWin32
Required Files for Network Communication  --  Win32	Required Network DLLs

Now select which server you are targeting:

NetWare

Windows NT


rfncWin32_NT
Required Files for Network Communication  --  Win32  --  NT	Required Network DLLs

Which Protocol do you want to use?

IPX/SPX

TCP/IP


rfncWin32_NT_SPX
Required Files for Network Communication  --  Win32  --  NT  --  SPX	Required Network DLLs

Name Resolution

NETAPI.DLL

Protocol

WSOCK32.DLL


rfncWin32_NT_TCP
Required Files for Network Communication  --  Win32  --  NT  --  TCP/IP	Required Network DLLs

Name Resolution

NETAPI.DLL

Protocol

WSOCK32.DLL


rfncWin32_NetWare
Required Files for Network Communication  --  Win32  --  NetWare	Required Network DLLs

Which Protocol do you want to use?

IPX/SPX

TCP/IP


rfncWin32_NetWare_SPX
Required Files for Network Communication  --  Win32  --  NetWare  --  IPX/SPX	Required Network DLLs

Which Client service do you use?

Microsoft's Client

Novell's Client


rfncWin32_NetWare_SPX_MSClient
Required Files for Network Communication  --  Win32  --  NetWare  --  IPX/SPX  --  MS Client	Required Network DLLs

Name Resolution

WSOCK32.DLL

Protocol

WSOCK32.DLL


rfncWin32_NetWare_SPX_NWClient
Required Files for Network Communication  --  Win32  --  NetWare  --  IPX/SPX  --  Novell Client	Required Network DLLs

Name Resolution

CALWIN32.DLL

Protocol

WSOCK32.DLL


rfncWin32_NetWare_TCP
Required Files for Network Communication  --  Win32  --  NetWare  --  TCP/IP	Required Network DLLs

Which Client service do you use?

Microsoft's Client

Novell's Client


rfncWin32_NetWare_TCP_MSClient
Required Files for Network Communication  --  Win32  --  NetWare  --  TCP/IP  --  MS Client	Required Network DLLs

Name Resolution

WSOCK32.DLL

Protocol

WSOCK32.DLL


rfncWin32_NetWare_TCP_NWClient
Required Files for Network Communication  --  Win32  --  NetWare  --  TCP/IP  --  Novell Client	Required Network DLLs

Name Resolution

WSOCK32.DLL

Protocol

WSOCK32.DLL