My Antminer S3 won't mine

[Leooo.C]

Setting is listed below

Pool http://api.bitcoin.cz:8332

Pool1 worker Leooo.worker1

Pool1 password

Pool 2 stratum+tcp://stratum.btcguild.com:3333

Pool2 worker Leooo_1

Pool2 password


Protocol

IPv4 address 192.168.1.99

IPv4 netmask 255.255.255.0

IPv4 gateway 192.168.1.1

IPv4 broadcast 192.168.1.255

Use custom DNS servers


I want to know the reason. Please help

THANKS

[1713414070]

1713414070

[1713414070]

1713414070

[1713414070]

1713414070

[1713414070]

1713414070

[1713414070]

1713414070

[Easy2Mine]

https://bitcointalk.org/index.php?topic=702653

Read this manual.
Good luck

[Leooo.C]

i have read it. but i am not understand what i have done wrong...

[silverthornne]

Your Antminer probably can't reach the internet. Do you have any devices that can actually reach the internet from that subnet? Just change its IP address to something from within the 192.168.0 subnet such as 192.168.0.99.

Edit: Forgot to add that you will probably want to go into your router and permanently assign that IP address to your Antminer's MAC so there won't be any conflicts.

[kabopar]

Setting is listed below

Pool http://api.bitcoin.cz:8332

Pool1 worker Leooo.worker1

Pool1 password

Pool 2 stratum+tcp://stratum.btcguild.com:3333

Pool2 worker Leooo_1

Pool2 password


Protocol

IPv4 address 192.168.1.99

IPv4 netmask 255.255.255.0

IPv4 gateway 192.168.1.1

IPv4 broadcast 192.168.1.255

Use custom DNS servers


I want to know the reason. Please help

THANKS

Use the address stratum.bitcoin.cz:3333 for Pool1
Use the worker style of  "Leooo.worker1", where "Leooo" is your registered user name and worker1 your registered worker. The password of worker1 has to be consistent with what you registered on Slush's pool (check Slush's instructions).
These entries have to be precisely what the pool requires, no additional 'spaces' or 'variations'.
There is no point in having 2 entries into the same server on the same pool.

Cheers

[Leooo.C]

Setting is listed below

Pool http://api.bitcoin.cz:8332

Pool1 worker Leooo.worker1

Pool1 password

Pool 2 stratum+tcp://stratum.btcguild.com:3333

Pool2 worker Leooo_1

Pool2 password


Protocol

IPv4 address 192.168.1.99

IPv4 netmask 255.255.255.0

IPv4 gateway 192.168.1.1

IPv4 broadcast 192.168.1.255

Use custom DNS servers


I want to know the reason. Please help

THANKS

Use the address stratum.bitcoin.cz:3333 for Pool1
Use the worker style of  "Leooo.worker1", where "Leooo" is your registered user name and worker1 your registered worker. The password of worker1 has to be consistent with what you registered on Slush's pool (check Slush's instructions).
These entries have to be precisely what the pool requires, no additional 'spaces' or 'variations'.
There is no point in having 2 entries into the same server on the same pool.

Cheers

I have double checked the worker & password. They are both correct.

[bitcoin_miner]

Setting is listed below

Pool http://api.bitcoin.cz:8332

Pool1 worker Leooo.worker1

Pool1 password

Pool 2 stratum+tcp://stratum.btcguild.com:3333

Pool2 worker Leooo_1

Pool2 password


Protocol

IPv4 address 192.168.1.99

IPv4 netmask 255.255.255.0

IPv4 gateway 192.168.1.1

IPv4 broadcast 192.168.1.255

Use custom DNS servers


I want to know the reason. Please help

THANKS

I have same problem with you. but now work fine. trouble caused you not change 192.168.1.99. Please change IP to 192.168.1.97. After you change it. you S3 will work fine.

[Biodom]

Setting is listed below

Pool http://api.bitcoin.cz:8332

Pool1 worker Leooo.worker1

Pool1 password

Pool 2 stratum+tcp://stratum.btcguild.com:3333

Pool2 worker Leooo_1

Pool2 password


Protocol

IPv4 address 192.168.1.99

IPv4 netmask 255.255.255.0

IPv4 gateway 192.168.1.1

IPv4 broadcast 192.168.1.255

Use custom DNS servers


I want to know the reason. Please help

THANKS

Use the address stratum.bitcoin.cz:3333 for Pool1
Use the worker style of  "Leooo.worker1", where "Leooo" is your registered user name and worker1 your registered worker. The password of worker1 has to be consistent with what you registered on Slush's pool (check Slush's instructions).
These entries have to be precisely what the pool requires, no additional 'spaces' or 'variations'.
There is no point in having 2 entries into the same server on the same pool.

Cheers

I have double checked the worker & password. They are both correct.

1. do you have anything else on your network with IP 192.168.1.99 address?
check with advanced IP scanner (on PC) or iNEt (on mac). It will also show at what address your miner actually is (it should show Paragon Technologies)
2. what do you mean Protocol? WAN? Check out your miner WAN settings, not LAN-maybe you setup LAN instead?
3. if address is incorrect, miner status should say "Dead" to the right of wallet/or worker name. It would say "alive" if it is correct.
4. did the miner hashed when first connected? It should have because it has the antpool default settings.

[Leooo.C]

Your Antminer probably can't reach the internet. Do you have any devices that can actually reach the internet from that subnet? Just change its IP address to something from within the 192.168.0 subnet such as 192.168.0.99.

Edit: Forgot to add that you will probably want to go into your router and permanently assign that IP address to your Antminer's MAC so there won't be any conflicts.

I don't think I can't change the IP address to 192.168.0.XX. Since  all my devices start with that.

I go to my router and I can only see one miner connected, but I can login to two different miner with different addresses 192.168.1.11 & 192.168.1.22.

What should I do in next step?

Thanks