Front View

Your 1 and 3-Port Printserver LEDs Following are the LEDs on the front of your PrintServer. The guide below tells you what each LED means. Not all PrintServer models will have all the LEDs. Power The Power LED lights up green when the PrintServer is powered on. The Link LED lights up green when a successful connection is made between the PrintServer and your network through the PrintServers Uplink Port. This LED is labeled as Link/Act on the 2-Port model. The Status LED lights up green when the PrintServer runs a self-diagnostic test while booting up. It turns off when the diagnosis is successfully completed. If this LED stays on too long, see page 44 for Troubleshooting. The Error LED lights up red when there is a problem with the PrintServer or it is writing information to the PrintServer. When assigning an IP address, this LED will also light up for a few seconds.
Dip Switches Settings (1 and 3-Port Models Only) There are three small, white dip switches on the PrintServer that you can use to set your PrintServer to auto-detect or manually set your network speeds. These switches are on the left edge of the 3-Port PrintServer (EPSX3) and on the front of the 1-Port PrintServer (PPSX1). A switch set in the down position is ON. In the up position, the dip switch is OFF. Set your dip switches as follows: Dip Switch 1: This dip switch controls the Auto-Negotiation Mode, which enables the PrintServer to automatically detect the speed (10Mbps or 100Mbps), polarity, and duplex of your network cabling. If Dip Switch 1 is OFF in the up position, Dip Switches 2 and 3 are automatically disabled. Dip Switch 2: This dip switch controls the PrintServers speed. For 100Mbps data transfer, set this dip switch OFF in the up position. For 10Mbps transfer, set the switch ON in the down position. When Dip Switch 1 is OFF, Dip Switch 2 is disabled. Dip Switch 3: This dip switch controls the duplex mode of data transfer. When this switch is set ON in the down position, data transfer runs in half duplex mode. When this switch is set on OFF in the up position, data transfer runs in full duplex mode. When Dip Switch 1 is OFF, Switch 3 is disabled.
Note: The 2-Port Switched PrintServer (EFSP42) does not have any dip switches.

Status

Getting to Know the 10/100 2-Port Switched PrintServer (EFSP42)
The Front Panel LEDs (EFSP42) The Rear Panel Ports
The 10/100 2-Port Switched PrintServer LEDs These 3 LEDs apply to the 2-Port Switched PrintServer only (EFSP42). Link/Act The Link/Act LED lights up a solid green when the PrintServer is successfully connected to a device through that port. If this LED is flickering green, the PrintServer is actively sending or receiving data through that port. The Full/Col LED lights up solid green when a successful full duplexconnection is made through that port. When this Full/Col LED is off, then the data is transmitting in half duplex mode. If the green LED flickers, that connection is experiencing collisions. Infrequent collisions are normal. If the switch seems to experience excessive collisions, verify that your network cabling is securely crimped and installed correctly. If this LED flickers too often, see page 44 for Troubleshooting. The 100 LED lights up orange when a successful 100Mbps connection is made through that port. When the 100 LED is off, then the data transfer rate is 10Mbps.

The 10/100 2-Port Switched PrintServer Ports Power Port This port on the back of your unit connects your Switchs AC Power cord. These two Parallel (LPT) Ports connect to your printers. The Uplink Port, which is shared with Port 1, connects to a standard RJ-45 port on another switch, hub, or router to expand your network. These four ethernet RJ-45 Ports connect to your network devices, such as PCs, other print servers, remote hard drives, and any other networkable device. Use Cat 5 UTP cabling with these ports.

Parallel 1, Parallel 2

Uplink Port

Full/Col

Ports 1 to 4
Linksys Instant EtherFast Series
PrintServer Hardware Installation
Overview The following instructions will get your PrintServer hardware installed and powered on your network. Before starting your physical installation, be sure to find the PrintServers Default Name and Node Address first. The information may be hard to access after the PrintServer is completely installed in your network and surrounded by wires and computers. Finding the PrintServers Default Name On the back or bottom of your PrintServer, there is a white bar code sticker with a SC number printed on it (example: SC123456). This number is the PrintServers Default Name, which youll use in the PrintServer driver installation. Since it is written in hexadecimal form, the SC number may include letters as well as numbers. Write it in the box below for future reference. Finding the PrintServers Node Address To find the node address of the PrintServer, add 00C002 to your PrintServers Default Name. The resulting combined number is your PrintServers Node Address. Write it in the box below for future reference. (example: 00C002123456). For example, if your PrintServers Default Name is SC123456, then your PrintServers Node Address is 00C002123456.
Connecting Your PrintServer to your Network Connecting the Power The PrintServer does not have an ON/OFF power switch. Whenever its AC power adapter is plugged into a power supply, your PrintServer is powered on. The PrintServer can be powered on before, during, or after your network.
Only use the power adapter packaged with the PrintServer. Using a different power adapter could damage your PrintServer.
1. Plug the power adapter into your PrintServers Power Port (on the back of the unit). If you have a Switched PrintServer (EFSP42 only), connect the its power cord to the power adapter, which is larger than the cord, and then plug the power cord into the Switched PrintServer. 2. Plug the power adapter into the wall. The PrintServers Power LED should light up green. Connecting Your Printserver to Your Network If you have a 1 or 3-Port PrintServer (PPSX1 or EPSX3), connect your PrintServer with a Cat 5 UTP cable from the RJ-45 port to a standard port on your switch or hub. If you have a 2-Port Switched PrintServer, complete steps 1 through 4 below. 1. After powering on the PrintServer, plug one end of a Category 5 UTP cable into the PrintServers Uplink Port (EFSP42 only). 2. Connect the other end of the cable into a networked hub or switch. The distance between your Printserver and the second device should not exceed 328 feet (100 meters). 3. The Link and Status LEDs will both become active. If the Link LED does not light up or the Status LED stays on for a long time, see page 44 for Troubleshooting. 4. You can network other computers or peripherals through the PrintServers Switched RJ-45 Ports 1 through 4 (EFSP42 only) at any time. When the PrintServer is powered on, the Switched Ports are always active and will accept new network connections.

IPX Printing in NetWare 5.x, 4.x and 3.x Print Server Mode To set up the PrintServer under NetWare using the IPX/SPX protocol for NetWare 5.x, use an application called Quickset.exe, which is found in the D:\Utility\DOS directory on your PrintServer CD. 1. Log in to the NDS network as an Administrator or as a user with Administrator privileges. 2. Go to the Context (location) where you wish to create the PrintServer object. 3. To use the NetWare Print Server mode, use the following syntax: Quickset Unit_Name (/UN=P) (/Q1=W) (/Q2=X) (/Q3=Y) The Unit_Name is the PrintServers Default Name you copied onto page 10 from the white bar code sticker on your PrintServer, in the form of SC plus 6 digits, which are in hexadecimal form, so you may see letters as well as numbers. P will be the default name of the PrintServer, if you do not specify this option here. W, X and Y are the queues names for parallel ports 1, 2, and 3, respectively. Queues 2 and 3 apply only to the 2 and 3-Port model. If you do not use these options, then the NDS mode uses the following default queue names: NDS_Q1, NDS_Q2 and NDS_Q3 (for parallel ports 1, 2, and 3, respectively.) In the binary mode, Q1, Q2, and Q3 will be the default names. Heres an example, which may differ from your setup depending on what version of NetWare you are using:
quickset SC0C8A02 /un=PS /q1= epson The above example installs the PrintServer SC0C8A02 as a NetWare PrintServer in the current location. Its name is now "PS," and epson is the name for the first printer queue. Remote Printer Mode The instructions below configure the PrintServer for Remote Printer Mode, and establish communication between it and your NetWare 4.x network. Before you begin, make sure you have already set up a NetWare print server resource on a file server or elsewhere and have its name handy. See page 29 for more information about print server resources. You can automatically set up the PrintServer under NetWare 4.x or 3.x with QUICKSET, a small one-time program run from either DOS with simple command-line arguments, or manually through the PrintServers PSCONFIG or Bi-Admin programs. To set up the PrintServer manually, see page 40. Log in as an Administrator or a user with Administrators rights. Run the QUICKSET program in the D:\Utility\DOS directory of the PrintServer CD. The program must run from a MS-DOS prompt. The syntax of the programs command-line arguments must be entered as one long command, as below: Quickset Unit_Name R (/UN=P) (/Q1=W) (/Q2=X) (/Q3=Y) Unit_Name is the PrintServers Default Name you copied onto page 10 from the PrintServers white bar code sticker. P is a user-friendly name you can give the PrintServer. Example: /UN=MARKETING R is the name of the print server resource on the file server that the PrintServer device will log into. W, X and Y are the queues names for parallel ports 1, 2, and 3, respectively. Queues 2 and 3 apply only to the 2 and 3-Port model. If you do not use these options, then the NDS mode uses the following default queue names: NDS_Q1, NDS_Q2 and NDS_Q3 (for parallel ports 1, 2, and 3, respectively.) In the binary mode, Q1, Q2, and Q3 will be the default names.

Caution! Restoring Factory Default will erase ALL of the work that you have done on this unit since purchasing it.

Upgrading the Firmware:

The Firmware Upgrade Icon To make sure that the PrintServer is running its most current version of firmware, upgrade the devices ROM chip regularly. To do so, you must be able to access both the Internet and the PrintServer device from your computer. Click on the Upgrade Firmware icon and follow the instructions on the screen. Exiting Bi-Admin:
The Application Exit Icon To exit the Bi-Admin program, just click on the Exit icon.
Logical Port Configuration:
Logical Port Configuration Icon To set or change the PrintServers logical port settings, highlight the PrintServer to be changed and click on the Logical Port icon (shown above). The Logical Port Configuration window will appear. Make any changes to the settings, and click on Save to Device when you are finished.

Troubleshooting

If your PrintServer is not working correctly, follow the advice in this chapter. If you have trouble printing, see the Hardware section first, and then go to the Printing section. If this Troubleshooting section does not resolve your problem, please see page 91 to contact Linksys Technical Support for help. Hardware Issues Problem 1: Solution 1: Problem 2: Solution 2: All the PrintServer's LEDs are off. Check the power supply and the power connection. PrintServer's Status LED stays lit continuously. Reset PrintServer by unplugging the power supply and plugging it back in. PrintServer Status LED and Power LED stays on continuously and do not turn off. Reset the PrintServer by unplugging the power supply or by turning off you printer(s) and pushing the Reset button. I am using DHCP, and the PrintServer gets an IP Address conflict involving the PrintServer. If the PrintServer is left on when the DHCP Server is turned off, the PrintServer will retain its IP Address without informing the DHCP server. Reset the PrintServer so it will obtain a new IP Address. This problem also arises if you assigned a static IP Address within the range used by the DHCP server. If so, use another address NOT within the range used by the DHCP server. I am having problems using WPCONFIG to configure the PrintServer in Windows 95. WPCONFIG is designed for Windows 3.1 only. For Windows 95, 98, or NT, you should use Bi-Admin. The LED on the side of the 3-Port PrintServer is not lighting up. Check your cabling and make sure that the Link LED on your hub or switch is lit up. Change the dip switch settings on the PrintServer.

2. Print a test text file and a test graphic file. If the text file prints correctly but the graphic file prints garbage, then specify /NT (no tabs) option for NPRINT or CAPTURE commands and print again. If both print incorrectly, go to step 3. 3. Temporarily disable the PrintServer servicing the print queue following the step-by-step instructions below:

NetWare 2.x and 3.x

(a) Run PCONSOLE, Select Print Queue Information, select the print queue that the PrintServer services, select Current Queue Status. (b) Set Servers can service entries in queue to NO. (c) Press Esc and select Print Queue ID. Record the queue ID. (d) Send your test files to the print queue using normal print commands.
NetWare 4.x and 5.x Bindery & NDS modes
(a) Run PCONSOLE, select Print Queues, select the print queue that your PrintServer services, select Status. (b) Set Allow service by current print servers to NO. (c) Press Esc and select Information, and record the queue ID. (d) Send your test files to the print queue using normal print commands. 4. Reroute network printing to local printing. (a) Disconnect the printer attached to your PrintServer and connect it to LPT1 of your PC. (b) Change to the drive and then the directory on the file server that contains the print queue. The direc tory will have the name of the queue ID (e.g. \queues\Q_ID for NDS mode, or system\Q_ID for Bindery mode).
My PrintServer is configured as a NetWare PrintServer, and cannot log in to a file server. Try the following: 1. Get the PrintServer information using PSCONFIG or Bi-Admin. If the device is configured as a NetWare print server, the information will look like the following:
Server Name: SC110049 NetWare Information: Master File Server: ICE Print Server Mode Status: Your_File_Server: Current Status Remote Printer Mode Status: N/A
6. If the file server is not in the status list and the PrintServer has logged into the master file server, it means that the file server has not been serviced by the PrintServer. Check to see if the file server is in the list of File Server To Be Serviced item of PCONSOLE. If not, insert the file server name to the list. Problem 4: Solution 4: My PrintServer is configured as a NetWare Remote Printer and can't log in to the NetWare PrintServer. Try the following steps: 1. Get the PrintServer information as described in Problem 3. 2. Check the fields after the following. Remote Printer Mode Status: For each logical printer, there will be a status entry. The status will be one of the following. Connected: No action required Unable to find server: Load NetWare Print Server. Connecting to Server: Wait and check if the NetWare print server is loaded Printer not Defined Install the PrintServer as a remote printer of a NetWare print server. 3. Check NetWare to see if the PrintServer is ready. If it is not, check the error message and perform the required corrective action. 4. Check the NetWare print server's name. If it is over 20 characters, rename the NetWare print server name using no more than 20 characters.

