- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveInteral 5000(decimal; was -1)
- HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime 1200000(decimal; was -1)
- Increased the client cache from 100MB to 200MB
Topic: bitcoin core 0.11.2 on windows never gets mor than 8-10 connections (Read 810 times)
January 18, 2016, 03:03:37 PM
In case anyone else can benefit, I have made the following modifications, I'm still syncing:
January 17, 2016, 11:12:08 AM
thanks, if that's true.. ..why is nobody providing blocks? these 8 peers provide nothing for 5-10 minutes at a time or more.
Blocks come at 10 minute intervals on average so that could be the data that you are getting. However you should be seeing data for transactions.#1 connections are low during the initial sync, thats normal.
#2 is your CPU or your disk maxed out? Because if thats the case you might have an answer why you dont get any new blocks. If your machine is busy verifying and writing the blocks it has it can not request more.
January 17, 2016, 11:03:25 AM
thanks, if that's true.. ..why is nobody providing blocks? these 8 peers provide nothing for 5-10 minutes at a time or more.
Blocks come at 10 minute intervals on average so that could be the data that you are getting. However you should be seeing data for transactions.
January 17, 2016, 11:02:44 AM
thanks, if that's true.. ..why is nobody providing blocks? these 8 peers provide nothing for 5-10 minutes at a time or more.
Blocks come at 10 minute intervals on average so that could be the data that you are getting. However you should be seeing data for transactions.#1 connections are low during the initial sync, thats normal.
#2 is your CPU or your disk maxed out? Because if thats the case you might have an answer why you dont get any new blocks. If your machine is busy verifying and writing the blocks it has it can not request more.
January 17, 2016, 10:58:10 AM
thanks, if that's true.. ..why is nobody providing blocks? these 8 peers provide nothing for 5-10 minutes at a time or more.
Blocks come at 10 minute intervals on average so that could be the data that you are getting. However you should be seeing data for transactions. January 17, 2016, 10:55:50 AM
thanks, if that's true.. ..why is nobody providing blocks? these 8 peers provide nothing for 5-10 minutes at a time or more.
Blocks come at 10 minute intervals on average so that could be the data that you are getting. However you should be seeing data for transactions. January 17, 2016, 10:52:09 AM
thanks, if that's true.. ..why is nobody providing blocks? these 8 peers provide nothing for 5-10 minutes at a time or more. i feel like i'm trying to catch up and i'm stuck with bad neighbors 
January 17, 2016, 10:38:54 AM
Bitcoin Core by default only allows 8 outgoing connections and 255 connections total. You already have 8 outgoing, so the rest will be incoming. Incoming connections only happen if others want to connect to you. In order to be someone that they connect to, you generally have to be for several days so that the DNS seeds will get your IP address and so that people can know about you and connect to you.
Something might also be wrong with your firewall that may be limiting it to only 10 connections.
Something might also be wrong with your firewall that may be limiting it to only 10 connections.
January 17, 2016, 10:22:52 AM
i did an experiment and completely disabled the windows firewall.. ..and bitnodes.21.co says it can connect. i'll leave it this way for a while and see what happens. [edit] that must have been random, it doesn't connect any more.
January 17, 2016, 09:53:42 AM
I've read a lot of posts on this subject, so I feel a bit naive asking again. A week ago I had to start from scratch after restoring my wallet. I let the client run overnight and sometimes all day. The client only receives (in the debug window) ~ 2GB overnight. I never observe more than 8 outgoing and 2 incoming connections. Here's what I think is relevant that everyone asks about:
(while typing this dazzlepod.com is trying to connect to bitcoin-qt and also getting CLOSE_WAIT as do some others)
At this rate, I won't catch up for ~ 2 weeks, if ever.
[edit] i'm watching tcpview while i posting.. ..some connections do establish. some go to SYN_SENT/LAST_ACK, i'm assuming most of this is all normal. I restarted the client just before posting this, and it seems that it's doing better in the last 15 minutes than it was some previous hours. however, i still don't understand i can't establish more than ~2 incoming and 8 outgoing.
- windows firewall showing bitcoin-qt allowed
- netgear router showing UPNP is forwarding TCP port 8333
- http://www.yougetsignal.com/tools/open-ports/ says that my port 8333 is open
- https://bitnodes.21.co/ however says it cannot connect, and I can see in tcpview that it connection does come in to bitcoin-qt and immediate goes to CLOSE_WAIT
(while typing this dazzlepod.com is trying to connect to bitcoin-qt and also getting CLOSE_WAIT as do some others)
At this rate, I won't catch up for ~ 2 weeks, if ever.
[edit] i'm watching tcpview while i posting.. ..some connections do establish. some go to SYN_SENT/LAST_ACK, i'm assuming most of this is all normal. I restarted the client just before posting this, and it seems that it's doing better in the last 15 minutes than it was some previous hours. however, i still don't understand i can't establish more than ~2 incoming and 8 outgoing.
Jump to: