Can't connect to COM1

[Guest Bob]

Hi,

 

I've an application that uses the COM1 port on Windows Server 2003. The

application connects fine to COM1 when I'm using the console, but when I TS

in, it can not connect. Is there something about TS that prevents the user

from accessing the COM1 port?

 

p.s. I used remote desktop connecting to the console ID-0 and not connecting

to the console ID-x, but it fails either way.

 

Thanks!

 

 

---

Bob

[Guest Jeff Pitsch]

Re: Can't connect to COM1

 

have you mapped the com1 port into the session? change port command

 

Jeff Pitsch

Microsoft MVP - Terminal Server

Citrix Technology Professional

Provision Networks VIP

 

Forums not enough?

Get support from the experts at your business

http://jeffpitschconsulting.com

 

Bob wrote:

> Hi,

>

> I've an application that uses the COM1 port on Windows Server 2003. The

> application connects fine to COM1 when I'm using the console, but when I TS

> in, it can not connect. Is there something about TS that prevents the user

> from accessing the COM1 port?

>

> p.s. I used remote desktop connecting to the console ID-0 and not connecting

> to the console ID-x, but it fails either way.

>

> Thanks!

>

>

> ---

> Bob

>

>

[Guest Bob]

Re: Can't connect to COM1

 

Hi Jeff,

 

Running "change port" on the remote session, the following displays:

 

AUX = \DosDevices\COM1

COM1 = \Device\Serial0

 

I'm not sure what I should do from here.

 

I can see in TS Manager that my session name presently is: RDP-Tcp#16

And RDP is running through port 3389

 

I suppose a command like "change port 1=16" or maybe "change port 1=3389"

is what you are suggesting?

 

And then use "change port /d 1" before I log off?

 

Thanks!

 

Bob.

[Guest Ken Zhao [MSFT]]

Re: Can't connect to COM1

 

Thanks Jeff.

 

Thanks & Regards,

 

Ken Zhao

 

Microsoft Online Support

Microsoft Global Technical Support Center

 

Get Secure! - http://www.microsoft.com/security <http://www.microsoft.com/security>

====================================================

When responding to posts, please "Reply to Group" via your newsreader so

that others may learn and benefit from your issue.

====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

 

 

 

 

--------------------

| Date: Wed, 29 Aug 2007 13:06:17 -0400

| From: Jeff Pitsch <Jeff@Jeffpitschconsulting.com>

| User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)

| MIME-Version: 1.0

| Subject: Re: Can't connect to COM1

| References: <eCBdBBl6HHA.5012@TK2MSFTNGP02.phx.gbl>

| In-Reply-To: <eCBdBBl6HHA.5012@TK2MSFTNGP02.phx.gbl>

| Content-Type: text/plain; charset=ISO-8859-1; format=flowed

| Content-Transfer-Encoding: 7bit

| Message-ID: <e1yzr7l6HHA.5796@TK2MSFTNGP05.phx.gbl>

| Newsgroups: microsoft.public.windows.terminal_services

| NNTP-Posting-Host: 71-82-91-103.dhcp.aldl.mi.charter.com 71.82.91.103

| Lines: 1

| Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP05.phx.gbl

| Xref: TK2MSFTNGHUB02.phx.gbl

microsoft.public.windows.terminal_services:10353

| X-Tomcat-NG: microsoft.public.windows.terminal_services

|

| have you mapped the com1 port into the session? change port command

|

| Jeff Pitsch

| Microsoft MVP - Terminal Server

| Citrix Technology Professional

| Provision Networks VIP

|

| Forums not enough?

| Get support from the experts at your business

| http://jeffpitschconsulting.com

|

| Bob wrote:

| > Hi,

| >

| > I've an application that uses the COM1 port on Windows Server 2003.

The

| > application connects fine to COM1 when I'm using the console, but when

I TS

| > in, it can not connect. Is there something about TS that prevents the

user

| > from accessing the COM1 port?

| >

| > p.s. I used remote desktop connecting to the console ID-0 and not

connecting

| > to the console ID-x, but it fails either way.

| >

| > Thanks!

| >

| >

| > ---

| > Bob

| >

| >

|

[Guest Jeff Pitsch]

Re: Can't connect to COM1

 

You use the commadn to map the virtual com port to the physical.

 

 

 

Bob wrote:

> Hi Jeff,

>

> Running "change port" on the remote session, the following displays:

>

> AUX = \DosDevices\COM1

> COM1 = \Device\Serial0

>

> I'm not sure what I should do from here.

>

> I can see in TS Manager that my session name presently is: RDP-Tcp#16

> And RDP is running through port 3389

>

> I suppose a command like "change port 1=16" or maybe "change port 1=3389"

> is what you are suggesting?

>

> And then use "change port /d 1" before I log off?

>

> Thanks!

>

> Bob.

>

>

[Guest Bob]

Re: Can't connect to COM1

 

It is now fixed.

 

Although I mistaken thought that COM1 was available locally, it turned out

the port was fried in the last electrical storm.

 

I installed a DB9-male to USB adapter to bypass COM1 and now I can use TS to

access the PBX phone system remotely.

 

Thanks for all your help!

 

Bob.