2. Make sure the master file server name is assigned correctly. 3. Check the Current Status of Your_File_Server: Connected: No action required No file server: Assign a master file server using PSCONFIG or Bi-Admin Connecting to Server: Wait and check if the file server exists Password Mismatch Clear the NetWare password with PCONSOLE, or set the correct password for the PrintServer using PSCONFIG or Bi-Admin. Print Server Not Defined Install PrintServer again 4. Check NetWare to see if the log in status of the PrintServer to the file servers is Ready. If it is not, check the error message and perform the required corrective action. 5. Check the NetWare file server's name for character length. If it is over 20 characters long, rename it with less than 20 characters.
My PrintServer cannot print the jobs sent to the print queue. Try the following: 1. Check if the printer attached to the PrintServer is online. 2. Check if your PrintServer is logged into the file server (See Problem 3). 3. Check the current status of the queue. Run PCONSOLE and select Print Queue Information. Then select the queue and select Current Queue Status. See if there are three YESes. If not, set them to YES. 4. Check if the NetWare printer number is correct. 0 = parallel port 1 of the PrintServer. 1 = parallel port 2 of the PrintServer. 2 = parallel port 3 of the PrintServer 5. Check to see if the PrintServer is a static queue server to the queue. Run PCONSOLE and select Print Server Information. Then select Print Server Configuration and select Queues Serviced by Printer. Then select your desired printer and check if the queue is on the list. If its not, insert the queue into the list by pressing Insert key and select the queue. Then reset the PrintServer to service the new queue. 6. The total number of queues to be serviced may be over the limit of 56. If so, reduce the number of queues.

Problem 7: Solution 7:

PSCONFIG or Bi-Admin shows "No Response." This may be due to the following: The network traffic is busy now. Wait for a minute and then try it again. The PrintServer is not powered on. Power it on. The network cable is disconnected. Check the cable. The node address of the PrintServer may be the same as the node address of another device on the network. QUICKSET timed out when checking if the device had logged in to the file servers. This means that the PrintServer did not log in the master file server. It might be that the Ethernet frame types do not match. 1. Try to find a computer the frame type of the PrintServer using PSCONFIG or Bi-Admin. 2. Enable the PrintServer's frame type to the frame type that the master file server uses and disable all other frame types.

Problem 8: Solution 8:

Problem 9: Solution 9:
I cannot receive Notify message in NetWare 4.x environ ment. 1. Make sure you are a Notify member of the PrintServer. 2. Run NetAdmin and set the name of the Default Server to receive notification. I cannot use PCONSOLE or Bi-Admin to see Printer Status or the current server status in PrintServer Information is showing Down in the NetWare 4.x environment. It may be that you created the print server object in NetWare 3.x environment and used PCONSOLE in NetWare 4.x to view the status. Try the following: 1. Ensure the PrintServer is ON. 2. Delete the print server object of the PrintServer. 3. Install the PrintServer again in NetWare 4.x NDS environment.

Problem 10:

I used the Capture command to print a job, but the job was separated into two parts. The time-out setting in Capture command may be too short. Increase the timeout value of the Capture command by using the option /TI=n of the Capture command to increase the time-out value, where n is the value of timeout.

Solution 10:

Problem 11: Solution 11:
The "String Before Job" and/or "String After Job" set tings in the Logical Printers don't work properly. Check the length of the control strings. No string can exceed 15 characters. Check that the control strings are in HEX. How do I service additional NetWare bindery file servers? If your PrintServer is configured as a NetWare Print Server and you want it to service more than one bindery file server, perform the following steps. 1. Log in, with supervisory rights, to the other file servers you want your PrintServer to service. 2. Create queues and a print server name for your PrintServer on each file server you want to service. 3. Log in, with supervisory rights, to the master file server of your PrintServer. 4. Run PCONSOLE. 5. Select Print Server Information, then select your PrintServer in the print server list. 6. Select Printer Server Configuration, then select File Server To Be Serviced. 7. Insert the file server names of the other file servers to be serviced by your PrintServer. 8. Reset the PrintServer. How do I attach to more than one NetWare Print Server? In NetWare Remote Printer mode, if you want each port of the PrintServer to attach to a different NetWare Print Server, perform the following steps. 1. Use PCONSOLE to create and assign the required printers and queues as detailed in the Remote Printer Mode section. 2. Run PSCONFIG and select Set to NetWare Remote Printer Mode. Enter the correct NetWare print server names in the print server name fields, then select Execute Setup.

