Quote from: itod on August 05, 2014, 05:43:04 PM

Quote from: not.you on August 05, 2014, 05:17:28 PM

Quote from: wlefever on August 05, 2014, 03:53:13 PM

Quote from: waldohoover on August 05, 2014, 03:50:50 PM

Quote from: wlefever on August 05, 2014, 03:46:50 PM

Quote from: opieum2 on August 05, 2014, 10:25:26 AM

Quote from: Duce on August 05, 2014, 04:14:08 AM

Quote from: opieum2 on August 05, 2014, 03:29:29 AM

I got an issue with one of my S3s. It does not hash at all. I can connect to it no problem. This one appears to have an issue where the unit does not hash at all. All the settings are identical to the other ones (minus the IP addresses which are statically assigned. I can connect to it from within my lan to get to the web interface. cgminer appears to be running but not hashing. Anyone run into this? It seems like it would be a quick fix. Thanks

Did you open it up and check the cables from the blades to the controller? You could try to reseat the cables as well. If that does not fix it the next step would be to swap out controllers to determine if it is the blade/s or controller. I did not cover the power supply verification as I am sure you have already been down that road. Please let us know what you find.

I will give that a try. I checked on the IP conflict and that was not an issue. I statically assign everything in my network so I know thats not it. But just the same I checked just in case. I will open it up and check it. I will post back if that was the problem.

Why after I statically assigned my ip address on my miner can i not pull the interface back up on the web browser?

Did you set your subnet mask and dns settings correctly?

Yeah I matched my IPv4, subnet mask, and default gateway

10.8.201.103
255.255.255.0
10.8.201.1

But, cant seem to reach the miner again

I would be really surprised if the subnet mask on that network was really 255.255.255.0. That IP is a class A address which (without any fancy subnetting) would be 255.0.0.0 for the mask.

You are right, 255.0.0.0 is probbably the right netmask, but that shouldn't be an issue since they are almost certanly within the same C class (first three dot separated numbers in IP address are the same), so machines would see each other even with the wrong netmask. The issue may be that he has collison on the network since he gave the same IP (10.8.201.103) to both his computer and the miner. If that's the case ask your network admin to give you another IP for the miner.

It's interesting to notice that people are avoiding to use DHCP with the S3s because they often run into problems not following proper DHCP network administration. Proper procedure would be to find your miners MAC address, and then reserving fixed IP address for that MAC address in your DHCP server settings. Your DHCP server is almost always on your router, find those settings through web interface of your router. This way you won't have to monkey around with DNS and other settings, and your S3 will have non-changing IP which you will always be able to find.

Okay I figured out what the IP of the first miner was because I set it up for DHCP and it assigned 10.8.201.178. Now when I plug the 2nd miner to my laptop to connect I get a conflicting ip address notice. What do I need to change now to be able to connect my laptop (10.8.201.103) to the second antminer s3 (192.168.1.99) to reach the interface screen and go through the settings to change to DHCP client so that it automatically assigns the 2nd miner an ip?