Document Number: NIPRSUP1008
Product: NIPrint (any version)
Date: 11-5-97
Title: Setting up TCP/IP on a Win 95/98 PC (for use with a print server)
Setting up TCP/IP on a Win 95/98 PC (for use with a print server)
Disclaimer: This document is intended as a general guide for UNIX system administrators who wish to set up a solution similar to that described here. No warranties apply and the procedures described are unsupported by Network Instruments.
This document is to serve as a brief guide to setting up a TCP network for printing to an lpd-enabled printer (Tektronics, Lantronix, HP JetDirect, Xerox, etc.). The benefits of printer sharing and the speed of printing via TCP makes this a popular network combination, and remember that this will co-exist with an existing protocol or protocols (like the Windows peer-to-peer networking).
We’re assuming that you’re using Windows 95, and that the ethernet hardware is in place and that you DON’T already have a TCP/IP protocol in place (if you do, see your LAN administrator instead of following these steps). Our example network will consist of three Windows 95 PCs and one ethernet-attached printer. The steps follow:
1. Plan the IP addressing scheme
2. Address the printer and specify the subnet mask
3. Add the TCP/IP protocol in each Windows 95 PC and set address
4. Test the TCP connection
5. Install and Configure NIPrint
1.Plan the IP addressing scheme
Each node must have a unique IP address. You’ll also need to specify a subnet mask, but this will be the same for each node. Rather than go into IP addressing in detail (many references are available if you’re curious), we will supply a simple numbering scheme:
Name |
IP Address |
Subnet Mask |
Printer |
200.100.100.1 |
255.255.255.0 |
John’s PC |
200.100.100.2 |
255.255.255.0 |
Jackie’s PC |
200.100.100.3 |
255.255.255.0 |
Jane’s PC |
200.100.100.4 |
255.255.255.0 |
2. Address the Printer
Make sure that the printer (or print server if it’s an external box that the printer plugs in to) is set to use TCP printing and enter the address and the subnet mask. Each manufacturer’s method for doing this is unique, so check your printer documentation or give them a call if you need help with this step.
3. Add the TCP/IP protocol in each Windows 95 PC and provide address
In Windows 95, go to the Start button, Settings, Control Panel, Network. This screen will list the existing network components. Hit the Add button, Protocol, Microsoft, TCP/IP. This will bring you back to the Network window and you’ll see TCP/IP listed. Click on it and then click the Properties button, then choose Specify and IP address, and you’ll see the dialog for entering the IP address and subnet mask Enter them, hit Ok and Ok again, and you’ll be prompted to restart Windows. Once Windows comes up again, your protocol and addressing for that PC should be in place. Repeat for the other PCs.
4. Test the TCP connection
Once the TCP protocol is installed and the addresses are in place, you’re ready to test to make sure you have TCP connectivity. The most basic test is by using a “ping” command. In Windows 95, access it by going to Start, Programs, MS-DOS Prompt. At the DOS prompt, the syntax is “ping <address you want to test>”, so for our example go to John’s PC (which is 200.100.100.2) and type (at the C:\WINDOWS> prompt):
ping 200.100.100.1
If successful, it will return this (or something similar) almost immediately:
Pinging 200.100.100.1 with 32 bytes of data:
Reply from 200.100.100.1: bytes=32 time=1ms TTL=128
Reply from 200.100.100.1: bytes=32 time=1ms TTL=128
Reply from 200.100.100.1: bytes=32 time=1ms TTL=128
Reply from 200.100.100.1: bytes=32 time<10ms TTL=128
If not, it will return:
Pinging 200.100.100.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
From one PC, you should be able to ping each address in turn. Obviously if you have one or more that are not successful you’ll want to go back and check your steps before continuing. You will not be able to print via TCP if your ping tests are unsuccessful.
5. Install and Configure NIPrint:
Install NIPrint using default settings. Since NIPrint needs to be running in order to send your print jobs, you will probably want an NIPrint shortcut in the Startup folder so it starts automatically.
Next, run NIPrint and go to the Configuration, General Settings screen and check the Enable Remote Print Server checkbox. Hit Ok and go to Configuration, Remote Print Configuration. Click Add Printer. At this point, you need to specify the NAME of the printer. What can be challenging is knowing the appropriate printer or queue name that lets you access the TCP/IP lpd capability. This is the name you need to use in Remote Print Configuration in NIPrint. Since these devices are made to work in many environments (Netware, AppleTalk, Unix), the documentation doesn’t usually say “Here’s the name you use to access lpd in so-and-so mode”, so it’s hard to get that info without a call or two to the manufacturer, so here’s as much information as we’ve gathered in order to at least provide an example (listed by manufacturer):
Tektronix:
PS
AUTO
HP JetDirect:
May be found as an internal device in some printers, or an external box. Make sure that lpd capability exists (the box may require an additional SIMM that has lpd embedded). The name is typically referred to as “host name” on the status pages that you can print. If it doesn’t list the host name, it’s possible that it’s dynamic, which means that you can make one up in Remote Print Configuration.
Lantronix:
For the MPS devices, the name is MPS_(6 numbers)_(mode). For example:
MPS_0D9ED3_PS
MPS_0D9ED3_PCL
MPS_0D9ED3_TEXT
Xerox (DocuTec):
lp
Emulex:
TEXT
PASSTHRU
Once you’ve entered the appropriate printer name and the IP address of the printer, enter the User name and then hit Ok and then the Save button. There are advanced settings available, but the defaults are fine for now.
When you Save the remote printer in NIPrint, the program adds a new port to the printer ports list in Windows 95. The next step is to add a printer to Windows 95 for the new printer and connect it to this new port. Add the new printer driver as you normally would (Start, Settings, Printers) from the list or unlisted (if you’re using the driver from the printer manufacturer). As you add it, there will be an option for Local or Network printer. You must choose Local. Then go through the normal installation until you get to the port selection. Choose the NIPrint port from the list (it will look like “c:\ni\out\printername\job” in the ports list); then finish.
To test the whole thing, choose an application in Windows 95 (like Word or something simple) and print a short document. If you don’t get output, check the Remote Print Trace in the NIPrint Help menu, or call Network Instruments for help. |