Pros: Unit is easy to configure with included software provided your configuration computer shares the network subnet. Unit can connect to most any wireless network regardless of transmission methodology.

Cons: The WiFi capabilities of the unit make it a good fit for environments with only one wireless network subnet and SSID or where it's the only such device on a network such as a small home WiFi network. The problems arise in facilities where there is more than one active SSID, when channel hopping is required, or when DHCP connectivity absolutely has to work and static addresses can't be used.

The device does not reliably poll DHCP. In my case, I could not get it to hit the active DHCP server once, regardless of setup. No other devices on the large network where I'm employed have any issues obtaining DHCP provided addresses. Strike one.

No reliable DHCP capabilities means that I could only get the device to attach using a static address defined on the unit. That means the unit can't build a DNS record and one has to be built manually so no stateful naming. In large operations where there are dozens and dozens of printers this is a huge issue. Strike two.

The units are easily configured for WiFi networks with one caveat; no channel hopping. The channel must be defined along with the SSID and the encryption methodology. I verified that the device will lose all connectivity if attached to a WiFi network, then moved within the range of a different LWAP running on a different channel but using the same SSID or if the addressing LWAP changes channels to avoid interference. Strike three.

Other Thoughts: These units seem like they'd be perfect if one needs to add wireless connectivity to a printer in a small office with a very simple network or for a home printer. That said, most decent consumer grade printers come with WiFi options installed out of the box. Those options will usually be just as easy to install as the StarTech unit which makes me wonder what market StarTech is aiming for with these devices. They're definitely not robust enough to be used in large scale environments with their channel limitations and their unreliable DHCP polling.

Pros: Worked perfect on a Zebra LP 2844-Z Thermal Printer

Cons: It's a little difficult to setup, but if you have some tech. knowledge you should be able to get through the setup.

Other Thoughts: Things to keep in mind. 1) The default address is 192.168.0.10... this means you're going to have to be on the same subnet in order to login to the print server's web server.

Pros: It does what it says, connect a USB printer to an existing network. Can acquire an IP through DHCP or set as static so can accommodate just about any network configuration. I didn't use the wireless part so I can't comment on that. I used this as a temporary connection on a LaserJet 5035 that got hit by lightning and lost it's NIC until the company decides to get a new printer - worked fine for that except that none of the network features (scan to network folder) of the printer work any more.

Cons: None I can think of

Pros: This little jem is fast, efficient, and easy to set up once you know what you're doing. Had to RMA/exchange the first one - but it turns out that there was nothing wrong with it. It was my own fault in not knowing it had it's own program accessible by directly connecting my Mac to the PM1115UW via CAT5 cable and setting the Mac IP address to 192.168.0.20 so that it would be on the same subnet as the server default IP of 192.168.0.10. At that point - using Safari browser on the Mac - I accessed the print server configuration page and set the server IP address to one that was on the same subnet as my network (192.168.1.108), saved the settings, and from there I was able to install the printer driver and all was good to go. Unit has worked like a charm ever-since.

Cons: Just one - I had to online-chat with their tech support several times before getting the hang of knowing how to reconfigure the server's IP address. Didn't even need to use the setup CD for my Mac to do this.

Other Thoughts: Like I said, just had to go through a learning curve because of my own lack of knowledge about how my LAN (router and other devices on the network) interacted.