Terminal Services client serial port redirection server 2003

[mackman]

TS application cannot connect to redirected serially attached capture device.

Works if logged on w/ adminstrator rights, doesnt work if logged on as a
regular user (Remote Desktop User / Terminal Services User)

I have several customers on Terminal Servers using RDP to access. Some
clients have a serial port signature capture device. I check to have serial
ports redirected in the RDP sessions. At one of my customers, the application
running on the terminal server is able to connect to the capture device only
if the logged in user has administrator rights. I have set all of my domain
and domain controller local security policies, and various related folder
security policies the same as I have at other customer sites that work.

Any suggestions??
--
Attempting to succumb to Vista

 

[Oliver Schröder]

Re: Terminal Services client serial port redirection server 2003

Hi,

it should work fine.
Check with "change port / query" if the ports are redirected.

Regards

Oliver


"mackman" <mackman@discussions.microsoft.com> schrieb im Newsbeitrag
news:37D7B945-C42D-4931-931C-FE04319AB0EA@microsoft.com...
> TS application cannot connect to redirected serially attached capture
> device.
>
> Works if logged on w/ adminstrator rights, doesnt work if logged on as a
> regular user (Remote Desktop User / Terminal Services User)
>
> I have several customers on Terminal Servers using RDP to access. Some
> clients have a serial port signature capture device. I check to have
> serial
> ports redirected in the RDP sessions. At one of my customers, the
> application
> running on the terminal server is able to connect to the capture device
> only
> if the logged in user has administrator rights. I have set all of my
> domain
> and domain controller local security policies, and various related folder
> security policies the same as I have at other customer sites that work.
>
> Any suggestions??
> --
> Attempting to succumb to Vista

 

[mackman]

Re: Terminal Services client serial port redirection server 2003

Thanks for responding, sorry for my delay. As I stated, it does not work.
Please re-read my original explanation.

Also, I do not understand what/how to check with "change port / query"
--
Attempting to succumb to Vista


"Oliver Schröder" wrote:

> Hi,
>
> it should work fine.
> Check with "change port / query" if the ports are redirected.
>
> Regards
>
> Oliver
>
>
> "mackman" <mackman@discussions.microsoft.com> schrieb im Newsbeitrag
> news:37D7B945-C42D-4931-931C-FE04319AB0EA@microsoft.com...
> > TS application cannot connect to redirected serially attached capture
> > device.
> >
> > Works if logged on w/ adminstrator rights, doesnt work if logged on as a
> > regular user (Remote Desktop User / Terminal Services User)
> >
> > I have several customers on Terminal Servers using RDP to access. Some
> > clients have a serial port signature capture device. I check to have
> > serial
> > ports redirected in the RDP sessions. At one of my customers, the
> > application
> > running on the terminal server is able to connect to the capture device
> > only
> > if the logged in user has administrator rights. I have set all of my
> > domain
> > and domain controller local security policies, and various related folder
> > security policies the same as I have at other customer sites that work.
> >
> > Any suggestions??
> > --
> > Attempting to succumb to Vista
>
>

 

[Vera Noest [MVP]]

Re: Terminal Services client serial port redirection server 2003

Check if this helps:

How can I verify that my local COM ports are redirected?
http://ts.veranoest.net/ts_faq_client_resources.htm#verify_COM_ports

_________________________________________________________
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?bWFja21hbg==?= <mackman@discussions.microsoft.com> wrote
on 11 jun 2008 in microsoft.public.windows.terminal_services:

> Thanks for responding, sorry for my delay. As I stated, it does
> not work. Please re-read my original explanation.
>
> Also, I do not understand what/how to check with "change port /
> query"