Bitcoin Core 0.9.3 drops incoming connections only - Windows

2112

legendary

Activity: 2128

Merit: 1073

Quote from: Itincalotson on January 16, 2015, 01:51:53 AM

Investigating a little I found that the IP address changes are due to qBitTorrent. It overuses the net so much that my router is unable to ping the PPPoE connection and it thinks that it has gone down and terminates it. Then my network goes down too until router reconnects the PPPoE connection giving me another new freshly IP address Grin

My router uses OpenWrt. I have to check if I can fix this. If not, I will try Bitcoin Core 0.10 version or DDNS.

It reads like you misdiagnosed this or the OpenWRT is the dumbest PPPoE router I have ever seen. It really terminates the PPPoE session when the PPPoE frames are coming in at the connection saturation rate? This is unbelievably dumb, put still possible. Can you just configure this "ping the PPPoE connection" out?

Quote from: Itincalotson on January 16, 2015, 01:51:53 AM

I've read that UPnP is vulnerable but I don't know what do you mean. Do you want me to enable it on the router?

Get the proper version of router firmware without vulnerabilities. Enable UPnP and poll it using upnpc-static from a .cmd script with a task scheduler. When there's an IP address change cleanly shutdown and restart bitcoind.

Quote from: Itincalotson on January 16, 2015, 01:51:53 AM

I usually use my computer for 3 hours and then turn all off, router too. I turn all them on again in one hour, and then 3 hours more using it. So will this behaviour spam the Bitcoin network?

It sounds like obsessive-compulsive behavior. DSL is an "always on" technology, you are supposed to keep your DSL *-box continuously on. Your ISP uses http://en.wikipedia.org/wiki/Dynamic_spectrum_management to continuously optimize your connection parameters. Probably any of your neighbors that use VoIP or IPTV and keep their *-box on at all times have much better Internet connection as a side effect of not being obsessive or stuck in behavior from the POTS dial-up modem times. All DSL ISPs I have ever seen always recommend to keep their connection on for around 10 days after starting the service to let the DSM calibrate. But I've also heard of people who are annoyed and distracted by the blinking lights of their *-box.

Or maybe you have a DSL modem that is separate from the router and independently powered?

Quote from: Itincalotson on January 16, 2015, 01:51:53 AM

If yes, I could use DDNS, like DuckDNS, so the Bitcoin network will not have to update the IP address and I will not spam its network. What do you think?

Bitcoin P2P network only deals with numerical addresses: 4 bytes for IPv4 and 16 for IPv6. How you think you are going to push a string DDNS name through the Bitcoin protocol?

Quote from: Itincalotson on January 16, 2015, 01:51:53 AM

I think polling it every hour is reasonable, isn't it?

Bittorrent clients poll UPnP every few minutes, typically 3, most I've seen was 15. In fact many popular UPnP gateways have time-to-live of 30 minutes, meaning that if they don't see the UPnP packet from a device for 30 minutes they consider it switched off/disabled.

If your question was about how often you can poll DDNS provider this is usually proprietary competitive information related to how they mitigate denial-of-service attacks. You are unlikely to get a straight and simple answer. DoS attacks from misconfigured routers is their everyday occurrence.

Itincalotson

newbie

Activity: 5

Merit: 0

Good morning!

Hello shorena

Quote from: shorena on January 14, 2015, 01:19:39 PM

You could try 0.10.0rc3 and see if it helps. Would be perfect if someone with the problem would test the version thats fixing it.

https://bitcoin.org/bin/0.10.0/test/

Investigating a little I found that the IP address changes are due to qBitTorrent. It overuses the net so much that my router is unable to ping the PPPoE connection and it thinks that it has gone down and terminates it. Then my network goes down too until router reconnects the PPPoE connection giving me another new freshly IP address Grin

My router uses OpenWrt. I have to check if I can fix this. If not, I will try Bitcoin Core 0.10 version or DDNS.

Hello 2112

Quote from: 2112 on January 14, 2015, 03:31:06 PM

The better choice is to get the upnpc-static program from the UPnP library that Bitcoin is using. Use that program to rapidly and continuously query your outside IP address from the UPnP gateway. Once you detect a change of IP addresses then you could stop and start the bitcoin daemon.

I've read that UPnP is vulnerable but I don't know what do you mean. Do you want me to enable it on the router?

Quote from: 2112 on January 14, 2015, 03:31:06 PM

But as gxmawell said your wanna-be-full-node isn't really helping much the overall Bitcoin network. You'll just end up spamming the network with your IP address changes. If all the DSL users with daily changeable IP would start doing the above procedure I think the overall availability and integrity of the Bitcoin P2P network will go down.

The whole process of the peer address distribution in the Bitcoin protocol would have to be significantly redesigned: shorter timeouts, lower time-to-lives, possibly adding a cryptographically signed IP address revocation message, etc.

From my observation of the behavior of Bittorrent protocol the overall swarm quality also suffers. Depending on the clients used the really-dynamic-IP peers sometimes constitute between 10 and 100 times the true active peers. With Bittorrent there are multitude of disjoint swarms whereas in Bitcoin there is just one global swarm.

I usually use my computer for 3 hours and then turn all off, router too. I turn all them on again in one hour, and then 3 hours more using it. So will this behaviour spam the Bitcoin network?

If yes, I could use DDNS, like DuckDNS, so the Bitcoin network will not have to update the IP address and I will not spam its network. What do you think?

Quote from: 2112 on January 14, 2015, 03:31:06 PM

Many DDNS providers will kick you out for abuse if you poll them too frequently. Or forcibly upgrade you to an expensive business plan.

I think polling it every hour is reasonable, isn't it?

However, the key here is to fix the OpenWrt and qBitTorrent problem.

Thanks!

2112

legendary

Activity: 2128

Merit: 1073

Quote from: Itincalotson on January 14, 2015, 01:09:09 PM

So the only solution that I imagine is to use a Dynamic DNS Service with Bitcoin Core. It will work perfectly, but I don't think it is the ideal solution as I explained before.

