Topic: Tons of "problem communicating...RPC" and "idle" errors (Read 1123 times)

From what I can see they have a number of hosts you can try depending on server load and your location:

nl2.btcguild.com   Netherlands   
nl.btcguild.com   Netherlands
uscentral.btcguild.com   Texas   
uswest.btcguild.com   California   
useast.btcguild.com   Florida   
de.btcguild.com    Germany   

So if you have tried all of these and still cant connect try entering a servers IP (rather than its DNS hostname) eg:

For uswest.btcguild.com server enter 69.42.217.226 instead

I'm not sure how to check about the DNS servers, but I did the flush. Trying again now.

I had the "host" in the servers file without the http, yeah.

What DNS servers are you using?

Shutdown guiminer

click start>run> key in cmd, hit enter >key in ipconfig /flushdns

Open guiminer and try again

Failing that shutdown the miner, delete the directory, then run, extract & try it again

Edit: You do have btc guilds hostname entered in the miner without the http:// prefix dont you?

You don't need to forward to mine.

Before I try that, is it possible I'm getting these errors but it's working fine?

I seem to be mining regardless, not sure if I'm mining to my full potential or not, but I reload my BTC Guild account page and I've gained some even when I'm getting these errors.

Are there any pools that use port 8333? I see bitcoin pool uses 8334...

My software is poclbm + guiminer.

Port forwarding in itself shouldnt stop you connecting as long as you have NAT enabled.

Can you successfully mine with another pool that uses a different port? What miner software are you using?

I did that first and it didn't work, so then I did the DMZ.

I port forwarded 8333 successfully but 8332 won't forward. No clue why.

I wouldnt be putting my PC's IP in the DMZ due to security implications.

Put it back behind the firewall, enable NAT & add the pools port to your forwarding list. Should work fine.

spoke too soon, still getting a bunch of errors. Hmm.

appears to have been the problem. Thanks!

You can keep it running, just slow down the upload rate to allow your miners packet to pass..

yep, I had utorrent running. I'll close it and see what happens. If that's the problem, I'm gonna feel pretty dumb.

Do you have any p2p(torrent or whatever) software running? I've seen this problem often on satured internet connections...

2011-06-25 17:01:56: Listener for "Default": 25/06/2011 17:01:56, warning: job finished, miner is idle
2011-06-25 17:05:47: Listener for "Default": 25/06/2011 17:05:47, warning: job finished, miner is idle
2011-06-25 17:05:48: Listener for "Default": 25/06/2011 17:05:48, Problems communicating with bitcoin RPC
2011-06-25 17:06:34: Listener for "Default": 25/06/2011 17:06:34, Problems communicating with bitcoin RPC
2011-06-25 17:06:37: Listener for "Default": 25/06/2011 17:06:37, warning: job finished, miner is idle
2011-06-25 17:06:40: Listener for "Default": 25/06/2011 17:06:40, Problems communicating with bitcoin RPC
2011-06-25 17:06:46: Listener for "Default": 25/06/2011 17:06:46, Problems communicating with bitcoin RPC
2011-06-25 17:07:29: Listener for "Default": 25/06/2011 17:07:29, warning: job finished, miner is idle
2011-06-25 17:07:29: Listener for "Default": 25/06/2011 17:07:29, Problems communicating with bitcoin RPC
2011-06-25 17:07:34: Listener for "Default": 25/06/2011 17:07:34, Problems communicating with bitcoin RPC
2011-06-25 17:07:40: Listener for "Default": 25/06/2011 17:07:40, Problems communicating with bitcoin RPC
2011-06-25 17:08:58: Listener for "Default": 25/06/2011 17:08:58, warning: job finished, miner is idle
2011-06-25 17:08:58: Listener for "Default": 25/06/2011 17:08:58, Problems communicating with bitcoin RPC
2011-06-25 17:09:31: Listener for "Default": 25/06/2011 17:09:31, Problems communicating with bitcoin RPC
2011-06-25 17:10:53: Listener for "Default": 25/06/2011 17:10:53, warning: job finished, miner is idle
2011-06-25 17:10:54: Listener for "Default": 25/06/2011 17:10:54, Problems communicating with bitcoin RPC
2011-06-25 17:11:00: Listener for "Default": 25/06/2011 17:11:00, Problems communicating with bitcoin RPC
2011-06-25 17:37:38: Listener for "Default": 25/06/2011 17:37:38, warning: job finished, miner is idle
2011-06-25 17:42:06: Listener for "Default": 25/06/2011 17:42:06, warning: job finished, miner is idle

what does this mean? Anyone know how to fix it? I assume it's not BTC Guild's fault, since no one else appears to be having this problem.

I put my computer's ip address in the DMZ zone of my router, so I shouldn't be behind the NAT anymore. Don't know what else to do.