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
not sure I understand. What do you mean "I matched my IPv4 address"?
IP address of the miner has to be different (after the last .) from your computer/laptop and unique for your LAN (no other piece of equipment with the same IP).
Also, you need a fourth lane-your DNS, which could be same as your router/getaway (10.8.201.1)
Sorry, let me try to explain better. My network ip address is 10.8.201.103 so I had to temporarily change my computer to 192.168.1.99 (plugged the miner into computer and the interface ran) . When i changed to try and get the miner to run on my network ip (10.8.201.103) I was never able to get back to the miner interface