Topic: ANTMINER S3+ Discussion and Support Thread - page 32. (Read 710164 times)

No that is not normal to have to connect to laptop between each time you lose connection.  Are you not able to access it through lan connection?  Are you setting up wifi from latptop each time?

If so sounds like a networking error.  Can you post screenshots of your lan networking settings?

The gateway is ok, I changed it to be 192.168.1.1 manually on my router. But the Antminer is working but still not showing.

Also, I had a electricity shortage last night, and for the Antminer to restart I had to plug back my laptop to it, disconnect it from the WAN so it could reconnect on the WIFI.
Is that normal ? It's like if it was trying to connect via WAN and as long as there is no connection it kept trying until I deconnect it, then It tried WIFI....

Hi all, I have old S3/S3+ firmware here.
Read thread to find out which fw you need.

I've had many routers in the last few years and they've all shown up Antminer devices. Is the gateway IP correct?


Or bitmain.zendesk.com.

ok I'll be damned...

my router ip address is: 192.168.1.1
subnet mask : 255.255.255.0
Default gateway: 192.168.1.1

I connected my S3 directly to my router with ethernet cable.
I had no problem accessing the interface from any browser just by typping 192.168.1.99.

Went into WAN setting, change S3 ip address to 192.168.1.199
Set up my pools, then S3 start mining without any problem.

Then went to network, wifi, scan, join network, entered my password, selected WAN in (assign firewall-zone), clicked submit, then save and apply.

Then went to WWAN edit settings, left it to DHCP protocol, save and apply.
Unplugged the ethernet cable from my router, and restarted manually the S3.
Checked in router what Ip address was given, and UNKNOWN device is on 192.168.1.95
But it's unaccessable from any browser and the S3 is clearly not hashing.

Reconnected the ethernet cable to the router, easy access to 192.168.1.199
S3 is now hashing.

Went to WWAN settings
Changed protocol to static ip address and put these in
IPv4 address 192.168.1.155
IPv4 netmask 255.255.255.0
IPv4 gateway 192.168.1.1
IPv4 broadcast
Use custom DNS servers  192.168.1.1
then save and apply.

Then stop the WAN and deconnected ethernet cable from the router.

F**k me ! HOLY COW !! Written all that for nothing, it's working now !!!!
I'll leave it here in case it might help someone else.


But weird thing... I don't see the S3 in my router DHCP client list... anyone knows why?

Moving it to somewhere else and shutting it down, required me to plug my laptop back to it with ethernet to stop the WAN connection again, and then It restarted on the WIFI connection.

If it is a software issue on the controller it's possible it might be recovered using serial to usb. - https://bitcointalksearch.org/topic/bitmain-s3-serial-connect-889206

If you truly mean the board somehow got burned and has physical damage you can contact Bitmain Support to get a new one. (not sure current price)  Can do a ticket for it here - https://bitmain.zendesk.com/hc/en-us

Thats the link I found...I went thru the sequence, but had no luck.   I think the communication board is burnt up.

Best documentation on reset is right here - https://bitcointalksearch.org/topic/setup-troubleshoot-bitmain-antminer-s3-440ghs-miner-697474 .  It's at end off first post hope that helps.

I will look for a link on how to do the factory reset.  Thanks for your help. HerbPean

DNS resolving an internal IP is allowed even hosting on public external servers.  Might be a security risk, but it is allowed and does works.  DNS just resolves a name to an IP.

This is done at major corporation all day long.  Only difference is they restrict via ACL the IPs that can resolve to the servers that have the internal IP addresses.

There should be nothing that keeps this from working, but it does not on an S3+

I could setup just an internal DNS server as you are referring to, but functional external or internal DNS servers should not matter.  Have you done this and know that this will fix the issue?

its because you arent doing it right.. you shoudlnt DNS an internal IP..
most routers have naming built into them. you should use that instead.

proxy-a.brokenshop.net resolves to 192.168.1.133 Bitmain S3+ does not resolve this address via Ping or Configuring as a pool

If I put the IP address is 192.168.1.133 in the pool config everything works fine.

Everywhere else in the world this DNS entry resolve correctly except on these Bitmain devices.

Even at my office, behind many corporate firewalls it still resolves.  Just not on these Bitmains for some reason.

C:\>ping proxy-a.brokenshop.net

Pinging proxy-a.brokenshop.net [192.168.1.133] with 32 bytes of data:
Request timed out.
Request timed out.

Ping statistics for 192.168.1.133:
    Packets: Sent = 2, Received = 0, Lost = 2 (100% loss),
Control-C
^C
C:\>

im still confused as to what you are running into..

so you are using a proxy to mine through, but you can still set it to IP and change the proxy on the host computer just the same.

the IP on the host computer shouldn't change, if you set it to static.

Modding the config via SSH takes a lot longer then just setting something that should work anyways.  I am really surprised no one has run into this before.

um, its pretty easy to change their config, just enable the write access to the api and use a program like cryptoglance.

sucks you would have to do each one because its not enabled by default, but once it is, you can just upload the new config to them all at once vie api.

No cause I am configuring over 100 S3's if I use an IP it is very hard to change their config, as with DNS I can change it on the server.  I am pretty sure this is a Bitmain issue as the DNS is hosted by GoDaddy and works on all other platforms I tested BTCGarden, Linux, Mac, and Windows.

Going to test Bitmine, MAT, and others tonight, but I am assuming they will all work.

just use the ip.

its probably not the s3 fault, its the network dns is windows only.

Thanks

Call Bitmain Support, I believe they will replace a board for $25.

That is the exact point.  This is an internal proxy only, no one else should have access to it.

The problem is the Bitmain S3 refuse to resolve the address.