Quote from: sdjernes on December 10, 2014, 04:35:07 PM

Quote from: ChineseSavior on December 10, 2014, 07:02:20 AM

now after series of resets it is saying it is mining server side but not showing on reward etc pool side. But any pool I use (after I reboot only) it says it is mining. If i try to change to any different pool without rebooting it will not hash (miner side)

using this reboot sequence.no matter what pool i use it is showing miner not pool side. Huh

thats about the best info i think.

Would a home router have a limit to how many connections can be attached? I have 17 devices attached via eternet and switches to 4 routerports

First thing I would just try a reboot on your router. If you do DHCP for your miners, try moving them to static IPs in your subnet. Make sure those static IPs are not in the "Dynamic Space" that your router assigns as some other device on your network may be taking the address. IP networking works mostly by a who responds first method, so if you have two devices that somehow get the same IP (should not happen with DHCP, but depending on the software in the router it can), the faster guy wins and a PC, Tablet, Phone etc... which are designed to be more real time will almost always win.

If your router supports it (and you can find it), look at the connected devices page. See what MAC address it says for the IP you have assigned to the miner. Compare that with the info from the minor info screen.

It is rare, but some older home router firmware (or broken firmware) will not have a good NAT (Network Address Translation) table that will make is so something that connects gets dropped. This most often only happens with things like VoIP and Gaming but can happen with other protocols. If you can, I would find a "High Quality" not "High Priced" router, and better yet try a custom firmware load like DD-WRT or OpenWRT if you have the willingness to go that far.

I run an older Netgear WNDR3700 v3 with DD-WRT with over 25+ devices doing both outbound and inbound connections.

I was just going to suggest this. Every time one of my S3s stops hashing, its the damn router causing it and a reboot of the router fixes it.