Note: For help with the Internet Mail Printing Configuration features, see the guide in D:\Not_supp\Manual directory on the PrintServer Setup CD. Linksys does not provide technical support for this option.
Setting Up TCP/IP and IPX Protocols
Setting Up TCP/IP in Windows Before a computer can communicate with the PrintServer, it must be configured with the TCP/IP protocol. If you know how to set up TCP/IP on your computers, do so now. Otherwise, use the guidelines below to help get TCP/IP installed on all of the computers that need PrintServer access. If you are unable to successfully install TCP/IP on one or more computers after following the directions, contact the manufacturer of your computers' network operating system for further assistance. Check with your network administrator for your TCP/IP settings. The directions below provide general guidelines for coming up with IP addresses and subnet masks. Check with your network administrator to see if you need to use specific IP addresses or DHCP settings. First, each computer on the network will require an IP address, which is a series of numbers, separated by periods, identifying the PC on the network. To make things simple, it is recommended you use the following numbering scheme: 10.0.1.X where X is a unique, arbitrarily assigned number from 1 to 255. Each computer must have its own unique X number. Note: Never use 127 or 255 for X -- these numbers are reserved by TCP/IP for other uses. For example, if you have three computers, you could number them as follows: 10.0.1.17 10.0.1.44 10.0.1.126 In this case, 17, 44, and 126 are arbitrary numbers between 1 and 255. Each computer will also require a subnet mask, which is a numerical filter that tells a computer what kinds of TCP/IP data packets to accept. If youre not sure which mask to use, the following mask is recommended: 255.255.255.0
The following instructions are provided as examples for reference only. For complete instructions on installing and troubleshooting TCP/IP and IPX, consult your Windows operating system documentation. TCP/IP Setup for Windows 98 and 95 1. Click on Start, Settings, then Control Panel. Double-click on the Network icon. 2. If the TCP/IP Protocol is listed for your network adapter, go to step 4. Otherwise, click on the Add button. 3. When the Component Type window appears, click on Protocol, then Add. 4. Select Microsoft in the Manufacturers list, then choose TCP/IP in the Network Protocols list. Click OK. 5. When the Network window reappears, click once on TCP/IP, followed by the Properties button. 6. Click on Specify an IP Address. 7. Enter an IP Address for the computer, along with a Subnet Mask. Click OK. If you do not have these values, consult your network administrator. 8. When the Network window reappears, click OK. Choose to restart your machine. TCP/IP has now been successfully installed. IPX Setup for Windows 98 and 95 1. Click on Start, Settings, then Control Panel. Double-click on the Network icon. 2. If the TCP/IP Protocol is listed for your network adapter, go to step 4. Otherwise, click on the Add button. 3. When the Component Type window appears, click on Protocol, then Add. 4. Select Microsoft in the Manufacturers list, then choose IPX/SPX protocol in the Network Protocols list. Click OK.

Creating a Printer Resource 1. Right-click on the Context again. When the popup menu appears, scroll down to Printer and double-click on it. 2. Enter a name for the printer to be attached to the PrintServer. The name you enter must be the same as the one you gave your NetWare print server when you created it on the file server or elsewhere. When youre finished, click on the Create button. The Context now shows a print server resource, a print queue, and a printer. Configuring the Printer Resource 1. In the selected Context, double-click on the printer object, then click on the Configuration tab. 2. Set the Printer type to Parallel. Click on Communication. 3. Set the LPT value to the appropriate port on the PrintServer where the printer will be connected. Choose parallel (LPT) port 1, 2, or 3 if you have a 3-Port model. 4. Set the Interrupts value to Polled. Set the Connection type to Manual Load. Click OK. 5. Click on the Assignments tab. Click on Add. The queue you created above will appear in the list of available queues. Double-click on it so that it appears in the print queues field. Click OK. Configuring the Print Server Object 1. Double-click on the print server object in the Context. 2. Click on the Assignments button, followed by Add. The printer you created above will appear. Double-click on it. When the printer appears in the Printer List field , click OK. 3. On your file server, take the running print server resource service down, then bring it back up. The setup is complete. Refer to your NetWare documentation to see the PrintServer on the network using PSERVER or another NetWare printer utility.
Adding More Than One Printer (for EPSX3 and EFSP42) If your PrintServer has more than one parallel port and you want to add more than one printer, repeat all of the steps from Creating a Printer Resource on the previous page. When you create a new printer resource, use the same printer name you used for the first printer, with an additional _P2 or _P3 at the end to designate which additional printer youre adding. If printer number one is called myprinter, for example, printer two would be called myprinter_P2, and printer three would be myprinter_P3. If you need to change the PrintServers internal setup or configuration at any time, see page 37 on Bi-Admin.

NetWare 4.x with DOS

Print Server Mode The instructions below explain how to establish communication between the PrintServer unit and your NetWare 4.x network in a DOS environment. 1. Log into your NetWare network as an Administrator. 2. Run NetWares PCONSOLE program from DOS. 3. When the main menu appears, choose Change Context. Enter the name of the context where you want to install the PrintServer. For more information about NetWare contexts, see your NetWare user guides. Creating Queues 1. Select Print Queues from the main Available Options menu. When the Print Queues field appears, press the Insert key on your keyboard. Type in the name of the queue you want to create (example: MARKETING) and press Enter. 2. When asked for the name of the volume where the queue will be installed, press Insert. The Object Browser window appears. Use the arrow keys on your keyboard to move through the list until you find and highlight the volume you want, then press Enter. Repeat for each queue you want to create. The queues will show up in the Print Queues field. When you are finished, press Esc. Creating Printers 1. Select Printers from the main Available Options menu. When the Printers list appears, click Insert and enter the name of the printer you want to create (example: MYPRINTER). Click Enter. 2. Use the arrow keys to highlight the name of the printer you just created and press Enter. 3. Make sure the Printer Type is set to Parallel. 4. Scroll down to Configuration and click Enter.

