Antminer S1 not connecting to internet via LAN

[mipmip]

Hi all,
I became a bitcoin miner 2 days ago since I got my Antminer S1 unit.
I would like to get some help here as I'm not able to mine via the LAN connection.
The unit I have was new.

I followed the instructions from topic '[Setup & Troubleshoot] Bitmain AntMiner S1 180GH/S miner' but I can't get it working.

Below my setup:
Antminers IP: 192.168.2.99
Router IP range: 192.268.2.xxx

I connected the power supply, LAN cable to my pc (IP set to 192.168.2.200).
Loged in, LAN was on DHCP, WAN I didn't touch. Entered my pool data.
Connected via Wifi as I didn't had a LAN connection in the kitchen to test and .. miner was mining.

Unplugged everything, moved to empty room with LAN plug.
Connected everything and ... miner not mining .. beeps coming from miner however  I can access the miner via LAN through my router.

https://i.imgur.com/Ul8T5mF.jpg
https://i.imgur.com/eoujAAO.jpg
https://i.imgur.com/oc6wzj5.jpg
https://i.imgur.com/SN8FUm0.jpg
https://i.imgur.com/tCUb1au.jpg


What did I forget ?
Help appreciated

Peter

[mipmip]

Can Wifi and LAN be used at the same time ?

[soulofhoney]

Hi i have antiminer s2. I cannot seem to hard reset it after getting locked out. I followed bitmains instructions for the reset since s2 has a reset button. but no luck. Please help help...

EDIT: I actually got back in now. But now i have the ntp errors. they go like this:

Sun Jan 19 01:48:03 2014 daemon.info dnsmasq[2545]: using local addresses only for domain lan
Sun Jan 19 01:48:03 2014 daemon.info dnsmasq[2545]: reading /tmp/resolv.conf.auto
Sun Jan 19 01:48:03 2014 daemon.info dnsmasq[2545]: using nameserver 8.8.8.8#53
Sun Jan 19 01:48:03 2014 daemon.info dnsmasq[2545]: using local addresses only for domain lan
Sun Jan 19 01:48:03 2014 daemon.info dnsmasq[2545]: read /etc/hosts - 1 addresses
Sun Jan 19 01:48:31 2014 daemon.info sysinit: ntpd: bad address '1.openwrt.pool.ntp.org'
Sun Jan 19 01:48:31 2014 daemon.info sysinit: ntpd: could not resolve peer 1.openwrt.pool.ntp.org, skipping
Sun Jan 19 01:49:01 2014 daemon.info sysinit: ntpd: bad address '0.openwrt.pool.ntp.org'
Sun Jan 19 01:49:01 2014 daemon.info sysinit: ntpd: could not resolve peer 0.openwrt.pool.ntp.org, skipping
Sun Jan 19 01:49:07 2014 daemon.info sysinit: Alarm clock
Sun Jan 19 01:49:37 2014 daemon.info sysinit: ntpd: bad address '3.openwrt.pool.ntp.org'
Sun Jan 19 01:49:37 2014 daemon.info sysinit: ntpd: could not resolve peer 3.openwrt.pool.ntp.org, skipping
Sun Jan 19 01:50:07 2014 daemon.info sysinit: ntpd: bad address '2.openwrt.pool.ntp.org'
Sun Jan 19 01:50:07 2014 daemon.info sysinit: ntpd: could not resolve peer 2.openwrt.pool.ntp.org, skipping
Sun Jan 19 01:50:37 2014 daemon.info sysinit: ntpd: bad address '1.openwrt.pool.ntp.org'
Sun Jan 19 01:50:37 2014 daemon.info sysinit: ntpd: could not resolve peer 1.openwrt.pool.ntp.org, skipping
Sun Jan 19 01:51:01 2014 cron.info crond[548]: crond: user root: process already running: /usr/bin/cgminer-monitor
Sun Jan 19 01:51:07 2014 daemon.info sysinit: ntpd: bad address '0.openwrt.pool.ntp.org'
Sun Jan 19 01:51:07 2014 daemon.info sysinit: ntpd: could not resolve peer 0.openwrt.pool.ntp.org, skipping
Sun Jan 19 01:51:13 2014 daemon.info sysinit: Alarm clock
Sun Jan 19 01:51:43 2014 daemon.info sysinit: ntpd: bad address '3.openwrt.pool.ntp.org'
Sun Jan 19 01:51:43 2014 daemon.info sysinit: ntpd: could not resolve peer 3.openwrt.pool.ntp.org, skipping
Sun Jan 19 01:52:13 2014 daemon.info sysinit: ntpd: bad address '2.openwrt.pool.ntp.org'
Sun Jan 19 01:52:13 2014 daemon.info sysinit: ntpd: could not resolve peer 2.openwrt.pool.ntp.org, skipping
Sun Jan 19 01:52:43 2014 daemon.info sysinit: ntpd: bad address '1.openwrt.pool.ntp.org'
Sun Jan 19 01:52:43 2014 daemon.info sysinit: ntpd: could not resolve peer 1.openwrt.pool.ntp.org, skipping
Sun Jan 19 01:53:13 2014 daemon.info sysinit: ntpd: bad address '0.openwrt.pool.ntp.org'
Sun Jan 19 01:53:13 2014 daemon.info sysinit: ntpd: could not resolve peer 0.openwrt.pool.ntp.org, skipping



Any ideas what to do? I have changed the WAN dns to 8.8.8.8. I don't think it made any difference.