1. Check remote PC Windows firewall. It might blocks Radmin. 2. Install Radmin Viewer on that PC with Radmin Server and try to connect to 127.0.0.1. And try to connect using that PC`s local IP and write if these both connections were successful or not.
Thank you for your advice:) I checked the firewall and found it was closed. Then I installed the Radmin Viewer on my remote PC and connected to both 127.0.0.1 and the PC's local IP, the socket error didn't appear.
This socket error doesn't always happen every time I make the connection, probably once every 20 - 30 times. And when I try this on my remote PC, it doesn't happen at all. I have tried more than fifty times.
I found that Radmin will not close the connection immediately after the connection is closed.There are many connections in the remote server with time-wait status. Are these related?
1. Check remote PC Windows firewall. It might blocks Radmin.
2. Install Radmin Viewer on that PC with Radmin Server and try to connect to 127.0.0.1. And try to connect using that PC`s local IP and write if these both connections were successful or not.
I checked the firewall and found it was closed.
Then I installed the Radmin Viewer on my remote PC and connected to both 127.0.0.1 and the PC's local IP, the socket error didn't appear.
This socket error doesn't always happen every time I make the connection, probably once every 20 - 30 times.
And when I try this on my remote PC, it doesn't happen at all. I have tried more than fifty times.
I found that Radmin will not close the connection immediately after the connection is closed.There are many connections in the remote server with time-wait status. Are these related?
It`s a feature of this protocol.