This chapter provides information on the supported TCP/IP and Named Pipes network configurations. It serves as a checklist to help you ensure that the basic elements are installed and running on the client and server machines.

Refer to your network and operating system documentation for detailed information on installing the software and services required to run . Your software provider assumes no liability and does not guarantee the accuracy of this information.

This chapter contains the following sections:

• TCP/IP Support
• Named Pipes Support
• Novell Using Named Pipes Support
• LAN Manager Using Named Pipes Support

The following protocol stacks are tested and supported:

Client Support:

• Microsoft Windows 95 or Windows 98 Native TCP/IP

Server Support:

• Windows NT or Windows 2000 Native TCP/IP from Microsoft
• Microsoft Windows 95 or Windows 98 Native TCP/IP 
• HP-UX Native TCP/IP from Hewlett Packard
• AIX Native TCP/IP from IBM
• Solaris Native TCP/IP from Sun Microsystems
• Linux Native TCP/IP for Red Hat
  
  

  Note:

  Check the conventional memory requirements of these drivers to ensure that you have sufficient memory available.

  This section provides general steps for installing TCP/IP.

Server

  TCP/IP is included with Windows and UNIX platforms. As part of defining the Windows or UNIX computer with the TCP/IP protocol, the computer name and IP address are defined during the operating system's installation.

Client

To install TCP/IP on a client machine, follow these steps:

1. Install one of the supported protocol stacks.
2. For each server on the network, update the client HOSTS file to contain an entry for the server. For example, the following entry would be made for the server MAPLE at IP address 198.137.238.10:

    198.137.238.10   MAPLE
   

  The HOSTS file specifies the IP address of the server so the client can communicate with the server. A host is any device attached to the network that uses TCP/IP. To receive and deliver packets successfully between hosts, TCP/IP relies on information in the HOSTS file.

  Different TCP/IP vendors store HOSTS files in different locations, and some vendors allow you to change the location. The following describes the individual requirements for the protocol stacks supported.

FTP: In the installation directory, FTP stores the file PCTCP.INI in which you specify the location of the HOSTS file. To set the location (in this case, to C:\PCTCP\HOSTS), add the following line to the[pctcp kernel]section of the.INI file:

 

 host-table=C:\PCTCP\HOSTS

  If you specified HOSTS during installation, this line is added automatically.

  Before attempting an client-server connection, you should test the protocol installation to ensure the connection is installed properly.

  Use the PING command on the server to check that it is running and visible to your PC client. If the PING command is successful but the TELNET command is not, then there may be a problem with the inet daemon. If the PING command is unsuccessful on the server, you might have a routing or hardware problem.

  The following protocol stacks are tested and supported:

  Client Support:

• Microsoft LAN Manager (NetBEUI)
• Microsoft Windows 95/98 Native NetBEUI

  Server Support:

• Windows NT/2000 Native Named Pipes (NetBEUI)
• Microsoft LAN Manager (NetBEUI)

  _______________ supports the Named Pipes protocol stack on Novell Netware LANs (local-area networks). Novell currently supports Named Pipes services for PC clients connecting to Windows NT servers, but does not offer support for UNIX servers.

  This section contains information on connecting the Windows 95 or Windows 98 client computer to Windows NT or Windows 2000 servers using Named Pipes.

  To connect from Windows 95 or Windows 98 to Windows NT or Windows 2000 using Named Pipes, you might need to connect to the Windows NT or Windows 2000 server  To connect to the Windows NT or Windows 2000 server:

1. Open Network Neighborhood from your Windows 95 or Windows 98 desktop.
2. Locate the server name in the list. Double-click the server name.
3. If prompted, enter the password for the server, then click OK.

    

    

     Figure 61: Entering the Server Password

4. When you are connected to the server, the server window appears showing one or more directories to which you have access.
5. Close the server window and Network Neighborhood.

   Now you are ready to connect

  When connecting from Windows 95 or Windows 98 to Windows NT or Windows 2000 using Named Pipes, if you see the error message, Network error: Cannot receive data, try increasing the maximum number of connections on your Windows 95 or Windows 98 machine:

1. Select Start > Settings > Control Panel.
2. Double-click the Network icon.

     The Network dialog box appears.

3. In the list box entitled The following network components are installed, locate and double-click the option for NetBEUI. If you have more than one NetBEUI option, choose one of them.

     The NetBEUI Properties dialog box appears.

4. Click the Advanced tab.
5. Select Maximum Sessions in the Property list box. Increase the Value of the maximum sessions setting. You may need to experiment with this setting. In the example below, the setting was increased from 10 to 20. When done, click OK.

    

    

     Figure 62: Increasing the Maximum Sessions Value to 20

6. Click OK to close the Network dialog box.
7. Close Control Panel. If prompted, reboot your machine.

  Novell supports Named Pipes service in its IPX protocol environment.

After installing Windows NT or Windows 2000, install the NWLINK IPX/SPX driver on the Windows NT or Windows 2000 server. Select the Network options during installation or configuration of Windows NT or Windows 2000, and select NWLINK IPX/SPX.

  Novell does not currently provide Named Pipes requestors for UNIX.

  _______ supports the Named Pipes protocol stack on Microsoft LAN Manager LANs. Microsoft currently provides Named Pipes services for PC clients connecting to Windows NT servers, but does not offer support for UNIX servers.

Windows Clients

  LAN Manager workstations must meet the following requirements:

• Workstations must use LAN Manager 2.0 Enhanced (or above) drivers and have Named Pipes permission.
• Users executing "Net Logon" must attach to the appropriate server machine in the correct domain.

Windows Servers

  LAN Manager support for Named Pipes service under Windows NT or Windows 2000 is built-in, using NetBEUI.

UNIX Server

  LAN Manager does not support Named Pipes service to UNIX.