Help Requested for incorrect network settings for S2 Antminer.

[jpsmith8488]

I first tried connecting the S2 directly to my MacBook Pro. This allowed me to login to the S2 but it would not hash, likely because it could not reach the Internet. At that time the Internet was connected to the MBP by Wi-Fi. I then received the suggestion to connect the S2 directly to the router. I did so but now I cannot connect to the MBP using the default address 192.168.1.99. Here are the network settings for the three devices:

S2 Antminer
Type: Static
Address: 192.168.1.99
Netmask: 255.255.255.0
Gateway: 192.168.1.1
DNS: 192.168.1.1

MacBook Pro
Configure IPv4: Using DHCP
Subnet Mask: 255.255.255.0
Router: 192.168.168.168
Configure IPv6: Automatically
Router: blank
IPv6 Address: blank
Prefix Length: blank
DNS: 8.8.8.8, 8.8.4.4, 192.168. 1.1 (I added this from the S2)

Apple Extreme Base Station Router
Connect Using DHCP
IPv4 Address: 192.168.168.144
Subnet Mask: 255.255.255.0
DNS Servers: 75.75.75.75, 75.75.75.76

Do you see any settings that I could change to allow my MacBook Pro and the S2 to resume communication? Likewise, are there any setting changes I need to make to allow the S2 to hash?

Thank you,
Justin

[1715550165]

1715550165

[1715550165]

1715550165

[1715550165]

1715550165

[rarkenin]

You should put the S2 on your actual subnet. Looking at your subnet mask, that means that the S2 needs to get an IP address that is 192.168.168.***, where *** is an integer between 0 and 255 (inclusive) and not either 144 or 168 (since that would be a duplicate). The easiest configuration would be to leave everything the same except the antminer:

S2 Antminer
Type: Static
Address: 192.168.168.99
Netmask: 255.255.255.0
Gateway: 192.168.168.1
DNS: 8.8.8.8

I would set DNS to 8.8.8.8 as that's a well-known public DNS run by Google, while I have no idea if your router would provide DNS on 192.168.168.144. (192.168.1.1 would not work, as there is no actual device there)

You can then access the device at 192.168.168.99, it has a gateway to connect to the internet with, and everything is on a single valid subnet.

[jpsmith8488]

Thank you Rarkenin for your quick reply with such specific advice. Thank to you I now have the S2 and the MacBook Pro connected to the router and i am able to login to the S2 from the MBP. I still have no hashing even though I have added my credentials for Pool 1 of the Miner Configuration. Is there anything else I can do or check to get hashing to commence?
Here is the information I am using to access Slushes Pool:

api.bitcoin.cz:8332
smith123.worker1
R3ws2n

I have left the information for Pool 2 and pool 3 with the default information that came with the S2.

Any advice will be welcome.

Thank you,

JPS

[rarkenin]

S2 and other large miners support Stratum. Use a URL such as:

Code:

stratum.bitcoin.cz:3333

or

Code:

stratum+tcp://stratum.bitcoin.cz:3333

[jpsmith8488]

Thank you for the suggestion to use the stratum protocol. I have now got the S2 connected to the router by an ethernet cable and the MacBook Pro connected by Wi-Fi. Using 192.168.168.99 in the browser, I am able to connect to the S2 via the router. This is a good step forward. I then enter the following for the miner configuration:

stratum.bitcoin.cz:3333
jpsmith848.worker1
password

stratum+tcp://stratum.bitcoin.cz:3333
jpsmith848.worker1
password

stratum+tcp://mint.bitminter.com:3333
jpsmith848.worker1
password

and still no hashing. I don't know what else to check. Do you have any suggestions?
Best,
JPS

[rarkenin]

Unfortunately I do not own an S2 I could check on, so I can't seem to help you there. Now that you've established a worksable diagnostic network connection, Bitmain should be able to help you.

Anyway, is there any sort of network ping test you can do that originates from the S2 itself? Or try a different pool such as Eligius, that doesn't validate a password?