max 8 connections to Bitcoin Network

[proline1]

With the last core update to Bitcoins wallet (v0.10.2), I can no longer get more than 8 connections to the network.  Most of the time I get 0-5, which with the size of the ledger, will take months to sync.  Bitcoin was given rights to pass through the Windows 7 firewall when the update was installed, so I do not understand why it is unable to connect to more than 8 nodes max.

I am running other cypto currencies wallets (Litecon / Dogecoin) with no issues connecting to the max nodes for sync, even following their software updates.

I've tried -maxconnections=##, but it appears that it is not a command line option with Bitcoin Core version v0.10.2 (64-bit).

I'm running Windows 7 64bit (fully updated), Bitcoin Core version v0.10.2 (64-bit), though 2wire Gateway DSL modem.  No Virus protection when running wallets sync.

[Blazr]

You need to be accepting incoming connections in order to get more than 8. Make sure your node is listening for incoming connections.

[proline1]

You need to be accepting incoming connections in order to get more than 8. Make sure your node is listening for incoming connections.

Is that found in the Windows Firewall settings?


In the wallet Settings, Options, Network UPnP and Allow incoming connections are both checked.

[achow101]

You need to be accepting incoming connections in order to get more than 8. Make sure your node is listening for incoming connections.

Is that found in the Windows Firewall settings?


In the wallet Settings, Options, Network UPnP and Allow incoming connections are both checked.

Check your firewall settings to make sure that bitcoin-qt.exe is allowed to have incoming connections as well as tcp port 8333. Also check your router's firewall to make sure that it isn't blocking tcp port 8333.

[shorena]

If you use DHCP make sure the port 8333 is forwarded to the correct machine on the router/modem/firewall box.

[cr1776]

Also, this is not the current version.  :-)

With the last core update to Bitcoins wallet (v0.10.2), I can no longer get more than 8 connections to the network.  Most of the time I get 0-5, which with the size of the ledger, will take months to sync.  Bitcoin was given rights to pass through the Windows 7 firewall when the update was installed, so I do not understand why it is unable to connect to more than 8 nodes max.

I am running other cypto currencies wallets (Litecon / Dogecoin) with no issues connecting to the max nodes for sync, even following their software updates.

I've tried -maxconnections=##, but it appears that it is not a command line option with Bitcoin Core version v0.10.2 (64-bit).

I'm running Windows 7 64bit (fully updated), Bitcoin Core version v0.10.2 (64-bit), though 2wire Gateway DSL modem.  No Virus protection when running wallets sync.

[vm1990]

check to see the ports open. type into google "canyouserme" and click the top link should take you to a good port testing site

[proline1]

check to see the ports open. type into google "canyouserme" and click the top link should take you to a good port testing site

I do not have a static IP.  sigh

[tsoPANos]

check to see the ports open. type into google "canyouserme" and click the top link should take you to a good port testing site

I do not have a static IP.  sigh

If you want to port fordward, you need a static ip afaik.
The modem/router needs to know on what local ip it should forward a particular port.
DHCP assigns random ip addresses, so you will need to set a static one.

[jonnybravo0311]

Virtually every router allows you to assign IP addresses to machines within the network.  Just assign a static IP address to the machine running the BTC node, then forward the traffic over port 8333 to that machine.

By the way... you might want to update to 0.11 as that's the latest release (not the 0.10.2 you quoted).

[hexafraction]

Virtually every router allows you to assign IP addresses to machines within the network.  Just assign a static IP address to the machine running the BTC node, then forward the traffic over port 8333 to that machine.

By the way... you might want to update to 0.11 as that's the latest release (not the 0.10.2 you quoted).

It's not dependent on the router. You need to configure it on the computer itself. You also do NOT need a static external IP. I'm assuming you have a router and aren't just plugging your computer straight into a modem that doesn't do any NAT.

Here are the steps I would take. Note that I'm working from memory as I haven't used Windows in a while.

1. Press windows key+R for run dialog. Run ncpa.cpl (to open the network connections control panel page).
2. Right-click the wired or wireless interface you're using to connect to the internet. Click status. Head to the second tab and check that the address is of the form 192.168.X.Y. If this is not the case, these steps probably won't work. Record that address on a piece of paper.
3. Close that dialog. Right-click the interface again, properties. Select Internet protocol Version 4, and choose to edit its configuration. Give it the following settings: IP 192.168.X.200 (200 is a fairly high number so no risk of faulty routers causing weird DHCP conflicts). X must be the same as in step 2. Subnet mask is ALMOST always 255.255.255.0. Gateway is 192.168.X.1 (X must be the same as step 2) DNS servers can be 8.8.8.8 and 8.8.4.4 (Google public DNS).
4. Go to your router's page, and forward port 8333 to 192.168.X.200. Depends on the make and model of your router.

[schnuber]

I have the same problem actually, although I am running bitcoinXT client.
I have forwarded the port to the maschin's IP, when I go to canyouseeme.org it says port is open.
In the windows firewall I have enabled inbound and outbound connections for that program.
Still I can see only 8 connections in the client.

[tsoPANos]

I have the same problem actually, although I am running bitcoinXT client.
I have forwarded the port to the maschin's IP, when I go to canyouseeme.org it says port is open.
In the windows firewall I have enabled inbound and outbound connections for that program.
Still I can see only 8 connections in the client.

