Post
Topic
Board Hardware
Re: ANTMINER S3 Discussion and Support Thread.
by
ibminer
on 23/07/2014, 17:26:58 UTC
I have a bit of a problem. Hoping someone can help, I'm fine with computers but have no clue when it comes to network addresses etc.

To start with, I couldn't change the routers subnet so I went through a direct PC connection. Logged into the Ant fine & changed to DCHP. The Ant still had 192.168.1.99/24 as the IPv4 address at that time.

Here's where I went wrong perhaps, I had to connect to the internet again to get details for my pool (having to disconnect from the Ants), and since then I haven't been able to re-login to the Antminers. I've tried resetting them and trying to find them via the router, but they are not there. Anyone have any idea what went wrong/how I can login to them again pls?

Download Advanced IP Scanner and run that. It should find your Ant.

Good advice, but if you do find the IP address is still .1.99 and you can't log into it try a factory reset and plug directly in again.  I had a similar problem with my S1 when I first got it.  Played around with the settings and couldn't even connect directly to my lappy.  I could see it using IP scanner, but couldn't get to the login page because of the different subnet.  

I just changed the IP on my miner after to suit my routers subnet (.0.99)

Now doing a factory reset on an S3, I'm a B3'er so I have no idea if this is possible.  On the S1 there was a tiny button on the logic board.  I'd press it, then turn off at the power supply about 5 seconds after, power back up and it would be back to factory settings.

Hope that helps  Smiley

Thanks silverthorne, that was exactly the problem.

atledenin, Both Ants were still 192.168.1.99 but no matter how many times I reset the things I can't seem to log in as I did before.  This is getting frustrating, even GPU mining felt easier than this lol

Do you have both miners running on the same network, at the same time?   If so, try just doing one at a time to avoid any IP conflicts and change its IP before starting up the other.

Yes this may have been part of the initial problem, but I can't be sure. Certainly later when they were suddenly recognized again I found the software swapping between them so assigning separate IPs is essential.  thx for your help

And just to re-state my prior post, I had issues with making certain changes through the web interface using Safari and ended up having a smoother experience using firefox and/or chrome (I tried both). Not entirely sure why Safari was having issues but it wasn't changing the IP when I was using Safari.

Also - make sure you are modifying the right 'adapter' (not the bridge)