NetWare 3.x in DOS

The instructions below explain how to establish communication between the PrintServer unit and the rest of your NetWare 3.x network in a DOS environment. PSERVER must be loaded and configured properly on your file server before continuing. Consult your NetWare documentation for information on how to do this. Manual Setup of the Print Server Mode 1. Run the PSCONFIG program, which can be found under the D:\UTILITY\DOS directory on the PrintServer CD. 2. When the table of active devices appears, highlight the PrintServer device you want to configure and press Enter. 3. Choose Set to NetWare Print Server Mode from the Available Options menu and press Enter. 4. Make up a Print Server name and enter it. Write it down; you will need it in a moment. 5. Skip the NDS Tree Name and NDS Context entries. 6. When you reach Master File Server, press Enter to choose from a list of available file servers. 7. Enter a number from 1 to 255 in the Polling Queue, which is how many seconds the PrintServer waits before polling the queue for print jobs that might be waiting. 8. If turned on, Job Notification by Connection ID will automatically notify the file server after a job is complete, allowing the administrator to use PCONSOLE or other programs to monitor users printing. 9. Pick the frame types you want the PrintServer to support. 10. If you want to change the PrintServers configuration password (required for changing the PrintServers internal settings), do so by clicking on Change Password.
11. When you finish, click on Execute Setup to save the PrintServers new changes. Close down the PSCONFIG program. 12. Run Novells PCONSOLE program. 13. Choose Print Queue Information and press Enter. 14. A list of available print queues will appear. Press Insert. 15. Enter the name of the new queue youd like to create and press Enter. Repeat for each new queue youd like to make. 16. When finished, press Esc to return to the Available Options menu. 17. Choose Print Server Information. 18. When the Print Servers window appears, type in the name of the PrintServer you wrote down in step 4 and press Enter. 19. The PrintServers name will show up in the list of available print servers. Highlight it and press Enter. 20. Select Printer Configuration and press Enter. 21. A table of configured printers will appear. The first column shows the names of the configured printers; the second column shows the LPT ports on the PrintServer device. Zero refers to LPT1, 1 refers to LPT2, and 2 refers to LPT3. Press Enter and fill out the information. 22. Enter a name for the printer youre attaching to the PrintServer. (Example: ACE) 23. Choose the Parallel or LPT port that the PrintServer should use. 24. Set Interrupts to No and leave the IRQ and Buffer entries blank. 25. Press Esc to exit. Your new printer will appear in the configured printers list. 26. Press Esc repeatedly until the program ends.

Here are some of the ways your EtherFast 10/100 Switched PrintServer can help you optimize your network speed: (EFSP42 only) Speed up Nodes From Your 10BaseT Network In a 10BaseT network, connect your hubs, file servers and key users such as managers and network administrators directly to your Switch to channel dedicated bandwidth in full duplex mode to each station. The Switch can communicate with all its connections simultaneously, whereas a hub can only communicate with one workstation at a time, in half duplex transfer mode. Conserving Bandwidth with 10Mbps & 100Mbps Segments 10BaseT and 100BaseTX hardware are not readily compatible, but your 10/100 Switch can designate network segments of different speeds. This allows you to run one 10mbps segment to serve users without a need for considerable speed, and a faster 100mbps segment devoted to users who depend heavily on graphics, multimedia, database, or other speed-intensive applications. With switched segmentation, your 100mbps users will not be slowed down by the users on the 10mbps segment. Run 10Mbps Peripherals in Your Fast Ethernet Network Most of the network peripherals in place today run at 10mbps, since 10BaseT has been the standard network speed to date. These peripherals, designed to operate at 10mbps, cannot readily communicate with 100BaseTX equipment. A 10mbps interface is also required for cable and DSL connections, which are quickly becoming very popular ways to access the Internet. Your 10/100 Switch provides your 10BaseT equipment and cable and DSL lines with a 10Mbps interface while still running your Fast Ethernet devices at 100mbps. Strengthen Data Transfers Through Signal Regeneration Your Switch functions as a repeater, which regenerates data signals as they pass through it. This feature acts as a safeguard to deter data loss and ensure that transmissions arrive at their destination intact. Switches positioned between hubs can preserve your datas integrity and eliminate your need to buy and use repeaters in your Fast Ethernet network. Planning Y Installing Your Switch
Connecting Nodes to the Switched PrintServer The back of the Switch has two regular RJ-45 ports and one uplink port. Each port automatically detects the speed, type, and duplex of the cabling attached to it, and can operate in either half or full duplex, giving possible speeds of 200Mbps, 100Mbps, 20Mbps, or 10Mbps. Your switched ports can be connected to computers, PCs, file servers, hubs, repeaters, bridges, or other switches. Each cable connected to the switch must be a Category 5 UTP network cable with RJ-45 tips, and should not exceed 100 meters (328 feet) in length. Ready-to use network cables of various lengths can be purchased at most computer stores. Connecting Computers PCs should be connected to the switch with straight-through Category 5 network cabling. If connecting a computer directly to one of the switch's ports, connect one end of the cable into the switch, then plug the other end of the cable into the computer's 10Mbps or 100Mbps network adapter. Connecting to Other Switches and Hubs Switches, hubs, and similar devices are connected to the switched ports with regular Category 5 cabling via the special uplink port. This port automatically flips the Transmit (TX) and Receive (RX) signals on the wires inside of the cable. Connect one end of the cable to the switched port, then connect the other end to an uplink port on your hub or other device. The uplink port is shared, meaning that it shares its architecture with port number 4 on the switch. If you are using the uplink port, you will lose any connection on port 4. Be sure to disconnect any cabling in port 4 before using the uplink function. When connecting to other hubs and switches, you must use the uplink port. Linksys does not provide any technical support for connections made with crossover cables.

