Prev: the publisher could not be verified
Next: Client Printer Ports Missing for USB
From: Bett on 13 Jun 2006 17:45
Hello,

We have a teller application that uses a serial receipt/validation printer.
We are testing it to run on Windows 2003 Terminal Server with or without
Citrix Presentation Server 4.

We are trying to get printing working without Citrix using the Epson TM-U375
printer. With Citrix we are able to print to our receipt printers in the
teller application. With TS 2003, we can test print out of the redirected
serial device with an echo statement, but cannot print in the teller app.

We are using thinstation for the client for these tests also.

These test prints work:

Citrix: echo test > COM1

Terminal Server: echo test > COM2

We have had to map COM2 for Terminal Server, and changed our vendor's
instructions a bit for Terminal server versus Citrix:

NET USE COM2: \\TSCLIENT\COM2

works to map the printer and to do a test, but teller printing does not
work.
The app does not return an error, but it does hang up.

Citrix on the other hand is able to print our simple test and also print
from the teller program with the net use statement provided by the vendor.

NET USE COM1: \\CLIENT\COM1:

When I run NET USE in the ICA session it looks a lot cleaner than in the RDP
session. For example, in my RDP session, my C: drive is mapped to COM1, and
I cannot access the drive. Example:
------------------------------

New connections will be remembered.


Status Local Remote Network

-------------------------------------------------------------------------------
C: \\tsclient\com1 Microsoft Terminal Services
C: \\tsclient\COM1 Microsoft Terminal Services
C: \\tsclient\COM1 Microsoft Terminal Services
C: \\tsclient\com2 Microsoft Terminal Services
C: \\tsclient\com1 Microsoft Terminal Services
C: \\TSCLIENT\COM1 Microsoft Terminal Services
C: \\tsclient\com1 Microsoft Terminal Services
C: \\tsclient\COM1 Microsoft Terminal Services
OK F: \\bettstest01\apps Microsoft Windows Network
OK H: \\bettstest01\users\tsuser
Microsoft Windows Network
OK S: \\betsrvr09\share Microsoft Windows Network
OK T: \\bettstest01\tsusers\tsuser$
Microsoft Windows Network
--------------
RDP session Change Port command results:

AUX = \DosDevices\COM1
COM1 = \Device\RdpDrPort\;COM1:3\tsclient\COM1
--------------

If anyone has any suggestions for me, they are welcome. At this point,
Citrix is looking like the only option.

Thanks in advance.
From: Cl?udio Rodrigues on 14 Jun 2006 07:47
Have you tried using a Windows client instead of Thinstation? Thinstation
from what I remember is Linux based and uses RDesktop what is known for not
fully supporting RDP5.2. And keep in mind this will just get worse when RDP6
is out; in almost 4 years since 2003 came to the market, they still do NOT
support RDP5.2 so I can only see things getting worse for RDP6.
I have nothing against Linux but I would not base a corporate solution on
RDesktop at all.
Try the real RDP client for Windows (get the latest off the Microsoft
website) and see what happens.
It may simply work.

--

Cl?udio Rodrigues

Microsoft MVP
Windows Server - Terminal Services
"Bett" <Bett(a)discussions.microsoft.com> wrote in message
news:DA5DDB62-B27B-4D02-B8D8-1C9020096E29(a)microsoft.com...
> Hello,
>
> We have a teller application that uses a serial receipt/validation
> printer.
> We are testing it to run on Windows 2003 Terminal Server with or without
> Citrix Presentation Server 4.
>
> We are trying to get printing working without Citrix using the Epson
> TM-U375
> printer. With Citrix we are able to print to our receipt printers in the
> teller application. With TS 2003, we can test print out of the redirected
> serial device with an echo statement, but cannot print in the teller app.
>
> We are using thinstation for the client for these tests also.
>
> These test prints work:
>
> Citrix: echo test > COM1
>
> Terminal Server: echo test > COM2
>
> We have had to map COM2 for Terminal Server, and changed our vendor's
> instructions a bit for Terminal server versus Citrix:
>
> NET USE COM2: \\TSCLIENT\COM2
>
> works to map the printer and to do a test, but teller printing does not
> work.
> The app does not return an error, but it does hang up.
>
> Citrix on the other hand is able to print our simple test and also print
> from the teller program with the net use statement provided by the vendor.
>
> NET USE COM1: \\CLIENT\COM1:
>
> When I run NET USE in the ICA session it looks a lot cleaner than in the
> RDP
> session. For example, in my RDP session, my C: drive is mapped to COM1,
> and
> I cannot access the drive. Example:
> ------------------------------
>
> New connections will be remembered.
>
>
> Status Local Remote Network
>
> -------------------------------------------------------------------------------
> C: \\tsclient\com1 Microsoft Terminal
> Services
> C: \\tsclient\COM1 Microsoft Terminal
> Services
> C: \\tsclient\COM1 Microsoft Terminal
> Services
> C: \\tsclient\com2 Microsoft Terminal
> Services
> C: \\tsclient\com1 Microsoft Terminal
> Services
> C: \\TSCLIENT\COM1 Microsoft Terminal
> Services
> C: \\tsclient\com1 Microsoft Terminal
> Services
> C: \\tsclient\COM1 Microsoft Terminal
> Services
> OK F: \\bettstest01\apps Microsoft Windows Network
> OK H: \\bettstest01\users\tsuser
> Microsoft Windows Network
> OK S: \\betsrvr09\share Microsoft Windows Network
> OK T: \\bettstest01\tsusers\tsuser$
> Microsoft Windows Network
> --------------
> RDP session Change Port command results:
>
> AUX = \DosDevices\COM1
> COM1 = \Device\RdpDrPort\;COM1:3\tsclient\COM1
> --------------
>
> If anyone has any suggestions for me, they are welcome. At this point,
> Citrix is looking like the only option.
>
> Thanks in advance.


 | 
Pages: 1
Prev: the publisher could not be verified
Next: Client Printer Ports Missing for USB