HDE USB to Serial Interface Cable with Serial to RJ45 Console Adapter Cable for Cisco Routers

Worked in a VERY oddball environment.So I was building a virtualized environment for a friend. They work on OOOLLLDDD crap and need serial in many flavors. Using Oracle VB, I created several VMs from DOS 6.22, Win98SE, NT4, and XP. The host laptop was running Win10 Pro with the drivers installed. After setting up the Oracle USB extension pack for Virtual Box, and setting the hyper visor to pass that USB serial port as a native Serial Port on COM1, this device worked on EVERY oddball old software thrown at it. Only one was difficult, so I allowed the XP VM to access this dongle directly, and BOOM, it had drivers!!!The application worked as expected after that. Mind Blown. Great little dongle.

At the community college where I teach, there are many computers with only USB slots for serial connections. I had Cisco console cables that were RJ-45 to 9-pin serial and several serial-to-USB adapters but not really enough to satisfy my student pool. I ordered the HDE USB to Serial Interface Cable and it works like a charm. The shipping was very quick and we were in business right away. Drivers are seamlessly downloadable from the web and the cable works great under Windows 7 and 10.

Pros:Very in expensive and I didn't even have to make it.No drivers or additional configuration was required for it to work. (under linux)Tips:Works great on linux with little effort (new versions of linux may require root privileges to use the port)On ubuntu based distros expect to find the device present under /dev/ttyUSB0Works great with Watchguard Firebox XTM 5 series console port.Buy one they are cheap and very handy especially for older hardware (since it has a functional serial adapter)Cons:None this is a perfect product if you know what it does and it does it perfectly!

Got this cable to connect to an Oracle Database Appliance. The shipment came to me on time and in new condition. When I first tried to connect to my servers I could not get a connection. At first I thought maybe the cable was bad, so I plugged into a spare network switch I had. My switch had no problems connecting to my notebook. OK. Back to square one. After playing with my notebook & server baud rates AND after downloading new Proliant cable drivers I was finally able to connect to my Oracle hardware. The drivers that come with the cables are VERY hit or miss, and you should not rely on them. Not every piece of hardware will work with the included drivers.

I bought this cable and a 6 Ft FTDI USB to RJ45 for Cisco Console Cable over 2 years ago. Looking at the 2 cables, this cable looks like a quickly put together homemade cable vs the ftdi cable. I was skeptical that it would work well but figured it's only $7. Initially, I used the ftdi cable but started running into weird issues where my console session would freeze or in some cases not work at all (especially with WLCs). Where the ftdi cable failed, this cable has succeeded. I've been able to make a successful console connections to every single Cisco device I've ever tried when using this cable. Also, the extra 2 feet in length vs the ftdi cable has come in handy on more than 1 occasion. When you're troubleshooting, you don't want to worry about whether your console cable will work and with this cable I've never had to. I know it sounds as if I work for the manufacturer; I don't. I'm just very pleased with the cable!

Well, when I am wrong, I will admit it. I found that this console cable did not automatically get recognized by windows 10. I had sent an email to the vendor, thinking there wasn't much that was going to happen. Well, I guess I eat crow on this one. I admit it.The manufacturer responded and provided me with a link to the new drivers. Com port is now recognized. Console cable works as it is supposed to.Granted it took them an extra day to respond because of the country time zone, but all in all, I am satisfied. They were extremely happy to help me. Will definitely order their product again.

Needed to console port into Cisco switches etc. Using PuTTY (serial COM3 9600 8n1 no flow control) to configure. Main issue was W10 install of correct ch340 driver for the serial chip used but not insurmountable to the user familiar working with serial devices. I think the PCI/Vendor substring windows uses to search for the correct driver is not formatted correctly, or in the database, but I got it working regardless. Just not a completely smooth sail when my included driver DVD got broken during travel over the months and needed to use it on a different laptop later. Bit of fun finding the driver but once ch340 installed & done, works again.

Drivers are useless on included CD.So this is obviously not some OEM product and can tell from the mini cd that comes bundled with this, is some bootleg electronic. Heck - it's super cheap and the adapter does work under OSX and Windows 7 with some additional config.The Vendor ID under OSX is listed for the ch340 chipset. This is NOT the common PL2303 Prolific chipset found on most serial-usb cables.Please download this driver package for whatever OS of choice and you should be good to go! :D>https://drive.google.com/file/d/0B5okZr5AW4gaX2pZaWt6dVNaSFU/edit>Source : http://javacolors.blogspot.com/2014/08/dccduino-usb-drivers-ch340-ch341-chipset.html