Active4 months ago
NexRemote cable with USB-TTL Serial UART Converter Cable with FTDI Chip - posted in Celestron NexStar: Hello, Not a very frequent poster here on CN. Not exactly sure where I should post this, think this might be the place to start. It automatically reassigns the same COM port values to each port, so when the cable is disconnected or the system is rebooted, no additional configuration is needed. The FTDI USB to serial adapter also supports RS485 auto-transceiver turn around with unique featured ATTA hardware, as well as remote wake-up and power management. Ftdi Usb To Rs232 Serial Converter - DOWNLOAD. Device Drivers - USB Support - USB Serial Converter Support - USB FTDI Single Port Serial Driver This approach uses the stock L4T 21.4 kernel, not the Grinch one. If you want to use the Grinch, you will have to install the Grinch kernel sources instead of the stock kernel sources.
I have a client(Windows 7 Pro) that make a connection to Windows terminal server through RDP, i have enabled COM port redirection for both server and client side, but the redirection doesn't happen ...
The client don't have a native mainboard COM port, but have an USB-TO-Serial adapter (Prolific USB-to-Serial), it is possible redirect this USB-TO-Serial COm Port ?
alerootaleroot
2,77655 gold badges2525 silver badges3636 bronze badges
5 Answers
If you're running 2008r2 and win 7 ultimate, you do have the option to look at remotefx USB redirection... to redirect USB devices... or look at 3rd party software like this.
TheCompWizTheCompWiz
It's not currently possible without 3rd party software. Windows sees this device as a USB device, not a COM port (yes I understand the irony). RDP doesn't currently support remote USB devices (hopefully some day it will).
Chris SChris S74.3k1010 gold badges112112 silver badges204204 bronze badges
I don't think the accepted answer here is entirely correct.
Right next to me is a barcode scanner connected to a Prolific USB2Serial adapter connected to a Windows 7 client (with installed Prolific Drivers). The Client sees this Prolific Adapter as COM3.
Now if I connect to any terminal server while allowing ports to be mapped (Options > Local Resources > More. Check 'Ports'), that virtual COM3 will be available on the Terminal Server with no problem.
So to answer the question:
If you can install drivers on the Terminal Server Client machine and you install the Prolific driver, then you can enable Port redirection on the Client and the Port will be available and working correctly on the Server.
If you can't install drivers on the client, you will need an external 3rd party software as it was linked by @TheCompWiz
pilifpilif
I had a USB-based serial port for a credit card reader that I needed to redirect through RDP. I configured Remote Desktop to make ports available to the remote session. Initially, I had the serial port to COM100 (to easily avoid potential conflicts), and it didn't work. It did work, however, when I changed the port to COM2.
Ftdi Usb Serial Port Remote Desktop Windows 7
Edward BreyEdward Brey
We specifically use these adapters professionally with POS receipt printers and they work fine. Just know that you can't use the windows drivers on the server and need something that maps the ports via the registry such as the OPOS drivers we use for the receipt printers.
Ftdi Serial Converter
andrew robertsandrew roberts
Not the answer you're looking for? Browse other questions tagged windows-7rdpterminal-serverwindows-terminal-services or ask your own question.
When you troubleshoot issues with a serial device, there are some quick tests that you can complete to rule out potential problems. You can test to make sure that the following components are working correctly and are not the source of the issue:
Usb Serial Port Driver Download
- Serial cables
- Serial ports
- Serial devices
To test your setup components, try the following:
- Use the serial cable, serial port, and serial device in another setup to see if the problem is with the components or the setup.
- Use a different serial cable, serial port, and serial device in your setup to see if the problem persists. Ideally, you should test a component that you know works in another setup.
When you test your cables, it is recommended that you do the following:
- Test each cable individually.
- Use short cables when you are testing.
When you test the serial ports and serial device, it is recommended that you do the following:
- Press the Windows key + R, type devmgmt.msc, and press Enter to open Device Manager. Check to see if your device is listed under Ports (COM & LPT).
- Make sure that the COM port number is the correct number for the serial device and that the software being used to connect the computer to the serial device uses the correct COM port number.
- If you do not see the COM port number in Device Manager see this FAQ for PCI/PCIe expansion cards: https://www.startech.com/support/faqs/technical-support?topic=expansion-cards#pci-pcie-cannot-boot-os-or-detect-windows
or this FAQ for USB devices: https://www.startech.com/support/faqs/technical-support?topic=expansion-cards#usb-cannot-detect-windows - If the device is listed with an error, follow the instructions on the website to reinstall the drivers.
Note: Some serial devices work only if the COM port number is between a certain range. For example, COM1 to COM4.
- Perform a serial loopback test. See this FAQ on how to perform a RS-232 serial loopback test: http://www.startech.com/faq/serial_loopback_test_rs232_windows