Re: thin client com ports

Vera,

First and formost...thanks for all of your input on this topic. Its been
greatly appreciated.

I have looked at the pdf from Topaz in the past but dont recall anything
about a locally residing driver. I will have to take a look at it
again..thanks for bringing it up. However I do know that I didnt install the
driver on the XPe thin client and its RDP session works. So perhaps the term
"locally" means on the local server.

Since my last post I have reflashed the 1125 with 4.4.079 and have actually
had a halfway good result. I am at least now sending data and seeing the com
ports being redirected with a change port command from the console. However
my demo application and production application still dont recieve any data
from the com port. So I have a call setup for tomorrow with a Topaz tech to
see if there is something he can assist with.

One last thing....do you think that perhaps now that I can see data flow
with Hyper Terminal and not communication between the pad and applications
that it could be some type of permissions issue with the applications?

I am very new to 2k3 server and have found that permissions are a bit more
tricky or as some might call pesky when doing things as compared to 2k server.

Just a shot in the dark at that last comment...but I feel that I am getting
ever so close to actually getting this to work.

Again, thanks for all of your comments.



"Vera Noest [MVP]" wrote:

If the signature pad needs a locally installed driver, you'll need
XPe. The specs seems to indicate that:
http://www.topazsystems.com/products/specs/TS460.pdf

But this site
http://www.badgestuff.com/proddetail.asp?prod=TS460
claims that the signature pad is supported on CE.NET and linux thin
clients.
Have you contacted the Topaz reseller / manufacturer?
I'm sorry, I've never worked with signature pads, I don't think
that I have much more to contribute.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SVRndXlfU0hDTUhD?=
<ITguySHCMHC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 30 maj 2007 in
microsoft.public.windows.terminal_services:

I just typed a book and when I posted it...it got lost in
cyberland.

To sum my last thoughts up though...

I am testing several thin clients. they are as follows

WYSE thin clients

1125SE w/ Thin OS 4.4.079
3125SE w/ CE.NET 4.2 Pro
9455 XL w/ Win XPe

Devon IT Thin Client

6020A w/DETOS (linux derrived)

The hardware I am connecting is a Topaz TS 460 1x5 signature pad

I have 2 Win 2k3 Server R2 SP2 running as DC's and TS's for
redundancy.

The 1125 when connected to an RDP session shows not to have
mapped the com ports when using the "change port /query"
command. Of course nothing works because the com port has not
been redirected.

The 3125 (CE) when connected via RDP session does show the com
ports to be redirected by the change port command. However my
demo program or even my production application doesnt show any
communication. However I can test communication to the device
via Hyper Terminal and it does show dataflow, however it is
corrupted data with alot of incomplete packets.

The 9355 (XPe) works fine. I can launch into the XPe
environment and then launch and RDP session (making sure that I
chose the Local Resoures option "Serial Ports") and the sig pad
works fine in all ways (Demo and Production App). The com ports
also show to be redirected.

The 6020A (linux) does show the com ports being redirected
however the serial ports cause my Demo and Production App to
lock up. After talking to tech at the manufacturer...Ive
decided that there is nothing I nor they can do to make these
work.

I also have tested from an XP Pro SP2 desktop via RDP and this
works fine as well.

So based on all of that, I am really wanting to get either the
1125 (Thin OS) or 3125 (CE.NET) working. This will be more like
the environment that my users are accustomed to logging in for
the past year. If I have to go with XPe thin clients...I will.
But I would rather avoid all of the helpdesk calls that will
come with the XPe thin clients and users having to log into an
XP like desktop and then launch an RDP session. I have thought
about putting an RDP session in startup...but there will still
be confusion when/if they minimize that session to the desktop
or even close it out by accident. Like I said...I would rather
have a thin client that has only one option from a connection
manager into an RDP session.

Thanks for your help and input.



"Vera Noest [MVP]" wrote:

As I wrote, that would be "\tsclient\COM1", not
"myclient\COM1".

What do you mean with "the CE.NET client shows that the port is
redirected"? Does the output from the change port /query
command resemble that on the webpage I referenced?
Because if that is the case, then the port *is* redirected, but
it doesn't work with your application. That's a totally
different problem :-)

What device do you connect to the COM port?
What kind of application is trying to use the COM port? And is
it 32-bit or 16-bit?
And in what way does it fail? Any error message?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SVRndXlfU0hDTUhD?=
<ITguySHCMHC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 29 maj 2007 in
microsoft.public.windows.terminal_services:

Vera,

So what you are saying is that there is no manual map or
redirect command?

I am somewhat familiar with the change port /query command.
And I do see the mapping take place if I use an RDP session
originating from an XP box or an XPembedded thin client.

However the CE.NET thin clients, even though show that the
com ports are redirected....do no work with the application.
The Thin OS thin clients dont show any mapping at all....thus
my question on a way to do in manually.

In my research on this topic I found that when working with
com port redirection and "I think" 2k server that you use the
net use command to manually map the com port as follows....

net use com1: \\myclient\com1: or similarly net use com1:
\\name-of-client\comwhatever:

I just thought there was a way manually map the com port from
a devices netbios name to the com port on the server.



"Vera Noest [MVP]" wrote:

If the rdp client on your thin client doesn't support COM
port redirection, I don't think that it will work.

But if you want to give it a try, the redirected COM1 port
is \tsclient\COM1

Check
http://ts.veranoest.net/ts_faq.htm#verify_COM_ports
to see how it looks like when they are redirected.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SVRndXlfU0hDTUhD?=
<ITguySHCMHC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 29 maj 2007
in microsoft.public.windows.terminal_services:

The Thin OS is version is 4.4.079 and the CE.NET is 4.2
Pro.

The Thin OS does have serial port settings but nothing
"windows like" as far as settings go that are in the RDP
client (Options, Local Resources, Bring to this Machine --
Serial Ports).

However, I was under the impression that I could map the
serial ports manually with a "net use" or "change port"
command. I was thinking that the setting in the RDP
client that I mentioned above does the mapping and if I
knew the syntax to do it via command line...it should
work????

As far as upgrading the firmware....there is only 1
version newer Thin OS and its not available for non
support Wyse customers yet. The Windows CE.NET I am in
the same boat as well.

Thanks

"Vera Noest [MVP]" wrote:

Which version of ThinOS, CE.NET and rdp client?
If the rdp client doesn't support COM port redirection, I
would start by checking for a firmware update.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

=?Utf-8?B?SVRndXlfU0hDTUhD?=
<ITguy_SHCMHC@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote on 25 maj
2007 in microsoft.public.windows.terminal_services:

I am having a problem finding a way to map com ports
from thin clients to a windows 2003 R2 terminal server.

I have no problem using RDP from an XP Pro box or even
an XPe thin client. I am assuming this is because I
can enble the serial ports being brought to the local
device the RDP session is launched from.

However the majority of my thin clients are WYSE 1125
and 3125SE's which are ThinOS and CE.NET OS
respecitvely. There is no RDP settings to make the
mapping.

I am assuming there is a command such as "net use" or
"change port" to manually do this for each thin client
on the server that needs to use COM1 or 2. But I
cannot find any material explaining this.

Any thoughts on this are greatly appreciated.

Thanks

.

Relevant Pages

  • Re: thin client com ports
    ... specific instructions on the COM port settings. ... I am testing several thin clients. ... The 1125 when connected to an RDP session shows not to have ... port redirection, I don't think that it will work. ...
    (microsoft.public.windows.terminal_services)
  • Re: thin client com ports
    ... I am testing several thin clients. ... The 1125 when connected to an RDP session shows not to have mapped the com ... ports when using the "change port /query" command. ... redirection, I don't think that it will work. ...
    (microsoft.public.windows.terminal_services)
  • Re: thin client com ports
    ... I am somewhat familiar with the change port /query command. ... However the CE.NET thin clients, even though show that the com ports are ... redirection, I don't think that it will work. ...
    (microsoft.public.windows.terminal_services)
  • Re: thin client com ports
    ... specific instructions on the COM port settings. ... I am testing several thin clients. ... The 1125 when connected to an RDP session shows not to have ... port redirection, I don't think that it will work. ...
    (microsoft.public.windows.terminal_services)
  • Re: thin client com ports
    ... I am testing several thin clients. ... Of course nothing works because the com port has not ... The 3125 when connected via RDP session does show the com ... port redirection, I don't think that it will work. ...
    (microsoft.public.windows.terminal_services)
Loading