Many DDNS providers will kick you out for abuse if you poll them too frequently. Or forcibly upgrade you to an expensive business plan.

The better choice is to get the upnpc-static program from the UPnP library that Bitcoin is using. Use that program to rapidly and continuously query your outside IP address from the UPnP gateway. Once you detect a change of IP addresses then you could stop and start the bitcoin daemon.

But as gxmawell said your wanna-be-full-node isn't really helping much the overall Bitcoin network. You'll just end up spamming the network with your IP address changes. If all the DSL users with daily changeable IP would start doing the above procedure I think the overall availability and integrity of the Bitcoin P2P network will go down.

The whole process of the peer address distribution in the Bitcoin protocol would have to be significantly redesigned: shorter timeouts, lower time-to-lives, possibly adding a cryptographically signed IP address revocation message, etc.

From my observation of the behavior of Bittorrent protocol the overall swarm quality also suffers. Depending on the clients used the really-dynamic-IP peers sometimes constitute between 10 and 100 times the true active peers. With Bittorrent there are multitude of disjoint swarms whereas in Bitcoin there is just one global swarm.

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: Itincalotson on January 14, 2015, 01:15:14 PM

Happy to know that on version 0.10 maybe this will be fixed Cheesy

You could try 0.10.0rc3 and see if it helps. Would be perfect if someone with the problem would test the version thats fixing it.

https://bitcoin.org/bin/0.10.0/test/

Itincalotson

newbie

Activity: 5

Merit: 0

Happy to know that on version 0.10 maybe this will be fixed Cheesy

Itincalotson

newbie

Activity: 5

Merit: 0

Hello again!

Effectively, as member 2112 said, IP address is being changed when my network goes down.

When this happens, Bitcoin Core is not programmed to update itself to use the new IP address, making incoming connections not reachable. I can not believe that this easy feature is not being added to the code. We can not per-suppose that the external IP address will keep constant until we shutdown Bitcoin Core. I think it has to look for IP changes.

So the only solution that I imagine is to use a Dynamic DNS Service with Bitcoin Core. It will work perfectly, but I don't think it is the ideal solution as I explained before.

Greetings and thanks! Wink

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: gmaxwell on January 14, 2015, 01:00:28 PM

Quote from: shorena on January 14, 2015, 12:54:26 PM

AFAIK this has been discussed on github and no one is working on a solution.

Not so.

If this is what it appears to be, that Bitcoin never learns the new IP after it changes:
It's more or less solved, or at least more or less as much as it's ever likely to be, by the new discovery procedure in 0.10.

Of course, if your IP is changing you're somewhat less useful to the network because it takes time for other nodes to discover your IP before they can reach you.

Thanks for the update. Only had an old discussion in mind where it appeared as if no one was willing to invest time into a solution. Glad I am wrong.

gmaxwell

staff

Activity: 4284

Merit: 8808

Quote from: shorena on January 14, 2015, 12:54:26 PM

AFAIK this has been discussed on github and no one is working on a solution.

Not so.

If this is what it appears to be, that Bitcoin never learns the new IP after it changes:
It's more or less solved, or at least more or less as much as it's ever likely to be, by the new discovery procedure in 0.10.

Of course, if your IP is changing you're somewhat less useful to the network because it takes time for other nodes to discover your IP before they can reach you.

If UPNP is in use somewhat more could be done, but the result still would take a while to get back many connections.

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: Itincalotson on January 14, 2015, 12:30:34 PM

-snip-
Bitcoin Core loses incoming connections in around 30 minutes from when I start it and it takes a considerable amount of time to load the blockchain. So it doesn't seem a nice option to use the task scheduler.

You can improve the loading time with settings (in the bitcoin.conf[1]) like:

Code:

# How many blocks to check at startup (default: 288, 0 = all)
checkblocks=144

# How thorough the block verification is (0-4, default: 3)
checklevel=2

Quote from: Itincalotson on January 14, 2015, 12:30:34 PM

I always try to solve things by myself but this time I think that Bitcoin Core has to be able to recover from a bad connection, IP address change or other things related to network to make things easy. Bitcoin needs full nodes and I want to run one, but I can't with this problem :S

If this is related to changing IP-addresses there will probably no solution. AFAIK this has been discussed on github and no one is working on a solution.

Quote from: Itincalotson on January 14, 2015, 12:30:34 PM

I've searched but I have not find anything related to this problem, maybe I've searched wrong, maybe it is happening only to me? I don't think so Tongue

So... Any other suggestion to fix this? Maybe request this feature to developers?

Thanks in advance Wink

[1] https://en.bitcoin.it/wiki/Running_Bitcoin#Sample_Bitcoin.conf

Itincalotson

newbie

Activity: 5

Merit: 0

Hi, thanks for your quick reply!

Yes, I have a DSL connection using PPPoE but I'm not sure if my ISP is enforcing an IP address change. I think that when my network goes down for a little, the IP address is not changed. But I'll check.

Bitcoin Core loses incoming connections in around 30 minutes from when I start it and it takes a considerable amount of time to load the blockchain. So it doesn't seem a nice option to use the task scheduler.

I always try to solve things by myself but this time I think that Bitcoin Core has to be able to recover from a bad connection, IP address change or other things related to network to make things easy. Bitcoin needs full nodes and I want to run one, but I can't with this problem :S

I've searched but I have not find anything related to this problem, maybe I've searched wrong, maybe it is happening only to me? I don't think so Tongue

So... Any other suggestion to fix this? Maybe request this feature to developers?

Thanks in advance Wink

2112

legendary

Activity: 2128

Merit: 1073

Quote from: Itincalotson on January 14, 2015, 11:06:46 AM

However, sometimes my network goes down for about 1 minute

Anybody knows why is this happening?

Let me guess: you are on a DSL connection with PPPoE or PPPoA and your ISP is enforcing the periodic IP address change.

