Author

Topic: Socket connect failed: Connection refused Antminer A3 (SOLVED) (Read 461 times)

member
Activity: 231
Merit: 10
network problem is...
newbie
Activity: 4
Merit: 0

I've done all of them, but the problem still does not work
Try what I have done.I had the same problem.What I did to my Antminer X3 was first RESET {Diagnostic Page} to default and secondly change from originally STATIC to DYNAMIC connection..Click SAVE and now working well.Hope this info will helps.
newbie
Activity: 2
Merit: 0

I've done all of them, but the problem still does not work
newbie
Activity: 112
Merit: 0
I tried everything:

- Manually set the clock to 600MHz
- Set the fan speed at a fixed speed
- Changed the IP settings to static
- Changed the DNS Server
- Checked the firewall

The only thing I can consistently see is that the pool has an impact on the frequency of the problem.

I started using siamining when I got the machines and that worked great until about a week ago.
Both machines start getting the connection refused error, a problem I only saw with the D3's up until that moment.
A reboot would fix it for up to days sometimes but now it needs a reboot several times a day.

I stumbled upon the probable cause of the problem when I tried to move the horrible sia wallet to another machine, I didn't trust it anymore and just to be save I wanted to switch to nicehash or miningpoolhub and get paid in btc or whatever so I could just leave the wallet alone.

Switching to miningpoolhub gave me the connection refused problem all the time although the settings were correct.
Going to nicehash gave me exactly the same problem: not a single time was it able to connect.
When I switched back to siamining it ran again for a couple of hours on one machine and half a day on the other.
Even rebooting didn't always help.

So I tried another sia pool Luxor.Tech, this seemed to be working better for one of the machines but not at all for the other.

Now one of the machines is mining on luxor and the other one is mining on siamining.. let's see.

I think the problem is the connection to the pools.. I think a firmware update will be needed. Let's hope bitmain ran in to the same problems and will give us an update soon.

newbie
Activity: 1
Merit: 0

Manually setting the miner frequency to 600M fixed the problem for me.
Jump to: