I might have not explained it correctly. I have been asked to Virtualize a Microsoft Server which runs an application Server Software called MICROS. MICROS is used as the back end for POS Systems. When MICROS gets a transaction, it can send that transaction out through TCP or Serial Port. There is another Server that is connected to the MICROS Server via null modem cable. Since we are virtualizing the MICROS Server on a Windows 2008 R2 Server, we can not get the Serial Port to pass through from the Virtual Host because Microsoft no longer supports passing through Serial Ports from the Virtual Host to the Virtual Session. I am looking to create a C# Application to take the place of communicating on both sides because the null modem cable can not be used. The Server that receives data and sends data back to the MICROS Server is an old outdated piece of software that I can't change right now because there is no newer version. It is a DOS Application. So, I am looking for a way to pass Serial to Serial through Named Pipes, Serial to TCP, or any other method. If the receiving Server was able to send and receive via TCP then this wouldn't be an issue. My client is pushing me to make it happen. Thanks! :)

I have a Software Program from a MICROS Server that can send via TCP or Serial Port. I have another application on another server that sends and receives data from the MICROS Server through a physical null modem cable on Serial port COM2. I am virtualizing the MICROS Server and that does away with the Serial Port communication. I can't change the Server that receives the data from a Serial Port. So, does anyone have a solution to send from the MICROS Server through TCP to the second server and be able to pass that down to COM2 and be able to have COM2 respond back through the TCP port back to the MICROS Server without having a physical cable? Any code support would be greatly appreciated.