T10 Serial Redirection to RDP Issues

  • This topic is empty.
Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #8370
    Homes32
    Participant
    • Total Post: 5
    • Newbie

    T10 Serial Redirection to RDP Issues

    Hi guys. I’m having issues redirecting serial ports for use in a PURE RDP environment.

    The thin client recognizes that the usb to serial cable is connect to port 3 and assigns it to COM3. (I don’t know why COM3 and not COM1 or COM2 this is the only serial to usb cable to ever be plugged into this device but I’m getting off track…)

    running change port /QUERY from a command prompt in the RDP session shows the ports as being redirected


    C:Usersfakeuser>change port /query
    AUX = DosDevicesCOM1
    COM1 = DeviceRdpDrPort;COM1:8tsclientCOM1
    COM2 = DeviceRdpDrPort;COM2:8tsclientCOM2
    COM3 = DeviceRdpDrPort;COM3:8tsclientCOM3
    COM4 = DeviceRdpDrPort;COM4:8tsclientCOM4
    NONSPOOLED_COM1 = DeviceSerial0
    NONSPOOLED_COM2 = DeviceSerial1

    however nothing I do (printing to COM3 from software/testing with generic/txt printer to COM3/echo “testing<1B>E” > COM3/etc) will make anything print to the device. can anyone offer me any insight as to what the issue could be here?

    I know the adapter and printer/cables are good as the device works as expected if I don’t forcelocal the usb device and allow the adapter to show up as a new COM port on the RDP server but this is not desirable because this is a load balanced environment AND the software we are using only supports using COM1-COM9 (hint: we have more than 9 workstations) so just to clarify I need COM redirection not to get the serial to usb adapter to show up in the RDP session.

    thank you in advance to anyone that can offer any advice as to what the issue could be.

    Vital Info
    Thin Client: Wyse T10
    Firmware: 8.0_306
    Serial Adapter: 920207-11L (Wyse USB to Serial Adapter)
    RDP Session Host: Server2k8R2, TCX Server installed, RDP local Policy allows serial redirection
    Printer: Epson TM-U325D

    wnos.ini


    ;*************************************************************
    ; Thin Client Global Settings
    ;*************************************************************

    ; Our Pretty Logo
    FormURL=logo.png

    ; Speed up boot by only looking for DHCP
    BootpDisable=yes

    ; Disable WDM Service because we don't use it.
    WDMService=no

    ; Disable display of the sign-on dialog
    signon=0

    ; Look for firmware and AutoUpdate if needed
    Autoload=2

    ; Use Modern Zero Toolbar Mode
    SysMode=vdi

    ; Date/Time
    Timeserver=XXX.XXX.XXX.XXX Timeformat="24-hour format" Dateformat=mm/dd/yyyy
    TimeZone='GMT - 06:00' ManualOverride=yes Daylight=yes Start=030207 End=110107 TimeZoneName="Central Standard Time" daylightname="Central Daylight Time"

    ;*************************************************************
    ; VNC Shadow
    ;*************************************************************
    MaxVNCD=1 VNCD_8bits=yes
    VNCPrompt=no
    VncPassword=XXXXXXXX

    ;*************************************************************
    ; SNMP Serivce
    ;*************************************************************
    Service=snmpd disable=no
    community=wyse

    ;*************************************************************
    ; RDP Session Settings
    ;*************************************************************
    SessionConfig=RDP
    EnableGFX=yes
    EnableRFX=yes
    EnableNla=yes

    ;*************************************************************
    ; Default RDP Connection to RDFARM
    ;*************************************************************
    Connect=RDP
    Host=RDFARM
    Description="Connect to Server"
    Domainname="MYDOMAIN"
    Fullscreen=yes
    AutoConnect=yes
    KeepAlive=5
    Lowband=yes
    Mapdisks=yes
    Rdp_No_Animation=yes
    Rdp_No_Dragging=yes
    Rdp_No_Fontsmoothing=no
    Rdp_No_Theme=yes
    Rdp_No_Wallpaper=yes

    ;*************************************************************
    ; Peripherals
    ;*************************************************************
    Device=vusb ForceLocal=0x067b,0x2303,0x00,0x00,0x00
    Serial=COM3 Baud=9600 Parity=None Stop=1 Size=8 Flow=CTS/RTS Touch=No Touch_XYreverse=No

    Event Log


    14:55:36 System Start Date: 2014/09/26 Friday DST
    14:55:36 System Version: HF 8.0_306
    14:55:36 CPU Version: Marvell PJ4 v7 Processor-wmmx rev5 (v7l)
    14:55:36 Ethernet device version: MV Gigabit Ethernet.
    14:55:36 CESA: driver register OK.
    14:55:36 Embedded Controller Version: 3.04
    14:55:36 VGA: offscreen video ram = 207 MB
    14:55:36 Initializing Certification Center ...
    14:55:36 AUDIO: Change record device to DOVE Audio
    14:55:36 AUDIO: Change playback device to DOVE Audio
    14:55:36 VUSB: Local Device(0x05e3,0x0608,0x09,0x00,0x01)
    14:55:36 USB: Found a new 480Mbps device "HUB" on port 1
    14:55:37 Waiting for network link ...
    14:55:37 USB serial cable attach to COM3
    14:55:37 USB: Found a new 12Mbps device "uplcom" on port 3
    14:55:38 VUSB: Local Device(0x04f2,0x0112,0x03,0x01,0x01)
    14:55:38 USB: Found a new 1.5Mbps device "HID" on port 4
    14:55:38 USB: Found a new 1.5Mbps device "HID" on port 4
    14:55:39 Looking up IP address from DHCP ...
    14:55:45 Obtain IP[XXX.XXX.XXX.XXX] from DHCP server[XXX.XXX.XXX.XXX]
    14:55:45 DHCP lease time: 7 day 00:00:00
    14:55:45 Contacting File Server ...
    14:55:45 Accessing system profile ...
    08:55:45 SNMP: Community is set to wyse
    08:55:45 VUSB: Force Local (0x067b,0x2303,0x00,0x00,0x00)
    08:55:46 Checking Software ftp:/wnos/DOVE_boot ...
    08:55:47 Contacting SNTP [XXX.XXX.XXX.XXX] ...
    08:56:08 RDP: Start session to RDFARM
    08:56:08 RDP: Connect to RDFARM ...
    08:56:08 RDP: NLA CredSSP Authentication
    08:56:09 RDP: Start session to XXX.XXX.XXX.XXX
    08:56:09 RDP: Connect to XXX.XXX.XXX.XXX ...
    08:56:09 RDP: NLA CredSSP Authentication
    08:56:09 RDP: Bitmap Codec RemoteFX
    08:56:12 TCX USB: Server connected
    #25022
    ConfGen
    Keymaster
    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    Why are you using TCX?
    Have you tried to remove ForceLocal and add
    Device=UsbSerial Start=COMx (where x is the desired portnumber)?

    CG

    #25041
    Homes32
    Participant
    • Total Post: 5
    • Newbie

    thanks for the reply.

    @ConfGen wrote:

    Why are you using TCX?

    Because phase 2 involves getting a UareU 4000 fingerprint reader and safenet/rainbow auth token working on the same RDP server

    @ConfGen wrote:

    Have you tried to remove ForceLocal and add
    Device=UsbSerial Start=COMx (where x is the desired portnumber)?

    CG

    yes I have.
    Device=UsbSerial Start=COMx gets ignored. doesnt matter if I say COM1/COM2/COM3/COM4 if I plugin the serial adapter to port 3 (back closest to DVI port) it will show up on COM3. if I plug it into port 4 (back closest to edge) it will show up in event log as COM4. this is the case on every T10 I have tested on here.

    Have you tried to remove ForceLocal
    Also a yes. As I said in my initial post if I remove ForceLocal the serial device shows up as a new port in RDP session (COM5/6/whatever depending on the load balanced host it connect to) but the thin client will still not print to the COM3 port on the thin client even though the change port command will list the ports as being redirected.


    14:52:54 System Start Date: 2014/09/29 Monday DST
    14:52:54 System Version: HF 8.0_306
    14:52:54 CPU Version: Marvell PJ4 v7 Processor-wmmx rev5 (v7l)
    14:52:54 Ethernet device version: MV Gigabit Ethernet.
    14:52:54 CESA: driver register OK.
    14:52:54 Embedded Controller Version: 3.04
    14:52:54 VGA: offscreen video ram = 207 MB
    14:52:54 Initializing Certification Center ...
    14:52:54 AUDIO: Change record device to DOVE Audio
    14:52:54 AUDIO: Change playback device to DOVE Audio
    14:52:54 VUSB: Local Device(0x05e3,0x0608,0x09,0x00,0x01)
    14:52:54 USB: Found a new 480Mbps device "HUB" on port 1
    14:52:55 Waiting for network link ...
    14:52:55 USB serial cable attach to COM3
    14:52:55 USB: Found a new 12Mbps device "uplcom" on port 3
    14:52:56 VUSB: Local Device(0x04f2,0x0112,0x03,0x01,0x01)
    14:52:56 USB: Found a new 1.5Mbps device "HID" on port 4
    14:52:56 USB: Found a new 1.5Mbps device "HID" on port 4
    14:52:57 Looking up IP address from DHCP ...
    14:53:07 Obtain IP[XXX.XXX.XXX.XXX] from DHCP server[XXX.XXX.XXX.XXX]
    14:53:07 DHCP lease time: 7 day 00:00:00
    14:53:07 Contacting File Server ...
    14:53:07 Accessing system profile ...
    08:53:07 SNMP: Community is set to wyse
    08:53:07 Checking Software ftp:/wnos/DOVE_boot ...
    08:53:08 Contacting SNTP [XXX.XXX.XXX.XXX] ...
    08:58:33 RDP: Start session to RDFARM
    08:58:33 RDP: Connect to RDFARM ...
    08:58:33 RDP: NLA CredSSP Authentication
    08:58:33 RDP: Start session to XXX.XXX.XXX.XXX
    08:58:33 RDP: Connect to XXX.XXX.XXX.XXX ...
    08:58:33 RDP: NLA CredSSP Authentication
    08:58:34 RDP: Bitmap Codec RemoteFX
    08:58:36 TCX USB: Server connected
    08:58:36 USB serial cable detach from COM3
    08:58:36 VUSB: Redirected Device(0x067b,0x2303,0x00,0x00,0x00)
    08:58:36 USB: Found a new 12Mbps device "WYSE VUSB" on port 3
    08:58:36 VUSB: redirect device 4 (PID: 0x2303, VID: 0x067b)
    08:58:36 TCX USB: Redirect device on port 3
    #25209
    Homes32
    Participant
    • Total Post: 5
    • Newbie

    Figured I’d post an update in case there is another poor soul out there looking for answers.

    After opening a ticket with dell/wyse we figured out that as of this post the latest firmware (8.0.411) is broken when it comes to V2 of the Serial-To-USB adapter. Yes. apparently there are 2 versions of the wyse adapter with different prolific chips. U232-P9V2 is the part number on the back of the adapter for version 2. The only firmware that works with v2 is 8.0.214 (technically 8.0.210 “works” as well but coredumps alot) BUT only with None or XON/XOFF as flow control. Hardware flow control is broken in all available 8.x firmware releases.

    The good news is that the latest test firmware seems to have fixed the issue so if you don’t need hardware flow control you can revert to 8.0.214. other wise you are stuck waiting for the next release.

    regards,

    Homes32

Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.