Bitcoin Forum
May 11, 2024, 12:20:59 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Second S2 Antminer is connected to network but will not hash.  (Read 905 times)
jpsmith8488 (OP)
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
July 24, 2014, 12:29:39 AM
 #1

On my network, I have one S2 Antminer with IP Address 192.168.168.99 that is successfully hashing at around 1000GH/sec. I added a second S2 Antminer, set up the IP Address as 192.168.168.98, achieved a successful connection with my MacBook Pro over the network, and entered the same three pool settings that are working well for my first S2.

To my surprise, hashing does not commence. I have reseated the blades and control board and tightened the cable connections but it did not help. Pinging 192.168.168.98 shows a functioning connection. I am at a loss to try to troubleshoot this problem further and I welcome any suggestions.

Thank you,

Justin
1715430059
Hero Member
*
Offline Offline

Posts: 1715430059

View Profile Personal Message (Offline)

Ignore
1715430059
Reply with quote  #2

1715430059
Report to moderator
The grue lurks in the darkest places of the earth. Its favorite diet is adventurers, but its insatiable appetite is tempered by its fear of light. No grue has ever been seen by the light of day, and few have survived its fearsome jaws to tell the tale.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715430059
Hero Member
*
Offline Offline

Posts: 1715430059

View Profile Personal Message (Offline)

Ignore
1715430059
Reply with quote  #2

1715430059
Report to moderator
d2dtk
Hero Member
*****
Offline Offline

Activity: 518
Merit: 501


View Profile
July 27, 2014, 09:41:25 PM
 #2

Do you have a different user name for each pool?

Maybe an image of your settings from the miner would be beneficial

jpsmith8488 (OP)
Newbie
*
Offline Offline

Activity: 23
Merit: 0


View Profile
July 29, 2014, 01:17:19 PM
 #3

Thank you for your suggestions. I finally recognized that the problem was caused by a port conflict. I changed the port settings and both miners are now hashing.
Justin
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!