03-10-2020 05:26 AM
Hi there,
I've used built in example (Simple TCP server and client) with a Windows based computer and a CentOS based computer trying to implement TCP communication. In my case, it worked when I used Windows as client and CentOS as server. However, error 56 appeared if I used Windows as server and CentOS as client. Did anybody also get into this situation?
p.s. I've turn off the firewall of both computers and they can ping to each other.
03-10-2020 06:13 AM
check if the necessary ports are open at both sides. Another thing to keep in mind is that LabVIEW uses Big-Endian format whereas most of the other software uses Little-Endian. So you have to rearrange the bytes at LabVIEW side, this can be easily done though options available in flatten to /unflatten from string node in LabVIEW.
03-10-2020 09:58 AM
@djac91 wrote:
check if the necessary ports are open at both sides. Another thing to keep in mind is that LabVIEW uses Big-Endian format whereas most of the other software uses Little-Endian. So you have to rearrange the bytes at LabVIEW side, this can be easily done though options available in flatten to /unflatten from string node in LabVIEW.
When communicating LabVIEW to LabVIEW there is no need to worry about the byte ordering even when on two different OSs such as Linux and Windows. This does become an issue when communicating between servers/clients written in other languages.
As for the OP, what port are you using for your server? Are you sure it is available for use? Have you checked the settings in your virus scanner? LabVIEW itself has no issues communicating between platforms. Where are you getting your timeout error? Is it on the open, write or read?
03-10-2020 08:56 PM
Thanks for reply!
I found that the connection has been established and the data from server(Windows) has been transmitted to the client(CentOS).
However, client closed the connection so that server couldn't read the return value.
Perhaps there are some issue with my CentOS?
The attached file shows the port I used and error message I got.
Thanks again : )