ADONTEC Serial Communication (rs232 CommServer, Comm-Server, PortServer, RS-232, RS-485, gateway TCP/IP COMM Tools, ZMODEM, 3964, 3964R rk512, LSV/2,delphi builder Visual basic C++), Free of charge software supplement,Serial to TCP/IP Converter, s5, interface serial devices to tcp/ip,Serial to TCP/IP GateWay, Seriell zu TCP/IP Gateway Konverter

Install the COMM-Server on the PC where the serial devices are connected to. Connect to the COMM-Server with any TCP/IP client from your remote office and read, write data from and to the serial devices.

The COMM-Server PC can be located anywhere as long it's connected to a TCP/IP network.

The COMM-Server applications exists for Visual Basic 6 and C# incl. source code! Customization or porting it to C++, Delphi or other programming environment is easy ! A realy simple but yet powerfull application. No tons of code lines as one might expect but a realy lean application thanks to the portable SuperCom API.

Redirect serial data to TCP/IP.
Redirect or distribute TCP data to serial ports.
Easily access remote serial ports through TCP/IP networks (internet or intranet).
Access serial devices easily through TCP/IP.
Access remote printer, modem, barcode reader, PLC and other hardware connected to a remote serial comm port (e.g. COM1, COM2) through TCP/IP.
Access a PLC (e.g. S5) connected to a serial port over the intranet or internet.
Pure software based solution.
On the COMM-Server side, use the standard COM1, COM2 and/or any other installed multi serial card.
The Client can be any TCP/IP aware software that connects to the COMM-Server.
Data is routed between server and clients transparently.
Up to 254 clients can be connected simultaneously to the COMM-Server and gain access to the remote serial devices.

Q & A

Does this mean that I can drop RDP ?

Using the SuperCom Suite one can develop simple client/server application and Gateways in order to read data from remote serial ports as fast as if it is local.

Is it possible to route data from a machine connected to a PC COM1 port to a Windows 2008 server?

Yes. At one side you collect serial data using SuperCom and using the same SuperCom functions your application is handing over the data to the TCP side.

RDP is very slow. How is it with SuperCom?

Routing data from a remote serial connection to a local PC using SuperCom Suite functions is usually as fast as if it were local. The TCP network is a candidate that could add a small delay but that is not really a size. Usually the serial data communication is the slow medium. So using SuperCom to accomplish this is definitely an upgrade compared to RDP.

Can I use UDP for that?

SuperCom doesn't UDP. UDP is not as safe as TCP is, even if you add checksums etc. UDP is not suitable for a data streams. You are going a major risk to get garbaged data on receiver side.

The other issue is to have a stable link and the data transfered from serial and TCP synchronized. That is the job of a software like SuperCom. If the software failes here the link will cause delays and timeouts.

Is it possible to use a ready-made client to connect to the COMM Server created with SuperCom?

Of course. The COMM Server finaly behave as a TCP server. Once the client connected it can read, write data to and from the serial ports. And in case the client requires any special functionality (e.g. authentication) you have the source code to customized it as you require.