I am testing my own TCP client/server software, trying to use an Azure VM for testing.
I have done this successfully on a Azure VM that I set up over a year ago. Now I have
created a new VM that I need to test with. My service is installed on the VM and is
monitoring port 18971. In the Azure portal, I have created an "endpoint" for TCP for
that port. The machine is running Windows 2012. I have configured Windows Firewall
with inbound and outbound rules to allow all TCP traffic to/from that port. I have
also tried turning the firewall off. Still, my client software does not work, I
receive error 10060 on the Winsock API "connect". I tried both the domain name and
the IP address.
Any ideas of what else I have to do to allow TCP traffic? I am pretty sure this is
an Azure configuration problem - I have successfully tested the software on direct
connected machines as well as the old Azure VM I mentioned (I see no difference
between it and the one I am trying now).
Jeffrey McKay