Re: Ports and more

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@xxxxxxxxxxxxxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxxxxxxx> 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.

.

Relevant Pages

  • RE: Port Forwarding With 2 NIC Configuration
    ... Can SBS do 1-to-1 Natting? ... > and incoming/outgoing port, ... > automatically redirected from the SBS server to port 81 of the internal ... > Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Remote server management unavailable after installing latest hotfix
    ... other process listening on port 80. ... do you encountered any issue when accessing the SBS server from RWW ... Microsoft CSS Online Newsgroup Support ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: cant connect to TS after install sp1 on SBS
    ... Deploying Windows Server 2003 Terminal Server to Host User Desktops ... Microsoft ISA Server 2004 Documentation ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Microsoft SBS 2000 Internet Permissions Problem
    ... The web site logon page is access via HTTPS port 85: ... If Microsoft Internet Explorer is configured to reference a server that is ... ISA Server 2000 Standard Edition, ...
    (microsoft.public.windows.server.sbs)
  • Re: Terminal Server with SBS 2K3
    ... All of these problems only occur on the Terminal Server, there are others, ... > Microsoft CSS Online Newsgroup Support ... > |> policy and the local policy of the terminal server. ...
    (microsoft.public.windows.server.sbs)
Loading