Socket was closed remotely (by pool)

[Visitante]

Hello, I know this topic may look redundant but it isn't.

I've tried all the solutions people have posted at their threads but I can't solve mine.

I've tried using nanopool, ethermine, ethpool with all their servers and I'm getting the same error.

http://i63.tinypic.com/1zd5flk.jpg

My SW:
Windows 10 Pro x64 v.1703
Claymore's dual miner
AMD's latest Crimsom ReLive Blockchain Driver
MSI Afterburner 4.4

My HW:
MB: BTC250 Pro
CPU: Intel Core I3 - 7100 3.90 GHz
GPU: AMD RX 570 Gaming
RAM: 8GB DDR4
SSD: 60 GB
PSU: Silverstone ST1500W

I've disabled the Windows Firewall, I need help, I don't know what am I doing wrong.

[wacko]

I've tried using nanopool, ethermine, ethpool with all their servers and I'm getting the same error.

Even though it says that the pool closed connection remotely, I guess it could still be due to networking problems on your side? Can you check your network, whether the adapter in the rig works ok, the cable is alright and the router is functioning correctly?

This is also a valid question to the pool support. Run the miners with logging enabled and then contact the pool and send them relevant parts from those logs, asking why this could be happening. Maybe there's something in your miner's configuration that the pools don't like.

[m1n1ngP4d4w4n]

The cmdline you use to start your miner would help to see if there is any odd parameter.

Are you sure also that you execute the miner as admin ?

Check also if the process hasn't been locked out by Windows Defender.

[wacko]

Are you sure also that you execute the miner as admin ?

I don't think he needs to execute the miner as an admin. The only miner that needs this (that I'm aware of) is xmr-stak-cpu (and that's only for higher hashrate and not mandatory). Anything else, including the claymore ethereum miner he's using, doesn't require administrative privileges.

[m1n1ngP4d4w4n]

Are you sure also that you execute the miner as admin ?

I don't think he needs to execute the miner as an admin. The only miner that needs this (that I'm aware of) is xmr-stak-cpu (and that's only for higher hashrate and not mandatory). Anything else, including the claymore ethereum miner he's using, doesn't require administrative privileges.

Okay, doesn't hurt to try, but you are right probably not the issue.

[Visitante]

Even though it says that the pool closed connection remotely, I guess it could still be due to networking problems on your side? Can you check your network, whether the adapter in the rig works ok, the cable is alright and the router is functioning correctly?

This is also a valid question to the pool support. Run the miners with logging enabled and then contact the pool and send them relevant parts from those logs, asking why this could be happening. Maybe there's something in your miner's configuration that the pools don't like.

I double checked the cable and the router twice, I even have a second miner on the same network and it doesn't have the same problem.
I don't know if maybe the ethernet port came defective

The cmdline you use to start your miner would help to see if there is any odd parameter.

Are you sure also that you execute the miner as admin ?

Check also if the process hasn't been locked out by Windows Defender.

I disabled the Windows Defender

My cmdline is
set executable=EthDcrMiner64.exe
set commandline=-epool eth-us-east1.nanopool.org:9999 -ewal myewal.rigname/myemail -epsw x -mode 1 -ftime 10 -dcri 9

@heavyarms1912 helped me on that one.

Right now I'm not dual mining until I solve that problem and I'm only using one GPU

I think I will reset the MoBo BIOS, reinstall Windows and start over again.

[wacko]

If I would be having these problems I'd definitely try contacting the pools as well. It does say that "socket was closed remotely (by pool)", so it might be their doing and even if it's not there's still a good chance that they'll tell you why it could be happening. Just contact nanopool, tell them when it happened and maybe they'll help you with diagnosing this issue.

[m1n1ngP4d4w4n]

Have you tried other pools ?

Maybe in your early day of testing you sent alot of bad share to the pool and now you are banned (they usually ban you for a while when you do that)

Also you don't need "-dcri 9" in your cmdline if you mono-mine

[Visitante]

Thank you guys, I did contact ethpool a few days ago and all thei said was "add -allpools 1" to the bat file and that should do it... I said that was already on my bat file (because it was) and then they said "use another program" 

[wacko]

Thank you guys, I did contact ethpool a few days ago and all thei said was "add -allpools 1" to the bat file and that should do it... I said that was already on my bat file (because it was) and then they said "use another program" 

Then contact the other pools you have this issue with. You said it's the same with nanopool and ethermine, so try asking them as well. You can send them all the same question, so it shouldn't take you too much time to write it.

By the way, "use another problem" is not a bad idea. Not only there's plenty of older versions of the claymore's miner that you could try, but there are also other ETH miners that aren't that much slower (if at all).