Microsoft Operating System Forum

Legatus

I am running a couple of 2k3-R2 servers as Terminal Servers .
The majority of my users are connecting to the TS by means of WYSE S10 and
WT1125SE, wyse ThinOS.

On a couple of them I need a modem connected on the com port.
The application running on the TS need to connect to the modem connected to
the com port on the Wyse terminal client.

I have com port redirection enabled on both of my TermServs. On the
1125SE's and S10(thin OS) I dont know the command to map the com port to the
thin client. Can anyone help please!

/Jim


On the 3125(CE.NET) there is RDP settings to bring the com port to the local
machine...but this doesnt work either.



So in short. Is there anyone here that has had success in mapping com ports
to thin clients that are non XPembedded driven? I can get this to work fine
if using RDP sessions from an XP workstation or XPe thin client. However I
dont want to have to replace all of my equipment if I can get it working on
existing thin clients.

Oliver Schröder

Jim,

RDP com-port redirection should work fine with any thin-client supporting
RDP 5.1 or higher.
There is no "command" to redirect the ports, you just have to check the
appropriate checkbox. If there is no such checkbox, the integrated
RDP-client does not support com-port redirection. Maybe then there is a
firmware-update for the thin-client. You have to ask the manufacturer.

The problem with Linux-ThinClients is that their RDP-support is only 95 %
Microsoft-conform. So often things do not work exactly as they should.

With Windows CE.NET is should work absolutly fine. Same as with an Windows
XP Client. After connectig to the TS open cmd.exe and use "change port
/query" to see if the ports are redirected.

Sorry for my English.

Oliver



"Legatus" <Legatus@discussions.microsoft.com> schrieb im Newsbeitrag
news:2C5C35C0-F5FF-46B0-9557-72726DE49BB7@microsoft.com...
>I am running a couple of 2k3-R2 servers as Terminal Servers .
> The majority of my users are connecting to the TS by means of WYSE S10 and
> WT1125SE, wyse ThinOS.
>
> On a couple of them I need a modem connected on the com port.
> The application running on the TS need to connect to the modem connected
> to
> the com port on the Wyse terminal client.
>
> I have com port redirection enabled on both of my TermServs. On the
> 1125SE's and S10(thin OS) I dont know the command to map the com port to
> the
> thin client. Can anyone help please!
>
> /Jim
>
>
> On the 3125(CE.NET) there is RDP settings to bring the com port to the
> local
> machine...but this doesnt work either.
>
>
>
> So in short. Is there anyone here that has had success in mapping com
> ports
> to thin clients that are non XPembedded driven? I can get this to work
> fine
> if using RDP sessions from an XP workstation or XPe thin client. However
> I
> dont want to have to replace all of my equipment if I can get it working
> on
> existing thin clients.

Legatus

Thanks for this..
Have checked the command and it looks OK.
The output looks like this:

AUX = \DosDevices\COM1
COM1 = \Device\RdpDrPort\;COM1:15\tsclient\COM1
COM2 = \Device\RdpDrPort\;COM2:15\tsclient\COM2
COM3 = \Device\RdpDrPort\;COM3:15\tsclient\COM3
LPT1 = \Device\RdpDrPort\;LPT1:15\tsclient\LPT1
PRN = \DosDevices\LPT1

But when I add a modem to com1 on the server nothing happens, no respons
from the modem on the terminal client?
Also test the "query" optiion from the modem properties on the server.
When I did this a didod on the modem "lights up, so I guess there are some
connection.
Grateful for all input on this.
PS
Have never tried this before so i'm an beginner whit this..




"Oliver Schröder" wrote:

> Jim,
>
> RDP com-port redirection should work fine with any thin-client supporting
> RDP 5.1 or higher.
> There is no "command" to redirect the ports, you just have to check the
> appropriate checkbox. If there is no such checkbox, the integrated
> RDP-client does not support com-port redirection. Maybe then there is a
> firmware-update for the thin-client. You have to ask the manufacturer.
>
> The problem with Linux-ThinClients is that their RDP-support is only 95 %
> Microsoft-conform. So often things do not work exactly as they should.
>
> With Windows CE.NET is should work absolutly fine. Same as with an Windows
> XP Client. After connectig to the TS open cmd.exe and use "change port
> /query" to see if the ports are redirected.
>
> Sorry for my English.
>
> Oliver
>
>
>
> "Legatus" <Legatus@discussions.microsoft.com> schrieb im Newsbeitrag
> news:2C5C35C0-F5FF-46B0-9557-72726DE49BB7@microsoft.com...
> >I am running a couple of 2k3-R2 servers as Terminal Servers .
> > The majority of my users are connecting to the TS by means of WYSE S10 and
> > WT1125SE, wyse ThinOS.
> >
> > On a couple of them I need a modem connected on the com port.
> > The application running on the TS need to connect to the modem connected
> > to
> > the com port on the Wyse terminal client.
> >
> > I have com port redirection enabled on both of my TermServs. On the
> > 1125SE's and S10(thin OS) I dont know the command to map the com port to
> > the
> > thin client. Can anyone help please!
> >
> > /Jim
> >
> >
> > On the 3125(CE.NET) there is RDP settings to bring the com port to the
> > local
> > machine...but this doesnt work either.
> >
> >
> >
> > So in short. Is there anyone here that has had success in mapping com
> > ports
> > to thin clients that are non XPembedded driven? I can get this to work
> > fine
> > if using RDP sessions from an XP workstation or XPe thin client. However
> > I
> > dont want to have to replace all of my equipment if I can get it working
> > on
> > existing thin clients.
>
>