Re: Using Terminal Server 2003 and Port Redirection
- From: jamie gee <jamiegee@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 25 Nov 2005 09:58:03 -0800
Hi Jeff
Thanks for your help so far...
I have looked around your web site, the internet (in general), and so
forth....
I appreciate your reply about locking down the deskop and forcing launch of
RDP APP.
However, my other question is more imporant at this time as it is needed to
implicate the step you outlined above. That would be:
com port redirection over TS 2003. Is it fully supported? We use label
printers and hand scanners. The scanners for example are mostly used to
traffic data to the application From the port, whilst the label printers are
used to receive data.
My understanding is that there has been some less than 100% com port
compatibility for TS. this is where printers and more simple devices are
supported. For fuller com port rredirection applications like CITRIX would be
used.
What is in your understanding of the state of affairs as per MICROSOFT TS
2003 and its support for ALL COM PORT redirections ? Is there a list of
problemsand or known issues with COM PORT REDIRECTION that i could look over
? or is it supposed to be 100%?
Thanks
JAMIE
"Jeff Pitsch" wrote:
> Using Group Policy you can lock down desktops about as far as you want. you
> can also force machines to autologon by registry setting and kick off a app
> on start-up.
>
> Jeff Pitsch
> http://www.sbcgatekeeper.com
> Your Terminal Services Security Website
>
> "jamie gee" <jamiegee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:09515967-5977-4533-901F-CB5CDA75D8F4@xxxxxxxxxxxxxxxx
> > Thanks for your help. Simply checking the remoe ports option in the RDC
> > client was the trick!
> >
> > After discussing with some associates here, it seems they have already
> > been
> > down this path. They have concluded by their researcht hat the TS serial
> > port
> > redirection is only supported for Printers.
> > What is MSFT official stance on serial port redirection for non-printers?
> >
> > Lastly, lets say that we are able to get the serial ports to be supported
> > and function properly...
> >
> > Is there a way from WINXP PRO to have users upon reboot of theirmachine to
> > have the TS server login appear and the desktop of their true PC
> > unavailable
> > by conventional means?
> >
> > Thanks
> >
> > JAMIE
> > "Jeff Pitsch" wrote:
> >
> >> Oh and make sure to put the change port command in a login script or
> >> something so that the user doesn't have to manually run the command.
> >>
> >> Jeff Pitsch
> >> http://www.sbcgatekeeper.com
> >> Your Terminal Services Security Website
> >>
> >> "jamie gee" <jamiegee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> news:6F65F481-F597-4C8E-A92B-747C4A9A6D75@xxxxxxxxxxxxxxxx
> >> > Thanks Jeff
> >> >
> >> > However I am at a bit of a loss as to how to proceed...
> >> >
> >> > When i connect to the TS, it does not seem to see my ports on the local
> >> > pc.
> >> > How do I get them to be seen, then map them? (ie via Change port
> >> > /query)
> >> >
> >> > Please advise as what i need to do to map my port(s) successfully, as
> >> > in
> >> > where to locate the original port number (is this my local port or the
> >> > TS
> >> > port) and what port number to map it to (when I map it wil it be
> >> > visiibme
> >> > to
> >> > all sessions or just when this user is logged in?
> >> >
> >> > A baby document to guid em ewould be good. The MS article you gave
> >> > says
> >> > Syntax
> >> > change port[{PortX=PortY | /dPortX | /query}]
> >> >
> >> > Parameters
> >> > PortX = PortY
> >> >
> >> > Maps COM PortX to PortY.
> >> >
> >> > I am not sure where to get original port number (is this the local port
> >> > number) and what number to give it(can I make up a number), and to make
> >> > sure
> >> > this port is redirected back to the lcoal machine
> >> >
> >> > WOuld I simply be able to map port 1 to port 1? by MAP
> >> >
> >> > Thanks
> >> >
> >> > JAMIE
> >> >
> >> >
> >> >
> >> > "Jeff Pitsch" wrote:
> >> >
> >> >> You were almost there. Use the change port command:
> >> >> http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/ServerHelp/1db49727-f587-424d-8d98-bb51630d13a0.mspx
> >> >>
> >> >> Jeff Pitsch
> >> >> http://www.sbcgatekeeper.com
> >> >> Your Terminal Services Security Website
> >> >>
> >> >>
> >> >> "jamie gee" <jamie gee@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> >> >> news:24721222-1B57-4565-B315-531B0969F816@xxxxxxxxxxxxxxxx
> >> >> > Hello Jeff
> >> >> >
> >> >> > I am new to the game, so it may not be astupid question
> >> >> >
> >> >> > How would I know if it is mapped? If it needs to be mapped, what
> >> >> > would
> >> >> > be
> >> >> > the way you would recommend to do it? I am sure it is without saying
> >> >> > that
> >> >> > this is to be done on TS, so different users will need to have their
> >> >> > serial
> >> >> > pots mapped sepeerately so they may all connecct and use their ports
> >> >> > independantly.
> >> >> >
> >> >> > thanks
> >> >> > JAMIE
> >> >> >
> >> >> > "JAMIE GEE MCP" wrote:
> >> >> >
> >> >> >> Hello
> >> >> >> I have read through and tried several of the outlined tips
> >> >> >> regarding
> >> >> >> getting
> >> >> >> the 'automatic' functions of Terminal server 2003 to work properly.
> >> >> >>
> >> >> >> SETUP:
> >> >> >> (All Local)
> >> >> >> Server TS 2003 on Server Standard 2003
> >> >> >> All clients are XP PRO P4, etc
> >> >> >>
> >> >> >>
> >> >> >> Firstly, we are using propreitary software that uses COM (Serial)
> >> >> >> port
> >> >> >> devices like the following:
> >> >> >> -Opticon barcode Scanners
> >> >> >> -bar code printers ( Zebra / others)
> >> >> >>
> >> >> >> It is my understanding that versions of TS PRIOR to 2000 supported
> >> >> >> com
> >> >> >> port
> >> >> >> redirection (back to the client) ONLY for printers.
> >> >> >>
> >> >> >> It is also my understanding that now All serial traffic can be sent
> >> >> >> back
> >> >> >> to
> >> >> >> client ports seamlessly
> >> >> >>
> >> >> >> Backround: We have implemented CITRIX presentation server to allow
> >> >> >> TS
> >> >> >> on
> >> >> >> this same TS machine to redirect the ports on its own. However, my
> >> >> >> understanding is that this is overkill, as TS will do this properly
> >> >> >> on
> >> >> >> its
> >> >> >> own. The Citrix works fine, however
> >> >> >>
> >> >> >> I have looked into the following:
> >> >> >>
> >> >> >> While logged into TS via RDP client:
> >> >> >>
> >> >> >> Version RDP:
> >> >> >> 5.1.2600.2180
> >> >> >> Go to Printer Properties (from within RDP session to server:
> >> >> >>
> >> >> >> I see TS001 PRN001 TS002 Prn002 naming the pc that I am connecting
> >> >> >> from
> >> >> >>
> >> >> >> In RDP -TCP properties: Com port mapping is unchecked
> >> >> >> In GPEDIT on TS Do not allow com port redirection is not configured
> >> >> >>
> >> >> >> in DOS at Change port /query all I get returned is:
> >> >> >> AUX = \DosDevices\COM1
> >> >> >>
> >> >> >> Any tips or suggestions or so forth?
> >> >> >>
> >> >> >> Thanks
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >>
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>
.
- Follow-Ups:
- Re: Using Terminal Server 2003 and Port Redirection
- From: mag_pi
- Re: Using Terminal Server 2003 and Port Redirection
- References:
- RE: Using Terminal Server 2003 and Port Redirection
- From: jamie gee
- Re: Using Terminal Server 2003 and Port Redirection
- From: Jeff Pitsch
- Re: Using Terminal Server 2003 and Port Redirection
- From: jamie gee
- Re: Using Terminal Server 2003 and Port Redirection
- From: Jeff Pitsch
- Re: Using Terminal Server 2003 and Port Redirection
- From: jamie gee
- Re: Using Terminal Server 2003 and Port Redirection
- From: Jeff Pitsch
- RE: Using Terminal Server 2003 and Port Redirection
- Prev by Date: TS 2003 Per Device CAL
- Next by Date: Re: Desperate for help - sorry!!
- Previous by thread: Re: Using Terminal Server 2003 and Port Redirection
- Next by thread: Re: Using Terminal Server 2003 and Port Redirection
- Index(es):
Relevant Pages
|