About Bidirectional Printing Normal printing only sends print signals from a PC to a printer. Bi-directional printing, also called bitronic printing, refers to a printer's ability to do just the opposite- talk back to a PC to notify it of a print job status, paper jams, etc. This two-way communication technology can be found in HP, IBM, Panasonic, and other laser or color printers where close contact between the PC and printer is key. In color printing, for example, the printer "informs" the PC of its constant status in order to mix color inks correctly for optimal quality output. Bidirectional communication, communication from a printer to a PC, is normally handled by a combination of the printer hardware and special software on your computer. Bidirectional printers generally have highly advanced parallel interfaces. These printers often require special parallel ports in order to take full advantage of their features. Using a bidirectional printer on a network poses unique challenges. Unlike a direct PC-to-printer connection in which a bidirectional printer can easily send its signals back to the host PC through the computers parallel port (which is normally located only a few feet away from the printer), a networked printer faces the problem of having to route messages bound for a particular PC through a large array of hubs, switches, file servers, and computers. Unfortunately, most printers are not equipped to handle the complexities of printer-to-PC communication across a network. That does not mean that they cant be used on a network, however. Linksys designed the EtherFast 10/100 PrintServers to function with both regular as well as bidirectional printers. Standard print servers cannot work with bidirectional printers, but the EtherFast PrintServer features a custom design to support both parallel as well as bidirectional parallel interfaces. However, the EtherFast PrintServer cannot pass messages from the printer back to the printing PC -- this limitation is simply an industry standard, and not one of the PrintServer itself. However, the PrintServer can check any printers online and printing status on the network with the Bi-Admin management utility software packaged with the PrintServer. The status-checking feature built into the management software does not require a bidirectional printer to function. If your printer came with special bidirectional software allowing you to monitor printer status, do not use it with the PrintServer - the software is most likely not network-capable. For best results, turn off the printers bidirectional function either by (1)
removing any bidirectional printing software from your network computers, and/or (2) turning off the printers bidirectional print feature inside of the printers on-board menus (if it has menus). Your printers user guide should be able to provide specific instructions for doing this. About the PrintServer Software The PrintServer is fully compatible with Windows 98, Windows 95, Windows NT 4.0, and NetWare. When used with Windows 98, 95 and NT, the PrintServer uses the TCP/IP protocol for network communication. Each computer on your network that needs PrintServer access will need to have the TCP/IP protocol installed. TCP/IP installation files are included on your original Windows 95, 98 or NT CD-ROM. For tips on installing TCP/IP, see page 56. When operating under NetWare, the PrintServer uses IPX/SPX for communication, which is built into the NetWare network operating system. Most computers need only be able to log into the network in order to print after the PrintServer has been configured. NetWare 5.x supports the use of both IPX/SPX and TCP/IP. Instructions for the setup and configuration of IPX/SPX are provided on page 42 in the NetWare 5.x section of this user guide. TCP/IP instructions are provided on page 56. Please be aware that although Linksys provides instructions for the setup of the TCP/IP protocol, these instructions are provided for reference only. Linksys will not provide technical support for the configuration and troubleshooting of the TCP/IP protocol. For full instructions on using TCP/IP, consult your operating systems user guide.

