Problem solved! I changed the miner over the DHCP. My neighbor was able to fire up the miner just fine.
Now to get him to pay be up w a 6 pack of beer!!!
Thanks to all forum friends for the help.
Topic: Boot problems w an S3 miner (Read 161 times)
It's not a problem if you can access the dashboard now you need to set the network by going to network settings and change it to static.
Sample settings below.
Ip Address: 192.168.1.99
Netmask: 255.255.255.0
Gateway: 192.168.1.1
DNS servers: 8.8.8.8
There is a possibility that his ISP or network DNS is blocking the miner for connecting to the pool so adding DNS like 8.8.8.8 and 8.8.4.4 might solve the issue.
Sample settings below.
Ip Address: 192.168.1.99
Netmask: 255.255.255.0
Gateway: 192.168.1.1
DNS servers: 8.8.8.8
There is a possibility that his ISP or network DNS is blocking the miner for connecting to the pool so adding DNS like 8.8.8.8 and 8.8.4.4 might solve the issue.
192.168.1.99 [typo].
I'll look into that. Still, I was able to find the miner on his network using 192.168.1.99 on my Smartphone using his wifi.
[...]
I'll look into that. Still, I was able to find the miner on his network using 192.168.1.99 on my Smartphone using his wifi.
been a while since I used that gear.
But here goes.
You have a router in his setup.
It could be
192.168.0.1
192.168.1.1
192.168.2.1
192.168.10.1
My guess is his router is not 192.168.1.1
But your router is 192.168.1.1
So it works on your setup.
And not his setup.
Your first step is to find the address of his router.
And then set the miner to the same channel number.
Say his router is 192.168.10.1
The miner would work with a 192.168.10.whatever.
But here goes.
You have a router in his setup.
It could be
192.168.0.1
192.168.1.1
192.168.2.1
192.168.10.1
My guess is his router is not 192.168.1.1
But your router is 192.168.1.1
So it works on your setup.
And not his setup.
Your first step is to find the address of his router.
And then set the miner to the same channel number.
Say his router is 192.168.10.1
The miner would work with a 192.168.10.whatever.
We hit the reset button on the front plate and it reset to 198.162.1.99 via default, and miner config is set for factory set antminer pools. I was able to login to the miner using my cell phone logged into the WiFi in both locations. I mines on my cable system. but not on his ATT setup.
Well, I'm an 18 month newbie in crypto, and I got started first with USB miners, then a few Butterfly Labs 700Gh miners, then moved on to various Antminers.
What a learning curve.
So I have a lot of 'retired' miners (and PSUs). I sold an S3 to a neighbor, and he can't get it running. Everytime he brings it back to my network, the miner boots fine an runs @ full hash rate. At his house, the miner boots (access via 192.168.1.99) but the red light stays on, and refuses to fully boot and mine. It show 0-0-0 in mining status, yet you can access other features (reboot, other menu items) as expected.
My ISP is Charter (local cable) Internet. His ISP is ATT.
This is a mystery where I need Geek friends. Suggestions to get this S3 (and future upgrades) up and running are welcome.
What a learning curve.
So I have a lot of 'retired' miners (and PSUs). I sold an S3 to a neighbor, and he can't get it running. Everytime he brings it back to my network, the miner boots fine an runs @ full hash rate. At his house, the miner boots (access via 192.168.1.99) but the red light stays on, and refuses to fully boot and mine. It show 0-0-0 in mining status, yet you can access other features (reboot, other menu items) as expected.
My ISP is Charter (local cable) Internet. His ISP is ATT.
This is a mystery where I need Geek friends. Suggestions to get this S3 (and future upgrades) up and running are welcome.
The s3 has a network setting. Do you have it set to dchp?
Or do you have it set to static in your case 192.168.1.99?
Well, I'm an 18 month newbie in crypto, and I got started first with USB miners, then a few Butterfly Labs 700Gh miners, then moved on to various Antminers.
What a learning curve.
So I have a lot of 'retired' miners (and PSUs). I sold an S3 to a neighbor, and he can't get it running. Everytime he brings it back to my network, the miner boots fine an runs @ full hash rate. At his house, the miner boots (access via 192.168.1.99) but the red light stays on, and refuses to fully boot and mine. It show 0-0-0 in mining status, yet you can access other features (reboot, other menu items) as expected.
My ISP is Charter (local cable) Internet. His ISP is ATT.
This is a mystery where I need Geek friends. Suggestions to get this S3 (and future upgrades) up and running are welcome.
What a learning curve.
So I have a lot of 'retired' miners (and PSUs). I sold an S3 to a neighbor, and he can't get it running. Everytime he brings it back to my network, the miner boots fine an runs @ full hash rate. At his house, the miner boots (access via 192.168.1.99) but the red light stays on, and refuses to fully boot and mine. It show 0-0-0 in mining status, yet you can access other features (reboot, other menu items) as expected.
My ISP is Charter (local cable) Internet. His ISP is ATT.
This is a mystery where I need Geek friends. Suggestions to get this S3 (and future upgrades) up and running are welcome.
Jump to: