The FTP Software PC/TCP kernel interfaces between the Barr software and the TCP/IP network. Follow the instructions in the PC/TCP Kernel User’s Guide to install the PC/TCP kernel.
After you install the FTP software, configure the PC/TCP kernel to work with the Barr software by editing the PCTCP.INI file located in the directory where you installed your FTP software (the default directory is C:\PCTCP). Then verify that you can access the host.
In the PCTCP.INI file, you only need to change the PCTCP KERNEL section (see the following sample), which contains parameters that apply to PC/TCP kernel operation. Some of the fields might vary, depending on the conventions at your site.
Enter the serial-number and authentication-key. You can find this information printed on your product registration card. If your version of the software is not serialized, this information will not appear on your registration card.
You might need to adjust the large-packets field. After you start the Barr PC, use the PC/TCP INET DEBUG utility to determine if you need to change the value of this field. If the INET DEBUG utility indicates that packets are over allocated, decrease the value of large-packets. If the utility indicates that packets are under allocated, increase the value of large-packets.
Allot two tcp-connections for each print queue session you specify in the Barr software. For example, if you use four print queue sessions, set tcp-connections = 8.
The kernel-does-dns field allows you to use a local host table to translate host names into IP addresses. You do not need this setting if you have a domain name server (DNS) on the network.
After you install the ETHERNET2 or ETHERNET PCI adapter, adapter driver, and FTP software, you should be able to access the TCP/IP network.
You can use the ping command with a host address to verify you are connected to the network. The ping command sends an echo request to another host. Enter the command from a DOS prompt as in the following example:
ping 130.203.13.6
See your PC/TCP Kernel User’s Guide for more information about the ping command.
You should receive a host responding message when you connect to the TCP/IP network. If the host does not respond, you probably have a PC/TCP kernel or TCP/IP configuration problem. Check your ip-address and subnet-mask in the interface section of the PCTCP.INI file. For other problems, work with your network administrator. You might find the Troubleshooting the Kernel and Driver Configuration chapter in your PC/TCP Kernel User’s Guide helpful.