Dial failed: dial tcp 75.144.254.101:5555

[techroy23]

Hi I'm using windows server 2019 and it wont connect to the server. I already allowed the csminer to windows firewall and ran it as admin but still wont work.

Please see message log below

==== Status/Debug output follows ====
# 2020/11/23 14:21:11 INFO(csminer.go,110): Miner username: donate-getmonero-org
# 2020/11/23 14:21:11 INFO(csminer.go,111): Threads: 1
# 2020/11/23 14:21:11 INFO(minerlib.go,292): minerlib initialized
# 2020/11/23 14:21:11 INFO(minerlib.go,169): Pool login called
# 2020/11/23 14:21:32 ERROR(client.go,130): Dial failed: dial tcp 75.144.254.101:5555: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. client:cryptonote.social:5555
# 2020/11/23 14:21:32 ERROR(miner.go,75): Pool server not responding: dial tcp 75.144.254.101:5555: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
# 2020/11/23 14:21:32 INFO(miner.go,76): Sleeping for 3s seconds before trying again.
# 2020/11/23 14:21:35 INFO(minerlib.go,169): Pool login called
# 2020/11/23 14:21:56 ERROR(client.go,130): Dial failed: dial tcp 75.144.254.101:5555: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. client:cryptonote.social:5555
# 2020/11/23 14:21:56 ERROR(miner.go,75): Pool server not responding: dial tcp 75.144.254.101:5555: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
# 2020/11/23 14:21:56 INFO(miner.go,76): Sleeping for 4s seconds before trying again.

Tracert Log
C:\Users\Administrator>tracert -h 100 cryptonote.social

Tracing route to cryptonote.social [75.144.254.101]
over a maximum of 100 hops:

  1    51 ms    78 ms     1 ms  216.182.238.231
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    <1 ms    <1 ms    <1 ms  100.65.12.161
  8     1 ms     1 ms    <1 ms  52.93.29.89
  9    <1 ms     1 ms     1 ms  100.100.6.44
 10    32 ms    33 ms    43 ms  100.91.176.180
 11    33 ms    33 ms    33 ms  100.91.159.2
 12    32 ms    33 ms    32 ms  100.91.159.15
 13    33 ms    33 ms    33 ms  100.91.198.14
 14    33 ms    33 ms    32 ms  100.91.198.7
 15    33 ms    33 ms    35 ms  52.93.134.80
 16    32 ms    33 ms    32 ms  52.93.131.3
 17    32 ms    52 ms    32 ms  100.91.143.165
 18    33 ms    36 ms    33 ms  15.230.48.47
 19    32 ms    32 ms    32 ms  54.239.105.110
 20    33 ms    32 ms    33 ms  be-102-pe01.1950stemmons.tx.ibone.comcast.net [23.30.207.149]
 21    33 ms    35 ms    33 ms  be-12441-cr02.dallas.tx.ibone.comcast.net [68.86.89.205]
 22    49 ms    49 ms    47 ms  be-302-cr12.1601milehigh.co.ibone.comcast.net [96.110.38.101]
 23    47 ms    47 ms    47 ms  be-1312-cs03.1601milehigh.co.ibone.comcast.net [96.110.39.89]
 24    47 ms    47 ms    47 ms  be-1313-cr13.1601milehigh.co.ibone.comcast.net [96.110.39.106]
 25    47 ms    47 ms    47 ms  be-301-cr13.champa.co.ibone.comcast.net [96.110.36.193]
 26    47 ms    47 ms    47 ms  be-1413-cs04.champa.co.ibone.comcast.net [96.110.37.237]
 27    46 ms    47 ms    46 ms  be-1412-cr12.champa.co.ibone.comcast.net [96.110.37.222]
 28    69 ms    69 ms    69 ms  be-304-cr11.sunnyvale.ca.ibone.comcast.net [96.110.39.30]
 29    69 ms    69 ms    69 ms  be-1211-cs02.sunnyvale.ca.ibone.comcast.net [96.110.46.13]
 30    69 ms    75 ms    69 ms  96.110.41.70
 31    69 ms    69 ms    69 ms  be-299-rar01.santaclara.ca.sfba.comcast.net [68.86.143.94]
 32    69 ms    69 ms    69 ms  162.151.78.250
 33    69 ms    69 ms    69 ms  24.124.158.178
 34    77 ms    77 ms    77 ms  c-24-5-198-28.hsd1.ca.comcast.net [24.5.198.28]
 35    78 ms    76 ms   111 ms  75-144-254-101-SFBA.hfc.comcastbusiness.net [75.144.254.101]

Trace complete.

Nslookup Log
C:\Users\Administrator>nslookup cryptonote.social
Server:  ip-172-31-0-2.ec2.internal
Address:  172.31.0.2

Non-authoritative answer:
Name:    cryptonote.social
Address:  75.144.254.101

Ping
C:\Users\Administrator>ping cryptonote.social

Pinging cryptonote.social [75.144.254.101] with 32 bytes of data:
Reply from 75.144.254.101: bytes=32 time=81ms TTL=30
Reply from 75.144.254.101: bytes=32 time=83ms TTL=30
Reply from 75.144.254.101: bytes=32 time=78ms TTL=30
Reply from 75.144.254.101: bytes=32 time=83ms TTL=30

Ping statistics for 75.144.254.101:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 78ms, Maximum = 83ms, Average = 81ms

[cryptonote-social]

That's odd... are you able to mine with other software, e.g. xmrig? Are you able to reach the website https://cryptonote.social which is at the same IP?

[techroy23]

yes i can reach the website. xmrig also shows the same error. however if i use a different mining pool such as nanopool it works

[cryptonote-social]

Server: ip-172-31-0-2.ec2.internal

does ec2 imply you're going through an AWS host? The pool has some AWS addresses blocked.

[techroy23]

yes im using multiple ec2 aws for a farm cluster. i have also allowed all ports in the aws panel

[cryptonote-social]

OK that's likely the problem. We had blocked most AWS IP ranges because someone was mining with ~100K machines and overloading our server several months back. Are you using a narrow IP range? If so I can try unblocking that. Not sure if I want to lift all the AWS block rules though.

[techroy23]

i see. nope its fine ill will switch provider next week. i will close this issue now. thanks

[techroy23]

oh btw i got an alternative solution you dont need to open ip anymore i've just created a openvpn on my local server and route the traffic my aws farm to my own ip. it works well now. so the traffic now goes from [AWS SERVER] > [ALT LOCAL SERVER] > [CRYPTONOTE SERVER]

[cryptonote-social]

good deal! happy mining.