Re: COM port redirection issue

Bump.  Anyone?

-----Original Message-----
From: Lars Oberg [mailto:[email protected]] 
Sent: Friday, November 04, 2011 8:54 AM
To: 'Peter Åstrand'; 'Chris Weiss'
Cc: [email protected]
Subject: Re: [rdesktop-users] COM port redirection issue

I am trying to decide whether to use Windows or Linux for a large number of
point-of-sale stations, and it would be great if you could give some more
details on the COM port redirection instabilities (or other issues).  

All the POS stations will do is basically RDP to a Windows 2008R2 terminal
server and the only redirection is of one COM port to a pole-display.  This
is one-way communication from the server to the POS stations.  I did some
basic testing as a proof-of-concept, and it appears to work fine, but I
don't want to find out after deploying the Linux solution that the COM port
redirection is not reliable in production.

Any information on this would be greatly appreciated!

Thanks,
Lars

Ps. I plan to use either CentOS or Ubuntu if I go the Linux route.

-----Original Message-----
From: Peter Åstrand [mailto:[email protected]] 
Sent: Friday, October 28, 2011 12:03 AM
To: Chris Weiss
Cc: [email protected]
Subject: Re: [rdesktop-users] COM port redirection issue


> I've got 2 ubuntu 10.04 ltsp based thin clients setup connecting to 
> the same 2003 terminal server with com port redirection.  The first 
> one I setup works fine, but the 2nd is having some issues.
>
> First is using "-r comport:COM2=/dev/ttyS1", 2nd is using "-r 
> comport:COM4=/dev/ttyS1"
> The main symptom is that the when the application using the com port 
> on the 2nd tries to close the port, the entire RDP session hangs for 
> about 20 seconds.  Occasionally opening the port again will fail, and 
> merely disconnecting and reconnecting the rdp session will allow it 
> again.
>
> is there some way to get rdesktop to complain about what's going on, 
> maybe log to a file, so i can pinpoint what to fix?

The rdesktop serial redirection is not very stable, this is a known problem.
If you want to debug the code, you need to define WITH_DEBUG_SERIAL during
build.

You could dig in the SF tracker and see if you find any relevant patches or
bug report. I did a quick search but only found this one:

https://sourceforge.net/tracker/index.php?func=detail&aid=1518140&group_id=2
4366&atid=381349

Btw, you are using rdesktop 1.7.0, right?

Rgds,
---
Peter Åstrand		ThinLinc Chief Developer
Cendio AB		http://www.cendio.com
Wallenbergs gata 4
583 30 Linköping	Phone: +46-13-21 46 00


__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6581 (20111027) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com

 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6581 (20111027) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
  

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6583 (20111028) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
  

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6601 (20111104) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6601 (20111104) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 


----------------------------------------------------------------------------
--
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
rdesktop-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/rdesktop-users

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6601 (20111104) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6601 (20111104) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
  

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6606 (20111106) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 
 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 6606 (20111106) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com
 


------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1