Note: Throughout the user guide, it is assumed that the CD-ROM drive on your computer is designated as letter D. If your CD-ROM drive is designated as a different letter, use that letter instead.
EFSP42: EtherFast 2-Port Switched PrintServer EPSX3: EtherFast 3-Port 10/100 PrintServer PPSX1: EtherFast 10/100 PrintServer Standard IEEE 802.3, IEEE 802.3u Topology Star Protocol CSMA/CD Ports One Power Port EFSP42:One 10/100 RJ-45 Uplink Port; Four Autosensing 10/100 Ports; Two bidirectional parallel ports EPSX3: Three bidirectional parallel ports PPSX1: 1 bidirectional parallel port Buttons and Switches Reset button (EPSX3 & EFSP42) Three dip switches (EPSX3 & PPSX1) Max Speed (Mbps) 200 or 20 (Full Duplex) 100 or 10 (Half Duplex) Cabling Type 10BaseT Category 3 (10BaseT) 100BaseTX Category 5 (100BaseTX) LED Indicators (EPSX3 & PPSX1)Status, Link,Error, Power EFSP42:Link/Activity per port, 100Mbps per port, Full/Coll per port, Power Model Numbers
For help with the installation or operation of your EtherFast 10/100 PrintServer, contact Linksys Customer Support at one of the phone numbers or Internet addresses below. For the latest version of this User Guide, visit the Linksys website to download an Adobe Acrobat PDF version. Customer Support Fax Email Website FTP Site 800-326-7114 949-261-1288 949-261-8868 support@linksys.com http://www.linksys.com ftp.linksys.com
Extended Technical Support The 2-Port Switched PrintServer (EFSP42) supports the NetBEUI and Appletalk protocols, SNMP management, Internet Mail Printing, Unix support, HP JetDirect emulation, and much more. However, Linksys is neither responsible nor liable for supporting these optional features, and will not provide phone or online support for these features. In the Not_supp directory on your PrintServer Setup CD, you'll find software, drivers and informative how-to guides covering the installation of the unsupported functions. The User Guides provided in the Not_supp directory (PDF or DOC) have all of the information you need to set up and use these functions.
Dimensions Unit Weight EFSP42:7.5 x 5.4 x 2.0 EPSX3: 9 x 5.5 x 1 PPSX1: 7.5 x 5.4 x 1.4 EFSP42:1 lb. 3 oz. EPSX3: 14 oz. PPSX1: 1 lb. FCC Class A, CE Mark Commercial, 12VDC, 1Amp Maximum

comp.unix.sco.misc: Printing woes with print servers on 5.0.7
Printing woes with print servers on 5.0.7
Source: http://unix.derkeiler.com/Newsgroups/comp.unix.sco.misc/200411/0023.html
From: Dan Sadaka (NodanSPAM_at_website1.com) Date: 11/02/04
Date: Tue, 02 Nov 2004 13:25:52 0500
Greetings. I just setup two 5.0.7 systems with MP3, both on IBM eSeries servers. On one system, all printing is fine. This is the "smaller" system25 users vs 50 users. On the larger system, I have tried two different print servers: Lantronix and now Linksys. I have never had problems with Lantronix before. The Linksys EPSX3 3port parallel print servers are now attached (two of them). Both have the same problem. Symptoms: Send a single or maybe two jobs and printing is fine. Send multiple jobs and only one prints. The rest stay in the queue. restart the lpd process and the first one prints again. No communication problems exist (e.g. ping, telnet, lpstat all work fine.) Could lpd be running out of processes or file handles? I say this because the problem only exists on the larger server. I know that all the system tunables are "supposed" to be dynamic now, but one never knows. I activated sar and a sar v shows: 11:48:37 procsz ov inodsz ov filesz ov locksz (v) 11:48:37 sar data collection enabled 12:00:00 205/ 753/884/360/ 512 12:20:00 205/ 749/880/354/ 512 12:40:00 208/ 760/857/327/ 512 13:00:00 205/ 755/850/318/ 512 13:20:00 188/ 705/781/276/ 512
comp.unix.sco.misc: Printing woes with print servers on 5.0.7 What other sar options should I use? lpstat main shows (for printer main) qfhost.queensflowers.com: sending to epsserverroom ReqId Owner Size Date main805 root 732 Nov 2 13:23 main794 root 732 Nov 2 13:23 main795 root 732 Nov 2 13:23 main796 root 732 Nov 2 13:23 main797 root 732 Nov 2 13:23 main798 root 732 Nov 2 13:23 main799 root 732 Nov 2 13:23 main800 root 732 Nov 2 13:23 main801 root 732 Nov 2 13:23 main802 root 732 Nov 2 13:23 main803 root 732 Nov 2 13:23 main804 root 732 Nov 2 13:23 main806 root 732 Nov 2 13:23 main807 root 732 Nov 2 13:23 main808 root 732 Nov 2 13:23 main809 root 732 Nov 2 13:23 main810 root 732 Nov 2 13:23 (LPD Server): (P1)STATE: Idle TYPE: Parallel PRINTER STATUS: OnLine Has anyone else had this problem and resolved it? TIA, Dan