After working for some days, again with untouched and same configurations, the T-rex mining software stopped on the rig using shared LTE Internet with an error "no connection" on eth.2miners.com:2020 causing by failed to ethproxy-subscribe .... can not parse Json. However, the source rig with LTE Internet is still working without problems, firewalls are all disabled.
I have also tested the TCP connection as well as UDP connection with nmap software from nmap.org and they are successfully discovered well, specially the one related to 2020 port

Thanks

Many thanks for letting me know about TCP which is used by mining software. After doing the test command for TCP connection in Windows 10, which returned true, it started to work again via the cable... really strange to me but it works now.

Thanks again for your comment

Dear T-rex developer,

I hope everything goes well on your side. Recently, I have tried to migrate to one of the mining software recommended by 2miners website (i.e., gminer and t-rex). However, I have face difficulties in making them start to mine through a cable based or wireless based network. I am not sure what strategies or algorithms are behind the software for communicating with the mining pools, but the issue is still there on my side.
For your information, I have been successful in using an LTE USB dongle in using the t-rex 0.19.4 by the time being, but not tried it yet in gminer. The Claymore has also the same issue and is working using an LTE USB dongle, as a couple of days ago it faced the errors of time out or no connection through ADSL router cable or the shared Internet of working LTE USB dongle shared through a switch.
In other words, recently all of the the sofwares in my side have faced an strange issue.
Additionally, the Internet network can easily ping the eth.2miners.com without any problems on all rigs using cable, wireless or LTE USB dongle.
As I am not aware of the inside of the mining program, so I can not find out why the no connection or time out messages can be issued even if the ping replies are OK.

I would appreciated it if you may kindly comment on this issue.

Thanks for your attention in this regards.

Dear GMiner developer,

I hope everything goes well on your side. Recently, I have tried to migrate to one of the mining software recommended by 2miners website (i.e., gminer and t-rex). However, I have faced difficulties in making them start to mine through a cable based or wireless based network. I am not sure what strategies or algorithms are behind the software for communicating with the mining pools, but the issue is still there on my side.
For your information, I have been successful in using an LTE USB dongle in using the t-rex 0.19.4 by the time being, but not tried it yet in gminer. The Claymore has also the same issue and is working using an LTE USB dongle, as a couple of days ago it faced the errors of time out or no connection through ADSL router cable or the shared Internet of working LTE USB dongle shared through a switch.
In other words, recently all of the the softwares in my side have faced an strange issue.
Additionally, the Internet network can easily ping the eth.2miners.com without any problems on all rigs using cable, wireless or LTE USB dongle.
As I am not aware of the inside of the mining program, so I can not find out why the no connection or time out messages can be issued even if the ping replies are OK.

FYI: For one time, I tried other pool namely ethereum.org and there were no issues in that pool. I have also contacted the 2miners.com admin and they confirmed that there are no issues on their side.

I would appreciated it if you may kindly comment on this issue.

Thanks for your attention in this regards.

Hi,

I have used one internet connection on one system shared by Windows 10 and a switch between the other computer systems (all use Windows 10 and now Trex 0.19.4 cuda 11.10). I have no problem with the pool connection in the source system (which shared the Internet connection) and it works well and find shares. However, I get connection time out on the other ones starting from today, after the DAG sizes are set and MH/s are also visible (with all firewalls off) and working some minutes (e.g., 3 min), and hence they do not find any shares.  This process is repeated with no success such a loop.

FYI: Every thing about connection with pool was OK the previous days on Ethash algo with Claymore 15
The ping of the pool is also OK in all Windows 10 systems. I am not sure what the problem will be  

Thanks