EasyTCP Socket 103 error

I am hoping someone can can give me some clues about what might be going on with one of my customers… thanks in advance.

I have a Service app and a Desktop app that communicate via an EasyTCP socket… which all works very well at hundreds of installs. But I have one customer where shortly after the sockets are sucessfully connected the Desktop app starts getting 103 (NameResolution) errors when trying to communicate with the Service.

It seems that the Service socket is still connected… netstat lists its connection as “Established”.

If we restart the Service the problem goes away, we are able to connect the 2 apps but only briefly.

One complication is that this customer is running the Desktop on a Mac and the Service is running under a Linux instance on Azure…

Thanks again,