DS-510 USB to Gigabit Ethernet USB Device Server & AC Power Supply

I've not had much success with other print servers, I tried a couple and they worked for a while and then stopped. This one seems very stable. I used it for a DYMO 4XL. Once your print driver is installed. You hook up power, hook up the wire from your router, and the USB from your printer and you're on your way. You need one last thing. Its SX Virtual Link Software. This allows it make your computer believe the printer is directly connected to your printer by USB, even though it is on a network. It will say available. When you click on the printer, it will say connected. You can also disconnect and make it available again if you want. Of course, no two computers can use the same USB port.To solve this problem, if you are on another computer (where you must also have the SX software setup), you click on the Request Use button. I have the release time for each computer set to release in 10 seconds. So, if someone forgot to disconnect the printer from their computer, you can disconnect them from your computer by clicking on request use. It works flawlessly. The one thing I couldn't get it to do was automatically disconnect from the DYMO after it was done printing, but the request use accomplishes it almost as well. Of course, the other approach is to disconnect each time you're done. But, here, one of us uses the DYMO all the time and the other rarely use it. So, it makes sense to stay connected for one and for the other to request use for them to be disconnected.If this continues to work as well as it has been, it will be the best print server I've bought. The request use button solves any concern that someone might not disconnect and leave and then you'd not be able to use the printer. If it automatically disconnected, it would be even better, but that could be the DYMO and not the unit itself. That might vary from printer to printer. To do all the setup for these features, right click your printer when it shows in the SX software and make changes to the settings under connect and disconnect. They will be fairly obvious.In short, close to perfect. I say close because it would be absolutely perfect if it automatically disconnected from the DYMO, but its inability is not enough for me to lower it to a 4 because of the many bad servers I have had from mainstream vendors on Amazon, including those rated as top rated.. Also, it's not all that inconvenient to disconnect and connect on each computer. Thought it would be. It isn't. The Request Use just makes that easier and saves you from someone who has forgotten to disconnect. It will count the 10 second down and you will see it is working. The default is 120 seconds. That's too long for DYMO which prints immediately though you may want more than 10 seconds if your printer might print for a while after someone starts printing. This is more expensive and maybe that's why it works better, a bargain given how much trouble I had with other print serves going on and off randomly.

My Xfinity account requires an Arris cable modem. This modem has 2 USB ports that I thought I could connect with an external drive holding family pictures and videos the same way used with WD modem on the earlier cable service. As it turned out both USB ports are permanently disabled. The best go around this issue turned up to be Silex DS-510 device server with the Ethernet port connection to the Arris modem. I used USB cable to connect Silex with an external USB drive. I downloaded Device Server Setup for Windows file to set all up. Important tip - make sure that you turn on network discovery and file sharing at Network and Sharing Center\Advanced sharing settings. The PDF software installation manual at Silex site is very good, and after software installation was finished the drive was discovered immediately. I installed only the Computer configuration part on other computer and the drive came up, but I had to disconnect drive access on the first computer. The external drive can be accessed only from one PC at the time.

Works well for connecting my external USB drive to my network. You can only have one device connect to it at a time but that works for my situation. I thought having to use software to connect to it would be a pain but it's not. The software is basically one click to connect to the drive and then you're connected the entire time you're on your wireless network.

Seems to work fine, but be aware that they haven't released drivers for OSX 10.11 (El Capitan), so I'm stuck still using Yosemite. No ETA on them releasing new drivers so not sure if this going to end up being a $100 door stop. :(Update: Got an email from Silex indicating they're working on the driver with Apple and should have more information later this month. Not saying the driver will be ready by then, but it's good to know they're working on it!Update #2: Months later and still no update. And now Apple has released MacOS 10.12. I'm still using 10.10 which is now two major releases behind and I've noticed that my MacBook Pro seems to have kernel instabilities after using the DS-510 with my 3D printer. Hence I'm dropping my review from 4 to 2 stars because Silex doesn't seem serious about OS X support.Update #3: Silex has just released a beta version which they claim is compatible with the latest macOS Sierra OS release (Version 10.12.1). I've already moved on to a different solution for my needs, but figured I'd update my review with this latest information.Update #4: Silex just released their "official" version (3.18.0) for macOS Sierra and it not only failed to install correctly, but has totally ruined my system to the point where now I'm probably going to have to re-install the OS. Basically the Silex driver installer fails to install while "configuring components" (probably the kernel driver or something) and hangs. I waited 2 hours and finally had to turn off my computer (won't let me gracefully shutdown). When I rebooted and login, my login screen now takes up about 85% of the screen after I log in. (See screen cap) I tried uninstalling the driver and that didn't fix the problem. I ended up re-running the macOS Sierra installer (downloaded from the AppStore) and effectively "re-upgraded" my Mac to 10.12.2 which fixed the problem. Tech support admits they haven't tested with 10.12.2, so I highly recommend you wait until they've fixed this problem.