Tuesday morning she noted the miners were failing to connect. She rebooted and restarted the miners and they still would not connect. She has left them idling and 36 hours later no change, the box still has internet.

Any ideas??

This is not some pseudoeconomic post-modern Libertarian cult, it's an un-led, crowd-sourced mega startup organized around mutual self-interest where problems, whether of the theoretical or purely practical variety, are treated as temporary and, ultimately, solvable.Censorship of e-gold was easy. Censorship of Bitcoin will be… entertaining.

Tuesday morning she noted the miners were failing to connect. She rebooted and restarted the miners and they still would not connect. She has left them idling and 36 hours later no change, the box still has internet.

Any ideas??

Would need some kind of error report, miner client, DNS/IP being used to connect.

Tuesday morning she noted the miners were failing to connect. She rebooted and restarted the miners and they still would not connect. She has left them idling and 36 hours later no change, the box still has internet.

Any ideas??

Have her install teamviewer on there so you can log into the thing remotely and check on it.

for a quick check have her try changing one or more of them to mine1, mine2 or mine3, depending on what they are pointed at now to check that.

If you're not excited by the idea of being an early adopter 'now', then you should come back in three or four years and either tell us "Told you it'd never work!" or join what should, by then, be a much more stable and easier-to-use system. - GAIt is being worked on by smart people. -DamienBlack

Bumping this up to stress again that all users of cgminer should immediately upgrade to the latest version! You will definitely see a performance improvement since the longpoll handling has been fixed to not cause occasional problems with PoolServerJ-based pools.

Bumping this up to stress again that all users of cgminer should immediately upgrade to the latest version! You will definitely see a performance improvement since the longpoll handling has been fixed to not cause occasional problems with PoolServerJ-based pools.

People mining on port 80 mine2.btcguild.com/mine3.btcguild.com should now be properly getting longpolls on any miner. The LP connection for port 80 was still being attempted through the standard port 8332. It is now handled entirely through port 80.

Unfortunately, it looks like the problem is on your end for this one. I just launched a cgminer session (2.4.1) pointed at http://mine2.btcguild.com:80/, and it returned no errors. Same with using mine3.btcguild.com.

Last night there was a brief connectivity issue between the website and the database server, so the website's hourly log of your share counts [used to calculate speeds] was skipped. It was then captured the next hour, resulting in the graphs displaying 2x the hash speed.