You will need to forward port 8333 and assign a static local ip to your machine.
Don't use XT it is harmful to bitcoin btw.

[jonnybravo0311]

Virtually every router allows you to assign IP addresses to machines within the network.  Just assign a static IP address to the machine running the BTC node, then forward the traffic over port 8333 to that machine.

By the way... you might want to update to 0.11 as that's the latest release (not the 0.10.2 you quoted).

It's not dependent on the router. You need to configure it on the computer itself. You also do NOT need a static external IP. I'm assuming you have a router and aren't just plugging your computer straight into a modem that doesn't do any NAT.

Here are the steps I would take. Note that I'm working from memory as I haven't used Windows in a while.

1. Press windows key+R for run dialog. Run ncpa.cpl (to open the network connections control panel page).
2. Right-click the wired or wireless interface you're using to connect to the internet. Click status. Head to the second tab and check that the address is of the form 192.168.X.Y. If this is not the case, these steps probably won't work. Record that address on a piece of paper.
3. Close that dialog. Right-click the interface again, properties. Select Internet protocol Version 4, and choose to edit its configuration. Give it the following settings: IP 192.168.X.200 (200 is a fairly high number so no risk of faulty routers causing weird DHCP conflicts). X must be the same as in step 2. Subnet mask is ALMOST always 255.255.255.0. Gateway is 192.168.X.1 (X must be the same as step 2) DNS servers can be 8.8.8.8 and 8.8.4.4 (Google public DNS).
4. Go to your router's page, and forward port 8333 to 192.168.X.200. Depends on the make and model of your router.

No, it's not dependent upon the router.  You can certainly tell your machine to give itself a static IP address.  However, that won't prevent the DHCP server from attempting to assign that same IP address to another machine on the network.  You try to get around that by giving a relatively high value for the last bit.  My solution avoids the problem altogether by telling the DHCP server (i.e. your router) to always assign IP of x.x.x.x to the machine.  No conflicts.

In any case, the point is that the machine needs a static IP address in your home network so that you can properly forward traffic from your router to that machine.

[Mikestang]

You can also leave it as dynamic dns and set the renewal time to something really long, then your computer will basically have a static local ip.  Regardless, unless you have hundreds of devices on your local network when your local ip lease is up it usually renews with the same address.

So as has been mentioned, make sure the appropriate ports are open in your firewall and that those ports are forwarded to the local ip of the machine running core and you'll start seeing >8 connections immediately.

[hexafraction]

No, it's not dependent upon the router.  You can certainly tell your machine to give itself a static IP address.  However, that won't prevent the DHCP server from attempting to assign that same IP address to another machine on the network.  You try to get around that by giving a relatively high value for the last bit.  My solution avoids the problem altogether by telling the DHCP server (i.e. your router) to always assign IP of x.x.x.x to the machine.  No conflicts.

In any case, the point is that the machine needs a static IP address in your home network so that you can properly forward traffic from your router to that machine.

Yes, I address both of those things. 200 is fairly high in the range of 2-254 that is typically valid for a client device on such a network. However, setting the DHCP server to give a static address to a given machine has been flaky for me across multiple routers.

[schnuber]

I have the same problem actually, although I am running bitcoinXT client.
I have forwarded the port to the maschin's IP, when I go to canyouseeme.org it says port is open.
In the windows firewall I have enabled inbound and outbound connections for that program.
Still I can see only 8 connections in the client.

You will need to forward port 8333 and assign a static local ip to your machine.

No, I don't necessarily have to assign a static IP just for the sake of trying it out. I just have to make sure, that I forward the port to the currently assigned IP of my device.
I am aware, that the next time it could be different. It actually works now.

Don't use XT it is harmful to bitcoin btw.

I know very well what I am doing, believe me. Unfortunately its you that is harmful to bitcoin.

[Liquid71]

I have the same problem actually, although I am running bitcoinXT client.
I have forwarded the port to the maschin's IP, when I go to canyouseeme.org it says port is open.
In the windows firewall I have enabled inbound and outbound connections for that program.
Still I can see only 8 connections in the client.

You will need to forward port 8333 and assign a static local ip to your machine.

No, I don't necessarily have to assign a static IP just for the sake of trying it out. I just have to make sure, that I forward the port to the currently assigned IP of my device.
I am aware, that the next time it could be different. It actually works now.

Don't use XT it is harmful to bitcoin btw.

I know very well what I am doing, believe me. Unfortunately its you that is harmful to bitcoin.

He just helped you and you insult him    Typical XT troll, all ego no substance

[proline1]

Still only have 8 connections max.  The core has been running since I first posted In Mid Aug, and it still have more than 1.5 years to go.

- I have a 2wire DSL modem

- Currently computer is connected directly to 2wire

- Now running Core ver 11.0 (I've upgraded previously a couple times and nothing changed)

- Mapping UPnP and Allow incoming connects selected in Core Network settings

- ISP does NOT provide static IP

- I've tried adding a router inline and nothing changed (tried dedicated port modifications)

- Litecoin Core works fine, updates in minutes.  I'm beginning to think that LTC Core been coded properly and BTC Core has not..

[Mikestang]

I'm beginning to think that LTC Core been coded properly and BTC Core has not..

If that were the case then there would be thousands of other people having problems, too, but there's not.

The one thing missing from your list is port forwarding, which is what you have to do to get more than 8 connections as has been stated many times in this thread already.  Did you forward the port on your router to the computer running core?