Not too long ago, Netcfg2 experienced trouble configuring IOPRINT+ print server on a UNIX network. The problem, described in TechRepublic’s forums, was this:

I have recently moved my network hardware into a much larger room. As a result, I need to install an IOPRINT+ print server. It has two parallel ports and one serial port. I assigned a static IP address and connected the print server to a hub. I was able to ping the IOPRINT+. I then connected two Okidata 395 dot matrix printers to the two parallel ports.

At that point, I was able to create logical ports called L1 and L2 (although they’re physically in P1, P2). My problem is trying to print from a UNIX Alphaserver running True64. I was able to add the IP address and default printer names in the /etc/hosts file. I also ranarp -s defaultname IP addressto link the physical address and the IP Address.

I can ping the print server using either the server name or IP address in UNIX. When I try to open the print manager in UNIX, though, the window opens slowly and lp1 updates for a long time and then appears to freeze. Why is this happening, and what do I have to do to finish the process?

Thanks to a colleague, he found his answer. Mshavrov, who was awarded 200 TechPoints for his response, wrote in with the solution:

As I understand it, you completed only the first step. Now, you must configure your printer and printing queues.

I have ExtendNet Print Server, and it has the ability to use two printers. You must define two queue names for the print server, and when you define the printer in UNIX, name it as “Remote Printer Name.”

So keep in mind the following keywords:

“Remote System Name”—IP Address or Name of Print Server.

“Remote Printer Name”—Queue Name how it is in Print Server.
Wait no more! Get help from your colleagues in TechRepublic’s forums.If you’d like to share your opinion about this article, please send the editor an e-mail or post a comment below.