Someone please shoot me in the face (BITCOIN-QT connection problems)

[Prufrock3]

I'm so frustrated.  I tried Bitcoin-qt yesterday and created my first wallet, but it cannot connect via network to download blocks even when the client is reporting that I have "8 active connections".  I've successfully bootstrapped up to 16 weeks old data.  I also wanted to try mining just to experiment with it and mining pools, but my GUIMiner can't connect to receive shares either.  I'm assuming it's the same problem with both.

I've tried port forwarding, I've put the computer on the DMZ.  I'm not running anti-virus and windows firewall is disabled (I'm using Windows 7 BTW).  Based on some help I found through google, I tried to telnet to a bitcoin server via port 8333 and it worked fine, as well as some online utilities that check ports also report back that port 8333 is open.  I'm not using a proxy.  I've made sure that proxy settings are turned off in the bitcoin-qt client.  I've tried both enabling and disabling UPnP on the client, and ensured that it's enabled on my router.

I run an Abyss Web Server on this box, and Plex for sharing movies, and Google Play Music to share my MP3's to my car radio.  I've never had any issues communicating in or out from the internet with this machine.  But I've disabled all those programs just to make sure they aren't interfering in some way.  Still no love from my bitcoin-qt or GUIMiner clients.  I just don't get it.

What am I missing?  I've exhausted all the help I could find on other forums.

Thanks,
Mike

[Omnicron]

have you set up your bitcoin.conf file?

[Prufrock3]

Uh oh.  I guess not.  I don't know what I'm supposed to do with that file.

[Prufrock3]

Ok, I found a bitcoin.conf example file online, but it seems like 90% of the settings in it are already established and saved in the GUI of the Bitcoiin-qt client.  Are you sure this file is required for the latest Bitcoin-qt version?

As for GUIMiner, it's Readme file says that bitcoin.conf is only required for solo mining, but I'm trying to mine in a pool with EclipseMC, so it doesn't apply.

Mike

[Gator-hex]

You need something on the command line to import an old wallet/database I think.

In command prompt type something like: bitcoinqt.exe /? to bring up a list of the command options.

It's some like -update or -upgrade or -import or some such thing.

The you type Bitcoinqt.exe -whatEverItIs

[Prufrock3]

Ok, so I created a bitcoin.conf file and placed in C:\Users\Mike\AppData\Roaming\Bitcoin\ and restarted bitcoin-qt.  Even though there were settings changes in the bitcoin.conf file compared to what I had already set in the gui, those changes weren't set when I restarted the client.  For example, the .conf file said minimize to system tray false, but the gui still said true which I had already set there.  So I don't think bitcoin-qt is even looking for a conf file.  Maybe that's from an old version, or something only bitcoind uses?  Anyway, it didn't help.  I still have 8 active connections, but "No block source available".

As for the other potential solution, running bitcoin-qt.exe /? at the Windows command line just tries to launch the bitcoin-qt client again.  it didn't provide a help screen.  In the client, I opened the console and typed "help" but there are no "upgrade" or "update" commands like what you suggested, or anything that even sounds like it might be the same.  Also, I was skeptical anyway because I'm not trying to import a wallet or a database from another client.  This is a brand new install, brand new wallet, and I am a first time bitcoin user.  Or at least, I would like to be a first time bitcoin user.

Thanks anyway for trying.  Any more ideas?

This is what my logs look like if it helps:

Misbehaving: 61.18.77.182:8333 (59 -> 60)
ProcessMessage(inv, 73 bytes) FAILED
Misbehaving: 218.76.75.36:8333 (37 -> 38)
ProcessMessage(inv, 37 bytes) FAILED
Misbehaving: 82.224.110.190:8333 (39 -> 40)
ProcessMessage(inv, 37 bytes) FAILED
Misbehaving: 61.18.77.182:8333 (60 -> 61)
ProcessMessage(inv, 37 bytes) FAILED
Misbehaving: 24.212.184.180:8333 (98 -> 99)
ProcessMessage(addr, 31 bytes) FAILED
Misbehaving: 24.212.184.180:8333 (99 -> 100) DISCONNECTING
disconnecting node 24.212.184.180:8333
ProcessMessage(inv, 217 bytes) FAILED
trying connection 69.164.206.88:8333 lastseen=81.1hrs
Misbehaving: 218.76.75.36:8333 (38 -> 39)
ProcessMessage(inv, 37 bytes) FAILED
Misbehaving: 61.18.77.182:8333 (61 -> 62)
ProcessMessage(inv, 37 bytes) FAILED

Mike