Topic: [Guide] Dogie's Comprehensive Bitmain Antminer S3 Setup [HD] - page 6. (Read 137862 times)

Hi Guys, appreciate the help
Mikestang - going to change the IP address as it is currently set to what you suggested and hopefully that will work.

dogie - unfortunately i couldn't add a screenshot to this so i've just copied and paste the information:

Wired Devices
 IP Address   Device Name   Time Connected
192.168.X.X    XXxXXXXX   0days 00hrs 21mins 18s
192.168.1.99                      0days 00hrs 01mins 19s


Wireless Devices
IP Address            Device Name    Time Connected
192.168.X.X     XXXXimac         0days 00hrs 25mins 31s

Can you post a screenshot of your router's DHCP table (which I assume is what you're looking at?)

Are you connecting to if from a machine with the IP address of 192.168.1.xxx?  If you did not change the ip on your computer chances are it is 192.168.0.xxx and so you wouldn't be able to see the S3.

Hi guys,

been reading through this thread and some very helpful information, the guide by dogie is great. i'm only just starting to mine so my knowledge on this is minimal.   
I purchased an S3 to see how things work and in need of some help so any advice will be great from anyone..

i've connected the S3 to my router, reset it to default settings and can see it within my connected devices but when i go to 192.168.1.99 i get message "This webpage is not available" any suggestions?

Regards.

OK here's the catch and how I set it up:

I Put a static IP to the Jetpack (.1.1) and the EX6200 extender (.1.2).
I also put a static DNS Server (.1.1) so when rebooting it does not pick up alternative wireless
networks it may decide to try connect to first.
The Verizon Jet Pack Hot Spot in 3G only allows you 5 connections/IP addresses
and most the time it's only 4 connections. I will be calling Verizon Tech support on this.
In 4G it allows 10 connections/IPs which gives me 9 miners once I disconnect my laptop
since the Extender takes up one connection.

Problems:
When I set the Jetpack to only use 4G it would never connect
to the internet ever. Very strange.
In 3G mode it will pick and choose which IPs to connect to the net
and when you reboot the EX6200 or the Jetpack if you have more than 4 IPs
connected to the Extender the connections would vary.

What I had to do is:
1-Set the Jetpack to Automatic.
2-Boot everything up and let it connect to a few IPs.
3-Shut the Jetpack down.
4-Reboot the EX6200 Extender.
5-Immediately turn on the Jetpack.
Every time I follow this procedure I get 4G and all IPs.
Every time I don't I get 3G and 4 connections and though it may
switch to 4G or be 4G from the boot up of the Jetpack it will
either not connect to the net or only give me 4 IP's.

For some reason this procedure makes the Jetpack choose 4G
and I get the entire 10 IP connections.
Yesterday I had 5 miners running.
Today it's 6. Hopefully tomorrow it will be 9.

Go figure!?

MM

NOTE:
The Jetpack is 175ft away from the EX6200 Extender.
Connection through a 10" cement block wall and two 5/8" sheet rock steel studded walls
covered both sides on both walls.

Glad you got it fixed up!  It sure was a pain, but ended well

I was at a loss after talking to you and our teamviewer session.

Happy Mining!

They are all running.
Had to reboot the Verizon Hot Spot and the extender.
Who knew!
The first two miners hooked up without a hitch

Thanks for your time and efforts!
 
Will let you know what happens...

MM

Going to send PM.  Please make sure no confidential/wallets/passwords are up.  I am on need to know basis .

Hopefully teamviewer will speed it up.

I have 3 of S3s and 1 of S1 all not running all on different cables all on same PSUs as the working S3 and S4.

Im willing to do teamviewer if you are!
 

The ones not mining have 20+ active connections.
The one mining has 3 active connections.

I compared everything in all the network settings and  are the same

Well the DNS should have fixed a possible problem.   Is there anything different with this then the other's that are working?  Have you made sure not bad cable/port on network.  Are they using different PSU's.   What is different between setups?

If this continues you might want to try teamviewer with someone.  The posting method if common fixes are not getting it can take a while.

I rebooted and pinged but still same:
ping: bad address 'openwrt.org'

EDIT:
I unplugged it and still the same...

And did it start mining after?   Or what did it do?

I changed:
"Use custom DNS servers": to 8.8.8.8

That is why i suggested googles 8.8.8.8 .   I have a feeling everything will start working after that.

Or he really want's to keep his current or some reason change pool to it's IP. 

Either way I'm hoping hes back in a few minutes with good news.

Try using a real DNS server and not your local machine.

Looking above try a different DNS server.  I like 8.8.8.8  it is a DNS managed by google, and easy to remember

Let me know what happens after trying different DNS.

OK I hit "sync with browser" and save/apply.

Still pinging a bad address...

EDIT:
Tried rebooting. Same issues.