We’re having a very strange connectivity issue with our server/client at two customer sites.
The problem is that the client will not connect to the server at all, it’s as if the server wasn’t running. I did some diagnosis onsite at one of the customers and discovered some very strange behaviour.
It turns out that the client won’t even connect to the server when running on the same physical machine. Whether I specify the server by name or by IP address, it still won’t connect. The only thing that works is if I use the loopback address 127.0.0.1. Obviously this only works if the client is on the same machine as the server but it’s the only scenario in which it connects.
Has anyone seen anything like this before? I can find nothing wrong with the general networking configuration of the server. It’s fully “pingable” from anywhere on the network via both its name and IP address, but the client software just won’t connect.
We’re using the SynapseSuperTCPServer channel if that matters. Is it possible there’s some issue with this that’s causing the problem? I’m at a loss where to begin trying to diagnose this issue.