[/quote]
Whatever you do, do NOT follow these instructions. This guy is giving his machine an EXTERNAL IP with his setup leaving it completely vulnerable and open to the public internet to be hacked.
The beeping is due to it not sensing internet. It can be a number of things. IP conflict, DNS issues, bad network cable, etc. I would verify all settings as well as swapping with a known good cable. Also you might want to factory reset the controller in cause something got borked in the configs. You can do this by using a toothpick to push in the reset button to the right of the ethernet port. Hold it down until you see both red and green lights blink at the same time and it beeps. This will put it back to DHCP so you can then find its IP, browse to it, and put all of your settings back in.
[/quote]
Do I say somewhere that my S7 has an external ip?!
When you (x) static ip address on s7 setting (e.g. S7 has x- for a static ip 192.168.0.27, from e.g. Adv. ip Scanner). Antminer has to run a specific static ip 192.168.0.27. But ISP, for some reasons many ISP for home internet are not allow any customer home pc has static IP, but only running with dynamic ip. Antminer is beeping cause of networking ip conflicted. It is conflict with ISP domain name system (DNS). In this case it has nothing to do with bad cable; resetting Antminer
I learned to known these conflicts since Antminer s3 with Windows XP.
My extra static ip that I ordered from ISP has accepted Antminer static IP 192.168.0.27 and another static ip that Antminer has chosen in all of my Antminer that they are mining. And easy when I have to recounting them to pool.