(Msg. 1) Posted: Wed Mar 19, 2008 8:49 am Post subject: Ports and more Archived from groups: microsoft>public>windows>terminal_services (more info?)
I thank everyone for their help on this forum. Besides my LPT1: printing
issue, we also have a Serial Port issue. We have a program that monitors
Mocon units (burst testers) that should read the data from the testing unit
and store it into a SQL server database table. The main program is a VB6
app, which hopefully soon, will be converted for a .Net environment.
I am having the same issue with the Serial port. We test it on a standard
PC and it works fine. When we plug it into a thin client, nothing happens.
At least with my printing issue, I get a print error 482.
Could this be a user policy issue coming from the Terminal Server. I have
not yet looked at the TS event log yet. I will do that next.
Also, being new to Terminal Server and thin clients, does anyone have any
recommended books, sites, etc, that I can use for training?
(Msg. 2) Posted: Wed Mar 19, 2008 1:51 pm Post subject: Re: Ports and more [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Have you enabled COM port redirection on the server and the
clients?
Check here for more info:
_________________________________________________________
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?QnJhZA==?= <Brad RemoveThis @discussions.microsoft.com> wrote on 19
mar 2008 in microsoft.public.windows.terminal_services:
> I thank everyone for their help on this forum. Besides my LPT1:
> printing issue, we also have a Serial Port issue. We have a
> program that monitors Mocon units (burst testers) that should
> read the data from the testing unit and store it into a SQL
> server database table. The main program is a VB6 app, which
> hopefully soon, will be converted for a .Net environment.
>
> I am having the same issue with the Serial port. We test it on
> a standard PC and it works fine. When we plug it into a thin
> client, nothing happens. At least with my printing issue, I get
> a print error 482.
>
> Could this be a user policy issue coming from the Terminal
> Server. I have not yet looked at the TS event log yet. I will
> do that next.
>
> Also, being new to Terminal Server and thin clients, does anyone
> have any recommended books, sites, etc, that I can use for
> training?
>
> Thanks.
(Msg. 3) Posted: Tue Mar 25, 2008 5:44 am Post subject: Re: Ports and more [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Vera,
We looked at the server output by running the change port /query in the
command window and it does show that the ports are not being redirected. I
think it said something like COM1=\Device\Serial0.
But the KB solution (938645 - You cannot communicate with the local device
by using a redirected COM port in a Windows Server 2003-based terminal-server
session) does not provide much help.
This article states to resolve this problem immediately to contact Microsoft
Customer Support.
I guess I will have to do that unless you know of something else I can check
or do.
Thanks.
"Vera Noest [MVP]" wrote:
> Have you enabled COM port redirection on the server and the
> clients?
> Check here for more info:
>
> How can I verify that my local COM ports are redirected?
> http://ts.veranoest.net/ts_faq_client_resources.htm#verify_COM_port > s
>
> _________________________________________________________
> 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?QnJhZA==?= <Brad.TakeThisOut@discussions.microsoft.com> wrote on 19
> mar 2008 in microsoft.public.windows.terminal_services:
>
> > I thank everyone for their help on this forum. Besides my LPT1:
> > printing issue, we also have a Serial Port issue. We have a
> > program that monitors Mocon units (burst testers) that should
> > read the data from the testing unit and store it into a SQL
> > server database table. The main program is a VB6 app, which
> > hopefully soon, will be converted for a .Net environment.
> >
> > I am having the same issue with the Serial port. We test it on
> > a standard PC and it works fine. When we plug it into a thin
> > client, nothing happens. At least with my printing issue, I get
> > a print error 482.
> >
> > Could this be a user policy issue coming from the Terminal
> > Server. I have not yet looked at the TS event log yet. I will
> > do that next.
> >
> > Also, being new to Terminal Server and thin clients, does anyone
> > have any recommended books, sites, etc, that I can use for
> > training?
> >
> > Thanks.
>
(Msg. 4) Posted: Tue Mar 25, 2008 1:01 pm Post subject: Re: Ports and more [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
But have you made sure that COM port redirection is enabled?
By default, it is disabled.
Check on the server in Terminal Services Configuration - rdp-tcp
connection properties, and on the rdp client - local resources
KB938645 is about a situation where the COM port *is* succesfully
redirected, but the application cannot communicate with it.
That's not your situation.
_________________________________________________________
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?QnJhZA==?= <Brad RemoveThis @discussions.microsoft.com> wrote on 25
mar 2008 in microsoft.public.windows.terminal_services:
> Vera,
>
> We looked at the server output by running the change port
> /query in the command window and it does show that the ports are
> not being redirected. I think it said something like
> COM1=\Device\Serial0.
>
> But the KB solution (938645 - You cannot communicate with the
> local device by using a redirected COM port in a Windows Server
> 2003-based terminal-server session) does not provide much help.
>
> This article states to resolve this problem immediately to
> contact Microsoft Customer Support.
>
> I guess I will have to do that unless you know of something else
> I can check or do.
>
> Thanks.
>
> "Vera Noest [MVP]" wrote:
>
>> Have you enabled COM port redirection on the server and the
>> clients?
>> Check here for more info:
>>
>> How can I verify that my local COM ports are redirected?
>> http://ts.veranoest.net/ts_faq_client_resources.htm#verify_COM_p >> ort s
>>
>> _________________________________________________________
>> 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?QnJhZA==?= <Brad RemoveThis @discussions.microsoft.com> wrote on
>> 19 mar 2008 in microsoft.public.windows.terminal_services:
>>
>> > I thank everyone for their help on this forum. Besides my
>> > LPT1: printing issue, we also have a Serial Port issue. We
>> > have a program that monitors Mocon units (burst testers) that
>> > should read the data from the testing unit and store it into
>> > a SQL server database table. The main program is a VB6 app,
>> > which hopefully soon, will be converted for a .Net
>> > environment.
>> >
>> > I am having the same issue with the Serial port. We test it
>> > on a standard PC and it works fine. When we plug it into a
>> > thin client, nothing happens. At least with my printing
>> > issue, I get a print error 482.
>> >
>> > Could this be a user policy issue coming from the Terminal
>> > Server. I have not yet looked at the TS event log yet. I
>> > will do that next.
>> >
>> > Also, being new to Terminal Server and thin clients, does
>> > anyone have any recommended books, sites, etc, that I can use
>> > for training?
>> >
>> > Thanks.
(Msg. 5) Posted: Wed Mar 26, 2008 10:48 am Post subject: RE: Ports and more [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Vera,
I verified on the Terminal Server that the ports are enabled. Now, the thin
client's local resources did NOT have the port enabled. I did this and I am
now coming up with a VB error - "Runtime error 8012 - The Device Is Not open."
I still struggle with another error; a printer 482 error, which I tracked
down to be the printer information cannot be found. But I did verify that
the printer driver is installed on the server.
Oh, I do still need to look at the Event Log on the server.
"Brad" wrote:
> I thank everyone for their help on this forum. Besides my LPT1: printing
> issue, we also have a Serial Port issue. We have a program that monitors
> Mocon units (burst testers) that should read the data from the testing unit
> and store it into a SQL server database table. The main program is a VB6
> app, which hopefully soon, will be converted for a .Net environment.
>
> I am having the same issue with the Serial port. We test it on a standard
> PC and it works fine. When we plug it into a thin client, nothing happens.
> At least with my printing issue, I get a print error 482.
>
> Could this be a user policy issue coming from the Terminal Server. I have
> not yet looked at the TS event log yet. I will do that next.
>
> Also, being new to Terminal Server and thin clients, does anyone have any
> recommended books, sites, etc, that I can use for training?
>
> Thanks.
(Msg. 6) Posted: Wed Mar 26, 2008 12:27 pm Post subject: RE: Ports and more [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Seems that your application is suffering from the issue described
in KB 938645. I'd call Microsoft and get the hotfix.
About the printer: most likely, the printer driver is not TS
compatible. A lot of 3rd party printer drivers aren't. Which
printer model is this?
Have you tried to remap it to a native printer, using:
239088 - Windows 2000 or Windows Server 2003 Terminal Services
server logs events 1111, 1105, and 1106
http://support.microsoft.com/?kbid=239088
_________________________________________________________
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?QnJhZA==?= <Brad DeleteThis @discussions.microsoft.com> wrote on 26
mar 2008 in microsoft.public.windows.terminal_services:
> Vera,
>
> I verified on the Terminal Server that the ports are enabled.
> Now, the thin client's local resources did NOT have the port
> enabled. I did this and I am now coming up with a VB error -
> "Runtime error 8012 - The Device Is Not open."
>
> I still struggle with another error; a printer 482 error, which
> I tracked down to be the printer information cannot be found.
> But I did verify that the printer driver is installed on the
> server.
>
> Oh, I do still need to look at the Event Log on the server.
>
> "Brad" wrote:
>
>> I thank everyone for their help on this forum. Besides my
>> LPT1: printing issue, we also have a Serial Port issue. We
>> have a program that monitors Mocon units (burst testers) that
>> should read the data from the testing unit and store it into a
>> SQL server database table. The main program is a VB6 app,
>> which hopefully soon, will be converted for a .Net environment.
>>
>> I am having the same issue with the Serial port. We test it on
>> a standard PC and it works fine. When we plug it into a thin
>> client, nothing happens. At least with my printing issue, I get
>> a print error 482.
>>
>> Could this be a user policy issue coming from the Terminal
>> Server. I have not yet looked at the TS event log yet. I will
>> do that next.
>>
>> Also, being new to Terminal Server and thin clients, does
>> anyone have any recommended books, sites, etc, that I can use
>> for training?
>>
>> Thanks.
(Msg. 7) Posted: Wed Mar 26, 2008 12:36 pm Post subject: Re: Ports and more [Login to view extended thread Info.] Archived from groups: per prev. post (more info?)
Vera,
Also, just to let you know, we just opened a support ticket with Microsoft
so when I find something out from them, I will certainly post it so you know.
"Vera Noest [MVP]" wrote:
> But have you made sure that COM port redirection is enabled?
> By default, it is disabled.
> Check on the server in Terminal Services Configuration - rdp-tcp
> connection properties, and on the rdp client - local resources
>
> KB938645 is about a situation where the COM port *is* succesfully
> redirected, but the application cannot communicate with it.
> That's not your situation.
> _________________________________________________________
> 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?QnJhZA==?= <Brad.RemoveThis@discussions.microsoft.com> wrote on 25
> mar 2008 in microsoft.public.windows.terminal_services:
>
> > Vera,
> >
> > We looked at the server output by running the change port
> > /query in the command window and it does show that the ports are
> > not being redirected. I think it said something like
> > COM1=\Device\Serial0.
> >
> > But the KB solution (938645 - You cannot communicate with the
> > local device by using a redirected COM port in a Windows Server
> > 2003-based terminal-server session) does not provide much help.
> >
> > This article states to resolve this problem immediately to
> > contact Microsoft Customer Support.
> >
> > I guess I will have to do that unless you know of something else
> > I can check or do.
> >
> > Thanks.
> >
> > "Vera Noest [MVP]" wrote:
> >
> >> Have you enabled COM port redirection on the server and the
> >> clients?
> >> Check here for more info:
> >>
> >> How can I verify that my local COM ports are redirected?
> >> http://ts.veranoest.net/ts_faq_client_resources.htm#verify_COM_p > >> ort s
> >>
> >> _________________________________________________________
> >> 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?QnJhZA==?= <Brad.RemoveThis@discussions.microsoft.com> wrote on
> >> 19 mar 2008 in microsoft.public.windows.terminal_services:
> >>
> >> > I thank everyone for their help on this forum. Besides my
> >> > LPT1: printing issue, we also have a Serial Port issue. We
> >> > have a program that monitors Mocon units (burst testers) that
> >> > should read the data from the testing unit and store it into
> >> > a SQL server database table. The main program is a VB6 app,
> >> > which hopefully soon, will be converted for a .Net
> >> > environment.
> >> >
> >> > I am having the same issue with the Serial port. We test it
> >> > on a standard PC and it works fine. When we plug it into a
> >> > thin client, nothing happens. At least with my printing
> >> > issue, I get a print error 482.
> >> >
> >> > Could this be a user policy issue coming from the Terminal
> >> > Server. I have not yet looked at the TS event log yet. I
> >> > will do that next.
> >> >
> >> > Also, being new to Terminal Server and thin clients, does
> >> > anyone have any recommended books, sites, etc, that I can use
> >> > for training?
> >> >
> >> > Thanks.
>
All times are: Eastern Time (US & Canada) (change)
Page 1 of 1
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
