Suddenly I needed a wireless print server. After a great experience with Linksys products in the past, they got my purchase. As you read, please note that I am a former network administrator and have installed many genuine (HP, Lexmark, etc.) network print servers in the past. It took me a little over three hours to finally get it working. Most Linksys products come with good to excellent documentation and are easy to set up - even if you need to change settings or use a non-Linksys network. This is not a typical Linksys product. The documentation does not properly describe the installation process and factory configuration. The instructions were written in such a way that if something went wrong the instructions would be useless. To find out the factory configuration, you need a non-postscript printer. Chances are if you set this up something will go wrong and the documentation will become less than useless. What went wrong with me? First, the setup program didn't detect the print server over the wireless connection or the network cable. It seems to have undocumented compatibility issues with Windows XP. In an attempt to bypass the configuration, I tried to determine the factory configuration. I couldn't because I only had a PostScript printer. After moving it to another house with a non-postscript printer, I found that the default IP address is 0.0.0.0 (which you can't connect to) and that it's not an IP address of mine received from the DHCP server. Luckily, I also have a computer running Windows 2000. The software could see the print server from that computer, and I was able to set it up the way I wanted, or so I thought. When I installed the printer driver software, I found that the name I gave the print server didn't matter - it was still using the factory name when I "browsed" it. The configuration software saw this as my name and the driver software saw it as a factory name. The lack of communication between these pieces of software is another example of how immature drivers and firmware are. Another example is the need to navigate to a subdirectory on the CD to install driver software. Configuration software installed by autoran from CD. The installation is not integrated. Once started it seems to get the job done if you like the name Linksys gave it! Conclusion: o Compatibility problems with WinXP and the tuning tool The factory configuration is very difficult to handle o Immature installation process and driver of the setup tool. The driver and the setup tool do not "see" the same settings. A non-PostScript printer is strongly recommended. The documentation is exceptionally poor.
π» Cisco-Linksys PPS1UW EtherFast USB PrintServer with Wireless Capability
8 Review
Monoprice Networking USB Print Server
8 Review
Wireless-G USB Print Server from Hawking Technology HWPS1UG
8 Review
π¨οΈ Cisco-Linksys EPSX3 EtherFast 10/100 3-port PrintServer: Simplify Your Printing Workflow
8 Review
π USR-TCP232-410s: RS232/RS485 Serial to Ethernet Adapter/IP Device Server with DHCP/DNS Support
4 Review
π StarTech.com NETRS232 Serial to IP Ethernet Device Server - DIN Rail Mountable - Serial Device Server - Serial Over IP Device Server (Black)
4 Review
HB-UMLS Sabrent USB 2.0 Hub with 4 Ports and LED Power Switches for Each Port
12 Review
π uni USB C Hub with Ethernet Adapter, 4K HDMI, Gigabit Ethernet, and 3 USB 3.0 Ports for MacBook Pro, iPad Pro, XPS
11 Review