If the forced IP address change periods are reasonably accurate (e.g. 24 hours) you could stop and start your bitcoind using the task scheduler. I don't think bitcoind is capable to deal with the outside IP address change, unlike pretty much all bittorrent clients.

Itincalotson

newbie

Activity: 5

Merit: 0

Hello.

First, I want to thank you for this forum and greet all the members, Wink

I've registered because I'm having trouble with incoming connections to Bitcoin Core 0.9.3 for Windows.

I've already configured the port 8333 on my router and it works well because when I start Bitcoin Core, it is able to accept incoming connections and I get a max of 15, 8 outgoing and 7 incoming.

However, sometimes my network goes down for about 1 minute and uploading speed is down to 5kb/s when it is 150kb/s normally. After that, I don't know why, but it recovers Grin

. So then all the programs keep working well, even qBitTorrent, which I have its port openned too. But Bitcoin Core recovers only its 8 outgoing connections, but no its incoming ones, 0 incoming connections.

Here is the debug file:

Code:


Requesting initialize
Running AppInit2 in thread
2015-01-14 14:50:53

2015-01-14 14:50:53 Bitcoin version v0.9.3.0-g40d2041-beta (Mon, 22 Sep 2014 16:42:15  0200)
2015-01-14 14:50:53 Using OpenSSL version OpenSSL 1.0.1i 6 Aug 2014
2015-01-14 14:50:53 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2015-01-14 14:50:53 Using at most 125 connections (2048 file descriptors available)
2015-01-14 14:50:53 Using 2 threads for script verification
2015-01-14 14:50:53 Using wallet wallet.dat
2015-01-14 14:50:53 init message: Verifying wallet...
2015-01-14 14:50:53 Bound to [::]:8333
2015-01-14 14:50:53 Bound to 0.0.0.0:8333
2015-01-14 14:50:53 init message: Loading block index...
2015-01-14 14:50:54 Opened LevelDB successfully
2015-01-14 14:51:15 LoadBlockIndexDB(): last block file = 218
2015-01-14 14:51:15 LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=109, size=47459203, heights=338782...338890, time=2015-01-13...2015-01-14)
2015-01-14 14:51:15 LoadBlockIndexDB(): transaction index disabled
2015-01-14 14:51:15 LoadBlockIndexDB(): hashBestChain=00000000000000000e7169447d770c552857f76270d408c74049540f67251ea5 height=338890 date=2015-01-14 08:35:22 progress=0.999430
2015-01-14 14:51:15 init message: Verifying blocks...
2015-01-14 14:51:15 Verifying last 288 blocks at level 3
2015-01-14 14:54:17 No coin database inconsistencies in last 191 blocks (149246 transactions)
2015-01-14 14:54:18  block index          204859ms
2015-01-14 14:54:18 init message: Loading wallet...
2015-01-14 14:54:19 nFileVersion = 90300
2015-01-14 14:54:19 Keys: 106 plaintext, 0 encrypted, 5 w/ metadata, 106 total
2015-01-14 14:54:19  wallet                  592ms
2015-01-14 14:54:19 init message: Loading addresses...
2015-01-14 14:54:19 Loaded 13256 addresses from peers.dat  64ms
2015-01-14 14:54:21 mapBlockIndex.size() = 338934
2015-01-14 14:54:21 nBestHeight = 338890
2015-01-14 14:54:21 setKeyPool.size() = 101
2015-01-14 14:54:21 mapWallet.size() = 0
2015-01-14 14:54:21 mapAddressBook.size() = 5
2015-01-14 14:54:21 ext-ip thread start
2015-01-14 14:54:21 init message: Done loading
2015-01-14 14:54:21 msghand thread start
2015-01-14 14:54:21 addcon thread start
2015-01-14 14:54:21 Initialization result: 1
2015-01-14 14:54:21 opencon thread start
2015-01-14 14:54:21 dumpaddr thread start
2015-01-14 14:54:21 dnsseed thread start
2015-01-14 14:54:21 net thread start
2015-01-14 14:54:23 GetMyExternalIP() received [95.23.19.199] 95.23.19.199:0
2015-01-14 14:54:23 GetMyExternalIP() returned 95.23.19.199
2015-01-14 14:54:23 AddLocal(95.23.19.199:8333,4)
2015-01-14 14:54:23 ext-ip thread exit
2015-01-14 14:54:26 receive version message: /Satoshi:0.10.0/: version 70002, blocks=338928, us=95.23.19.199:50586, them=[2001:0:9d38:6abd:ad:26ed:6712:aa96]:8333, peer=152.237.85.105:8333
2015-01-14 14:54:26 Added time data, samples 2, offset -2 ( 0 minutes)
2015-01-14 14:54:27 receive version message: /Satoshi:0.9.1/: version 70002, blocks=338928, us=95.23.19.199:50606, them=203.69.212.61:8333, peer=203.69.212.61:8333
2015-01-14 14:54:27 Added time data, samples 3, offset  1 ( 0 minutes)
2015-01-14 14:54:28 receive version message: /Satoshi:0.9.3/: version 70002, blocks=338928, us=95.23.19.199:50615, them=135.23.178.163:8333, peer=135.23.178.163:8333
2015-01-14 14:54:28 Added time data, samples 4, offset -7 ( 0 minutes)
2015-01-14 14:54:32 P2P peers available. Skipped DNS seeding.
2015-01-14 14:54:32 dnsseed thread exit
2015-01-14 14:54:41 receive version message: /mining.bitcoinaffiliatenetwork.com west2:0.10.0/: version 70002, blocks=338928, us=95.23.19.199:50673, them=184.169.155.66:8333, peer=184.169.155.66:8333
2015-01-14 14:54:41 Added time data, samples 5, offset  1 ( 0 minutes)
2015-01-14 14:54:41 nTimeOffset =  0  ( 0 minutes)
2015-01-14 14:54:52 receive version message: /Satoshi:0.9.3/: version 70002, blocks=338928, us=95.23.19.199:50742, them=188.166.35.57:8333, peer=188.166.35.57:8333
2015-01-14 14:54:52 Added time data, samples 6, offset -1 ( 0 minutes)
2015-01-14 14:54:58 receive version message: /Satoshi:0.9.3/: version 70002, blocks=204662, us=95.23.19.199:50738, them=84.113.93.4:8333, peer=84.113.93.4:8333
2015-01-14 14:54:58 Added time data, samples 7, offset -2 ( 0 minutes)
2015-01-14 14:54:58 nTimeOffset = -1  ( 0 minutes)
2015-01-14 14:55:12 UpdateTip: new best=00000000000000001442e5b3a4615423c80c037e8c8275d4289939915a321e36  height=338891  log2_work=82.001948  tx=56702635  date=2015-01-14 09:20:47 progress=0.999493
2015-01-14 14:55:12 ProcessBlock: ACCEPTED
2015-01-14 14:55:13 receive version message: /Satoshi:0.8.5/: version 70001, blocks=338928, us=95.23.19.199:50766, them=104.207.128.182:8333, peer=104.207.128.182:8333
2015-01-14 14:55:13 Added time data, samples 8, offset -16 ( 0 minutes)
2015-01-14 14:55:13 UpdateTip: new best=00000000000000000776306128a8ee3e6a070294577607611af4d2dec8ceac6c  height=338892  log2_work=82.002004  tx=56702723  date=2015-01-14 09:23:13 progress=0.999497
2015-01-14 14:55:13 ProcessBlock: ACCEPTED
2015-01-14 14:55:13 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=312848, us=95.23.19.199:8333, them=176.9.46.6:8333, peer=176.9.46.6:38557
2015-01-14 14:55:13 Added time data, samples 9, offset -1 ( 0 minutes)
2015-01-14 14:55:13 nTimeOffset = -1  ( 0 minutes)
2015-01-14 14:55:14 receive version message: /bcoinx:1.7.0/: version 70002, blocks=0, us=0.0.0.0:0, them=0.0.0.0:0, peer=193.248.35.191:51690
2015-01-14 14:55:14 Added time data, samples 10, offset -1 ( 0 minutes)
2015-01-14 14:55:15 receive version message: /Satoshi:0.9.3/: version 70002, blocks=195361, us=95.23.19.199:50772, them=188.186.65.97:8333, peer=188.186.65.97:8333
2015-01-14 14:55:15 Added time data, samples 11, offset -3 ( 0 minutes)
2015-01-14 14:55:15 nTimeOffset = -1  ( 0 minutes)
2015-01-14 14:55:31 receive version message: /Satoshi:0.9.99/: version 70002, blocks=283676, us=95.23.19.199:8333, them=129.13.252.36:8333, peer=129.13.252.36:47731
2015-01-14 14:55:31 Added time data, samples 12, offset -38 ( 0 minutes)
2015-01-14 14:55:40 UpdateTip: new best=00000000000000000c63ba7ad063e8852658a9bb8de61c7c53400d92335f333d  height=338893  log2_work=82.002061  tx=56703720  date=2015-01-14 09:27:55 progress=0.999503
2015-01-14 14:55:40 ProcessBlock: ACCEPTED
2015-01-14 14:56:23 UpdateTip: new best=00000000000000000ff6f346bea61d1c87e455e2dd4e1da154e830dcfddba1f9  height=338894  log2_work=82.002117  tx=56704246  date=2015-01-14 09:28:38 progress=0.999503
2015-01-14 14:56:23 ProcessBlock: ACCEPTED
2015-01-14 14:56:24 UpdateTip: new best=0000000000000000108cc520cb80f765fcab4127e682ace9e0b3795f13e5a738  height=338895  log2_work=82.002173  tx=56704340  date=2015-01-14 09:29:35 progress=0.999505
2015-01-14 14:56:24 ProcessBlock: ACCEPTED
2015-01-14 14:56:42 Pre-allocating up to position 0x4000000 in blk00218.dat
2015-01-14 14:56:48 UpdateTip: new best=000000000000000009bcea02335bbb85f96f8e9eac7269016c9144c300653f65  height=338896  log2_work=82.002229  tx=56705806  date=2015-01-14 09:59:50 progress=0.999550
2015-01-14 14:56:48 ProcessBlock: ACCEPTED
2015-01-14 14:57:06 UpdateTip: new best=0000000000000000106507c2db67f4098a641be49cb52ee9639b25e58e56aa40  height=338897  log2_work=82.002286  tx=56706595  date=2015-01-14 10:01:55 progress=0.999552
2015-01-14 14:57:06 ProcessBlock: ACCEPTED
2015-01-14 14:57:10 UpdateTip: new best=00000000000000000468f1f21a83f84c793e98aa3f519b67da7ee9b6fac33842  height=338898  log2_work=82.002342  tx=56706827  date=2015-01-14 10:04:24 progress=0.999556
2015-01-14 14:57:10 ProcessBlock: ACCEPTED
2015-01-14 14:57:12 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-14 14:57:44 UpdateTip: new best=000000000000000003fb2e1c3f0d8781cfd4e977cf580f719397e8ced4bf53ac  height=338899  log2_work=82.002398  tx=56707928  date=2015-01-14 10:21:09 progress=0.999581
2015-01-14 14:57:44 ProcessBlock: ACCEPTED
2015-01-14 14:57:45 receive version message: /bitcoinj:0.13SNAPSHOT/DNSSeed:43/: version 70001, blocks=338928, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=162.243.132.6:58788
2015-01-14 14:57:45 Added time data, samples 13, offset -7 ( 0 minutes)
2015-01-14 14:57:45 nTimeOffset = -2  ( 0 minutes)
2015-01-14 14:57:53 UpdateTip: new best=000000000000000009ae58ccb23a372510e5f22b329881e7ee0b1333dc4c63f0  height=338900  log2_work=82.002454  tx=56708457  date=2015-01-14 10:27:27 progress=0.999590
2015-01-14 14:57:53 ProcessBlock: ACCEPTED
2015-01-14 14:58:15 UpdateTip: new best=000000000000000006437b7086ca85fc79f644cd544e731e9a370bcbe727b047  height=338901  log2_work=82.002511  tx=56709804  date=2015-01-14 10:51:00 progress=0.999625
2015-01-14 14:58:15 ProcessBlock: ACCEPTED
2015-01-14 14:58:34 UpdateTip: new best=0000000000000000095af82dbc3498db96d5e5326142028c4ceb334b15ced955  height=338902  log2_work=82.002567  tx=56710481  date=2015-01-14 11:02:18 progress=0.999642
2015-01-14 14:58:34 ProcessBlock: ACCEPTED
2015-01-14 14:58:45 UpdateTip: new best=00000000000000001613ce39a284b7377f53d2b8e018d9133b1ac955e9ff3ecf  height=338903  log2_work=82.002623  tx=56710672  date=2015-01-14 11:00:52 progress=0.999639
2015-01-14 14:58:45 ProcessBlock: ACCEPTED
2015-01-14 14:58:52 UpdateTip: new best=000000000000000006d4a905af3d13a4871e421f7a507b0ffc2ace10c61bdff6  height=338904  log2_work=82.002679  tx=56710828  date=2015-01-14 11:05:33 progress=0.999646
2015-01-14 14:58:52 ProcessBlock: ACCEPTED
2015-01-14 14:58:59 socket send error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 14:59:02 UpdateTip: new best=0000000000000000118b7b3bbea2a726d771b21445259223cce1c05fb7ac3f59  height=338905  log2_work=82.002736  tx=56711384  date=2015-01-14 11:13:39 progress=0.999658
2015-01-14 14:59:02 ProcessBlock: ACCEPTED
2015-01-14 14:59:02 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=338928, us=95.23.19.199:8333, them=0.0.0.0:0, peer=148.251.238.178:6276
2015-01-14 14:59:02 Added time data, samples 14, offset -3 ( 0 minutes)
2015-01-14 14:59:04 receive version message: /Satoshi:0.8.99/: version 70001, blocks=338928, us=95.23.19.199:8333, them=75.102.1.116:8333, peer=75.102.1.116:46092
2015-01-14 14:59:04 Added time data, samples 15, offset -2 ( 0 minutes)
2015-01-14 14:59:04 nTimeOffset = -2  ( 0 minutes)
2015-01-14 14:59:12 Pre-allocating up to position 0x800000 in rev00218.dat
2015-01-14 14:59:12 UpdateTip: new best=00000000000000000ecaa2edd0358dc9d802c5311ab902d187f69f2c0020f139  height=338906  log2_work=82.002792  tx=56712248  date=2015-01-14 11:27:30 progress=0.999679
2015-01-14 14:59:12 ProcessBlock: ACCEPTED
2015-01-14 14:59:14 ERROR: AcceptToMemoryPool : nonstandard transaction: non-final
2015-01-14 14:59:18 receive version message: /mining.bitcoinaffiliatenetwork.com:0.9.99/: version 70002, blocks=338928, us=95.23.19.199:52131, them=74.113.69.10:8333, peer=74.113.69.10:8333
2015-01-14 14:59:18 Added time data, samples 16, offset -2 ( 0 minutes)
2015-01-14 14:59:28 UpdateTip: new best=0000000000000000099753cec7585592791e7c7bc32ebff0386729560bfb0df5  height=338907  log2_work=82.002848  tx=56713057  date=2015-01-14 11:40:40 progress=0.999699
2015-01-14 14:59:28 ProcessBlock: ACCEPTED
2015-01-14 14:59:28 ResendWalletTransactions()
2015-01-14 14:59:30 UpdateTip: new best=000000000000000006ee5113984333edb6f7e0716b61313a8c543ef00243dd01  height=338908  log2_work=82.002904  tx=56713162  date=2015-01-14 11:38:08 progress=0.999695
2015-01-14 14:59:30 ProcessBlock: ACCEPTED
2015-01-14 14:59:33 UpdateTip: new best=0000000000000000174960c3ea822d132d630c52a5b2bc89089fe6925e874b16  height=338909  log2_work=82.00296  tx=56713447  date=2015-01-14 11:46:20 progress=0.999707
2015-01-14 14:59:33 ProcessBlock: ACCEPTED
2015-01-14 14:59:34 UpdateTip: new best=000000000000000001cf12e05cc26fe4e5d73296c8d1ee5b58cf634d4f64e3b4  height=338910  log2_work=82.003017  tx=56713651  date=2015-01-14 11:48:21 progress=0.999710
2015-01-14 14:59:34 ProcessBlock: ACCEPTED
2015-01-14 14:59:49 UpdateTip: new best=0000000000000000151b10e3a0f6476b3d12347d7cbe64a8c8fb2ed9ed202aff  height=338911  log2_work=82.003073  tx=56714572  date=2015-01-14 12:03:23 progress=0.999733
2015-01-14 14:59:50 ProcessBlock: ACCEPTED
2015-01-14 14:59:50 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=95.23.19.199:8333, them=0.0.0.0:0, peer=172.245.62.102:60363
2015-01-14 14:59:50 Added time data, samples 17, offset -7 ( 0 minutes)
2015-01-14 14:59:50 nTimeOffset = -2  ( 0 minutes)
2015-01-14 14:59:55 socket send error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:00:14 UpdateTip: new best=0000000000000000005db7df5713a415d21a7027becc1b95fef0caa2664a076b  height=338912  log2_work=82.003129  tx=56716333  date=2015-01-14 12:35:27 progress=0.999781
2015-01-14 15:00:14 ProcessBlock: ACCEPTED
2015-01-14 15:00:23 UpdateTip: new best=000000000000000000d8ce85c418aa241f1c79f2c71b1c9229390d5019cd97b2  height=338913  log2_work=82.003185  tx=56717007  date=2015-01-14 12:43:50 progress=0.999793
2015-01-14 15:00:23 ProcessBlock: ACCEPTED
2015-01-14 15:00:24 UpdateTip: new best=000000000000000001bf2f19c9f7860ce1eb662a55f40e7ae70763fd42ee090b  height=338914  log2_work=82.003242  tx=56717056  date=2015-01-14 12:44:03 progress=0.999793
2015-01-14 15:00:24 ProcessBlock: ACCEPTED
2015-01-14 15:00:26 UpdateTip: new best=00000000000000000f316567698602725a3639e4cba7cf59ec40d6171b79865f  height=338915  log2_work=82.003298  tx=56717417  date=2015-01-14 12:50:21 progress=0.999803
2015-01-14 15:00:26 ProcessBlock: ACCEPTED
2015-01-14 15:00:35 UpdateTip: new best=000000000000000007a9401c320720d7d027605c92f9627450929911cb4ad969  height=338916  log2_work=82.003354  tx=56718368  date=2015-01-14 13:05:19 progress=0.999825
2015-01-14 15:00:35 ProcessBlock: ACCEPTED
2015-01-14 15:00:39 UpdateTip: new best=00000000000000001387dda913934bdf1aaf87119d8731c64a840e67640ee2c6  height=338917  log2_work=82.00341  tx=56718878  date=2015-01-14 13:17:16 progress=0.999843
2015-01-14 15:00:39 ProcessBlock: ACCEPTED
2015-01-14 15:00:44 UpdateTip: new best=00000000000000000f43f8fdc552ed4acb9ed9054aee50476095326d754b5049  height=338918  log2_work=82.003466  tx=56719451  date=2015-01-14 13:20:54 progress=0.999849
2015-01-14 15:00:44 ProcessBlock: ACCEPTED
2015-01-14 15:00:47 UpdateTip: new best=00000000000000000bca307f33afde225ecb2325081b303edf042e9c3d2f4e5e  height=338919  log2_work=82.003523  tx=56719845  date=2015-01-14 13:32:57 progress=0.999867
2015-01-14 15:00:47 ProcessBlock: ACCEPTED
2015-01-14 15:01:05 UpdateTip: new best=000000000000000009d380662142133a5f5374c790fc9b4bade0a602976bb82b  height=338920  log2_work=82.003579  tx=56722734  date=2015-01-14 14:18:31 progress=0.999935
2015-01-14 15:01:05 ProcessBlock: ACCEPTED
2015-01-14 15:01:21 UpdateTip: new best=000000000000000002f50817a774de6c75feeb807777e107b931edcfdc9d18b6  height=338921  log2_work=82.003635  tx=56723741  date=2015-01-14 14:29:54 progress=0.999952
2015-01-14 15:01:22 ProcessBlock: ACCEPTED
2015-01-14 15:01:46 UpdateTip: new best=000000000000000008dcf04315f6f018639c6c2104a0ec9b9ccb8911bf32eef0  height=338922  log2_work=82.003691  tx=56724444  date=2015-01-14 14:28:19 progress=0.999949
2015-01-14 15:01:46 ProcessBlock: ACCEPTED
2015-01-14 15:01:49 UpdateTip: new best=000000000000000010cdf621f3b631573891d943fdc928e6d718c8882dc0b9a0  height=338923  log2_work=82.003747  tx=56724770  date=2015-01-14 14:34:19 progress=0.999958
2015-01-14 15:01:49 ProcessBlock: ACCEPTED
2015-01-14 15:01:51 UpdateTip: new best=000000000000000015da3548533b55c9a5000121e144f2292c2a8c8e5934dc8d  height=338924  log2_work=82.003804  tx=56725011  date=2015-01-14 14:36:19 progress=0.999961
2015-01-14 15:01:51 ProcessBlock: ACCEPTED
2015-01-14 15:01:55 UpdateTip: new best=00000000000000000a2b86a409bd4c4c726e840ef04f23840ff89e4a66d5161a  height=338925  log2_work=82.00386  tx=56725520  date=2015-01-14 14:42:05 progress=0.999970
2015-01-14 15:01:55 ProcessBlock: ACCEPTED
2015-01-14 15:01:57 Pre-allocating up to position 0x900000 in rev00218.dat
2015-01-14 15:01:57 UpdateTip: new best=000000000000000009e6b818ab79cd89d91d49418503bf5c5dbe767c5a77d622  height=338926  log2_work=82.003916  tx=56725837  date=2015-01-14 14:45:49 progress=0.999976
2015-01-14 15:01:57 ProcessBlock: ACCEPTED
2015-01-14 15:01:59 UpdateTip: new best=000000000000000015c9fc981cbddb4b2c10e68161b9d97b660c4f75a99570da  height=338927  log2_work=82.003972  tx=56726075  date=2015-01-14 14:48:03 progress=0.999979
2015-01-14 15:01:59 ProcessBlock: ACCEPTED
2015-01-14 15:02:01 UpdateTip: new best=000000000000000005c245f4f5fb44a0086f5292c3a5eafddbdb22aeef6d7fab  height=338928  log2_work=82.004028  tx=56726368  date=2015-01-14 14:51:00 progress=0.999983
2015-01-14 15:02:01 ProcessBlock: ACCEPTED
2015-01-14 15:02:04 receive version message: /Satoshi:0.9.3/: version 70002, blocks=338905, us=95.23.19.199:8333, them=148.251.249.69:0, peer=148.251.249.69:39024
2015-01-14 15:02:04 Added time data, samples 18, offset -1 ( 0 minutes)
2015-01-14 15:03:16 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=338928, us=95.23.19.199:8333, them=0.0.0.0:0, peer=148.251.238.178:21865
2015-01-14 15:05:42 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=95.23.19.199:8333, them=127.0.0.1:8333, peer=82.130.102.226:45030
2015-01-14 15:05:42 Added time data, samples 19, offset  2 ( 0 minutes)
2015-01-14 15:05:42 nTimeOffset = -2  ( 0 minutes)
2015-01-14 15:06:15 receive version message: /BitCoinJ:0.11.2/MultiBit:0.5.18/: version 70001, blocks=338928, us=127.0.0.1:8333, them=127.0.0.1:8333, peer=109.149.75.178:54021
2015-01-14 15:06:15 Added time data, samples 20, offset -4 ( 0 minutes)
2015-01-14 15:08:42 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=338928, us=95.23.19.199:8333, them=0.0.0.0:0, peer=148.251.238.178:60683
2015-01-14 15:10:16 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=95.23.19.199:8333, them=0.0.0.0:0, peer=50.244.13.28:40219
2015-01-14 15:10:16 Added time data, samples 21, offset -14 ( 0 minutes)
2015-01-14 15:10:16 nTimeOffset = -2  ( 0 minutes)
2015-01-14 15:10:24 socket send error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:10:46 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=95.23.19.199:8333, them=127.0.0.1:8333, peer=82.130.102.226:45074
2015-01-14 15:11:10 socket send error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:11:17 receive version message: /Satoshi:0.9.1/: version 70002, blocks=338928, us=95.23.19.199:55341, them=107.170.220.159:8333, peer=107.170.220.159:8333
2015-01-14 15:11:17 Added time data, samples 22, offset -2 ( 0 minutes)
2015-01-14 15:12:25 receive version message: /Satoshi:0.9.3/: version 70002, blocks=195450, us=95.23.19.199:8333, them=188.186.65.97:8333, peer=188.186.65.97:52837
2015-01-14 15:12:25 socket recv error An existing connection was forcibly closed by the remote host.  (10054)
2015-01-14 15:15:51 receive version message: /Snoopy:0.1/: version 60001, blocks=0, us=95.23.19.199:8333, them=127.0.0.1:8333, peer=82.130.102.226:57819
2015-01-14 15:16:43 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=95.23.19.199:8333, them=0.0.0.0:0, peer=106.187.90.222:46607
2015-01-14 15:16:43 Added time data, samples 23, offset -5 ( 0 minutes)
2015-01-14 15:16:43 nTimeOffset = -2  ( 0 minutes)
2015-01-14 15:16:51 socket send error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:17:14 UpdateTip: new best=00000000000000000c83ac167d47e87ae4d958d5d4706113bb5c0917b8f2fcd2  height=338929  log2_work=82.004085  tx=56728040  date=2015-01-14 15:16:48 progress=0.999999
2015-01-14 15:17:14 ProcessBlock: ACCEPTED
2015-01-14 15:17:28 ERROR: AcceptToMemoryPool : inputs already spent
2015-01-14 15:17:31 ERROR: AcceptToMemoryPool : inputs already spent
2015-01-14 15:17:58 UpdateTip: new best=000000000000000006e1704c5dd039b7c811ffa8fe06c96a5fcb384e9c531b89  height=338930  log2_work=82.004141  tx=56728326  date=2015-01-14 15:17:06 progress=0.999999
2015-01-14 15:17:58 ProcessBlock: ACCEPTED
2015-01-14 15:18:14 UpdateTip: new best=00000000000000000cf87bc7054a515f31e1a025bfb9c25400379f36701310f2  height=338931  log2_work=82.004197  tx=56728375  date=2015-01-14 15:17:52 progress=0.999999
2015-01-14 15:18:14 ProcessBlock: ACCEPTED
2015-01-14 15:18:40 ERROR: AcceptToMemoryPool : inputs already spent
2015-01-14 15:18:41 receive version message: /getaddr.bitnodes.io:0.1/: version 70002, blocks=338928, us=95.23.19.199:8333, them=0.0.0.0:0, peer=148.251.238.178:14355
2015-01-14 15:19:31 ERROR: AcceptToMemoryPool : inputs already spent
2015-01-14 15:19:39 ERROR: AcceptToMemoryPool : inputs already spent
2015-01-14 15:19:53 UpdateTip: new best=000000000000000016537c502c21da893957972fb1613399d83da076450a02e9  height=338932  log2_work=82.004253  tx=56728471  date=2015-01-14 15:20:56 progress=1.000002
2015-01-14 15:19:53 ProcessBlock: ACCEPTED
2015-01-14 15:20:26 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:28 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:29 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:31 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:32 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:32 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:35 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:39 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:39 socket send error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:42 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:42 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:44 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:20:52 receive version message: /Satoshi:0.8.1/: version 70001, blocks=338932, us=95.23.31.71:58072, them=104.174.154.228:8333, peer=104.174.154.228:8333
2015-01-14 15:20:52 Added time data, samples 24, offset -7 ( 0 minutes)
2015-01-14 15:20:58 receive version message: /Satoshi:0.9.3/: version 70002, blocks=338932, us=95.23.31.71:58107, them=37.187.97.120:8333, peer=37.187.97.120:8333
2015-01-14 15:20:58 Added time data, samples 25, offset -2 ( 0 minutes)
2015-01-14 15:20:58 nTimeOffset = -2  ( 0 minutes)
2015-01-14 15:20:58 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:21:02 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:21:10 receive version message: /Satoshi:0.8.5/: version 70001, blocks=338932, us=95.23.31.71:58179, them=92.14.81.125:8333, peer=92.14.81.125:8333
2015-01-14 15:21:10 Added time data, samples 26, offset -8 ( 0 minutes)
2015-01-14 15:21:27 receive version message: /Satoshi:0.9.1/: version 70002, blocks=338932, us=95.23.31.71:58269, them=93.174.90.30:8333, peer=93.174.90.30:8333
2015-01-14 15:21:27 Added time data, samples 27, offset -60 (-1 minutes)
2015-01-14 15:21:27 nTimeOffset = -2  ( 0 minutes)
2015-01-14 15:21:56 receive version message: /Satoshi:0.9.3/: version 70002, blocks=319075, us=95.23.31.71:58411, them=68.52.124.132:8333, peer=68.52.124.132:8333
2015-01-14 15:21:56 Added time data, samples 28, offset -5 ( 0 minutes)
2015-01-14 15:22:24 receive version message: /Satoshi:0.9.3/: version 70002, blocks=170267, us=95.23.31.71:58575, them=173.71.197.65:8333, peer=173.71.197.65:8333
2015-01-14 15:22:24 Added time data, samples 29, offset -1 ( 0 minutes)
2015-01-14 15:22:24 nTimeOffset = -2  ( 0 minutes)
2015-01-14 15:22:53 receive version message: /Satoshi:0.9.3/: version 70002, blocks=323024, us=95.23.31.71:58712, them=93.73.230.148:8333, peer=93.73.230.148:8333
2015-01-14 15:22:53 Added time data, samples 30, offset -3 ( 0 minutes)
2015-01-14 15:22:59 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=338932, us=95.23.31.71:58748, them=84.24.222.83:8333, peer=84.24.222.83:8333
2015-01-14 15:22:59 Added time data, samples 31, offset -1 ( 0 minutes)
2015-01-14 15:22:59 nTimeOffset = -2  ( 0 minutes)
2015-01-14 15:24:31 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:27:20 ResendWalletTransactions()
2015-01-14 15:31:28 UpdateTip: new best=00000000000000001039297670301909606f2e32d571844ac9b57e641697f9cf  height=338933  log2_work=82.004309  tx=56729472  date=2015-01-14 15:30:51 progress=0.999999
2015-01-14 15:31:28 ProcessBlock: ACCEPTED
2015-01-14 15:32:41 ERROR: AcceptToMemoryPool : inputs already spent
2015-01-14 15:34:42 ERROR: AcceptToMemoryPool : inputs already spent
2015-01-14 15:35:16 UpdateTip: new best=00000000000000001101d6cab1a03cf965ddb33aff5726f2c31725f85e5fb39d  height=338934  log2_work=82.004366  tx=56729852  date=2015-01-14 15:35:01 progress=1.000000
2015-01-14 15:35:16 ProcessBlock: ACCEPTED
2015-01-14 15:38:49 ResendWalletTransactions()
2015-01-14 15:42:43 socket send error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:42:46 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:42:55 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:43:01 receive version message: /Satoshi:0.9.3/: version 70002, blocks=338934, us=95.23.28.146:64269, them=176.36.99.222:8333, peer=176.36.99.222:8333
2015-01-14 15:43:01 Added time data, samples 32, offset -2 ( 0 minutes)
2015-01-14 15:43:01 receive version message: /Satoshi:0.9.3/: version 70002, blocks=338934, us=95.23.28.146:64275, them=176.9.126.177:8333, peer=176.9.126.177:8333
2015-01-14 15:43:01 Added time data, samples 33, offset -1 ( 0 minutes)
2015-01-14 15:43:01 nTimeOffset = -2  ( 0 minutes)
2015-01-14 15:43:02 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:43:03 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:43:15 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:43:18 receive version message: /Satoshi:0.9.1/: version 70002, blocks=338934, us=95.23.28.146:64368, them=93.174.90.30:8333, peer=93.174.90.30:8333
2015-01-14 15:43:20 receive version message: /Satoshi:0.9.2.1/: version 70002, blocks=338934, us=95.23.28.146:64374, them=85.1.100.87:8333, peer=85.1.100.87:8333
2015-01-14 15:43:20 Added time data, samples 34, offset -2 ( 0 minutes)
2015-01-14 15:43:26 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:43:42 socket recv error An established connection was aborted by the software in your host machine.  (10053)
2015-01-14 15:43:51 receive version message: /Satoshi:0.8.99/: version 70001, blocks=338934, us=95.23.28.146:64513, them=75.102.1.116:8333, peer=75.102.1.116:8333
2015-01-14 15:44:03 receive version message: /Satoshi:0.9.3/: version 70002, blocks=338934, us=95.23.28.146:64587, them=211.72.66.229:8333, peer=211.72.66.229:8333
2015-01-14 15:44:03 Added time data, samples 35, offset -1 ( 0 minutes)
2015-01-14 15:44:03 nTimeOffset = -2  ( 0 minutes)
2015-01-14 15:44:04 receive version message: /Satoshi:0.9.3/: version 70002, blocks=338934, us=95.23.28.146:64591, them=82.211.30.243:8333, peer=82.211.30.243:8333
2015-01-14 15:44:04 Added time data, samples 36, offset -2 ( 0 minutes)
2015-01-14 15:44:33 receive version message: /Satoshi:0.9.1/: version 70002, blocks=338934, us=95.23.28.146:64735, them=76.68.177.228:8333, peer=76.68.177.228:8333
2015-01-14 15:44:33 Added time data, samples 37, offset -6 ( 0 minutes)
2015-01-14 15:44:33 nTimeOffset = -2  ( 0 minutes)
2015-01-14 15:48:46 UpdateTip: new best=00000000000000000cb47fb59a70edb727241c029a4f571311ccc5d71957d229  height=338935  log2_work=82.004422  tx=56730824  date=2015-01-14 15:48:14 progress=0.999999
2015-01-14 15:48:46 ProcessBlock: ACCEPTED
2015-01-14 15:53:03 UpdateTip: new best=00000000000000000d1d59347069cfe59c15e59b30b0bfe5a9596bbf32615651  height=338936  log2_work=82.004478  tx=56731195  date=2015-01-14 15:52:00 progress=0.999998
2015-01-14 15:53:03 ProcessBlock: ACCEPTED
2015-01-14 15:54:09 UpdateTip: new best=000000000000000011aadf15e8004bac258ff5961d348b07e4488174a45ef466  height=338937  log2_work=82.004534  tx=56731341  date=2015-01-14 15:54:15 progress=1.000000
2015-01-14 15:54:09 ProcessBlock: ACCEPTED

In this file, I saw some "socket recv error" and I know that incoming connections start to drop when this error appears.

Anybody knows why is this happening?

Thanks

Topic: Bitcoin Core 0.9.3 drops incoming connections only - Windows (Read 1746 times)