Topic: ... (Read 8798 times)

I disconnected my router and connected the netbook directly to my cable from my ISP.  I had scanned it while it was on my lan and had some ports open.  I used a remote port scan site to see what ports I had opened.  They were all closed -- even those that were open.

Now, things are complicated.  There is a system where the computer can ask the router to open ports for it on its behalf but that system is considered too powerful.  A single compromised system on your network can leave all of your devices exposed.

To test whether your port is open on your host (local computer):

telnet localhost 8333


If you get a connection message then the port is open.  Press Control+C to get out. 
If it says something like "port not open", then there something wrong with the settings on your computer.  We cannot blame your router or anything else.

Now see if you can connect from another computer on the same LAN:

telnet your.LAN.IP 8333


You may find that some routers isolate hosts from each other on the LANs.  It may be that your computer has a restriction from allowing connections from another host to connect.  Your computer's fire wall settings are designed to protect you from worms.  But if you purposely run a server you want to be exposed to the Internet.  You pray there are no Zero day exploits and keep your system up to date.

If you cannot connect via telnet from the other computer, you have some settings to fix on your system and possibly your router.


Finally, once your have your bitcoin server exposed throughout your LAN, then you should see whether you can connect from the outside world.  There is a port scanner at www.grc.com or you could ask a friend to try the steps above.  Of course you need your global IP.   Not your LAN IP.  The router should forward requests at port 8333 to the same port inside to your.LAN.IP. 

If you are unable to get it exposed to the larger Internet, it may be the router or ISP.


sdp

May be your laptop may be old or dosent reach the requirements needed.

apples and oranges here..just stop comparing full client, web wallet and light wallets and it will be fine.

Blockchain wallet is not trusted at all. The trusted ones are Bitcoin Core, multibit electrum,etc.

I agree with op.
New members don't need to use qt.
Just use blockchain wallet or a similar trusted wallet.
This is what I do.

Thank you, i will try.

Make a backup of your wallet.
Install most recent version.
And you're done. If any problem occurs, you can downgrade and recover the wallet from the backup.

To check the version, running Bitcoin-QT, just click in the menu Help > About.
It will show a screen like this one: http://ubuntu-tricks.com/wp-content/uploads/2013/04/Screenshot-4.png

I´m fairly ignorant but i´m trying to learn (without losing the few bitcoin i have). What is the best way to update Bitcoin QT? For someone that as a poor understanding is kind of scary. I dont even know the version that i´m running Is there a step by step manual or something?

There is nothing sloppy here, the software is literally over a hundred times faster than it originally was, and much more reliable too-- in general. What it's doing is just fundamentally hard-- it is independently and autonomously verifying over 70 million transactions.  There are many recent improvements and more in the pipeline, and more that we know are possible but haven't started on yet... but nothing can magically make it fast and easy.  And these reasons, among others, are part of why almost all of the developers of Bitcoin Core are not in favor a >2000% increase in operating cost as a step function in the recent block size drama-- if you think it's bad now, try it with several times the load.

It's doing this because this persons state is corrupted and they have rejected the chain as invalid.  As far as its concerned these peers are just attacking it by feeding it invalid blocks.

Why precisely it rejected the chain is hard to say without a log of where the rejection happened, and even with those logs it can be hard to know why without more testing. This can be due to hardware errors, or due e.g. to antivirus software corrupting the database. (or bugs, but I am not aware of any that would cause chainstate corruption right now). The corruption can be resolved with a reindex, but without knowing why it happened it may just corrupt again before you even finish the reindex.

Unfortunately, Bitcoin is a fantastic hardware test. (The unfortunate part is that a surprisingly large amount of hardware is slightly flaky)

I remember having a similar issue when I was running the Qt core client on a Windows VPS. The syncing slows down for a while, but it will definitely go past that. Just leave it running in the background for a few hours or days as appropriate. Not efficient, but not necessarily a major issue.

Well hearing that he installed McAfee made me question his skill (he did mention customers). As far as removing it goes, it should be pretty simple to remove it for a experienced user. You can always take the hard way out and boot a live CD and manually destroy everything.

AFAIK the problem is the CPU and HDD. I've used some coins that were RAM heavy in the past which slowed down their syncing time (e.g. Monero). You can't blame the client for this.
However you can always download the blockchain via torrent if you want a quicker way. Without pruning syncing will always take a long time.

McAfee creates more problems than it solves. Also good luck in getting that out of your PC. It kind of latches on to anything like a leech and very hard to remove. Much worse than a virus.

Yes, 8333 is still the default port. Your local firewall is only one part of the picture though. If you want outgoing connections reaching your machine and its sitting behind a router you will need to configure the router accordingly. On most routers its called "port forwarding" and its forwarding traffic coming from the internet on (a) certain port(s) to a specific machine in your local network. Make sure your local machine running the bitcoin client has the same IP (via the routers DNS settings) and the rule allows port 8333 to be forwarded to that IP.

If my bitcoin executable is whitelisted on my firewall, do I still need to manually open 8333? How can I know if thats the correct port?
I haven't changed anything and from what i've read here I assume 8333 is still the default port?

Ok, if someone changed the default port to something other than the default they would then need to open/forward said port in lieu of 8333.  You got me and my "bullshit".

Being rude is only a minor issue. I think for non-technology-experts it is important to develop a feel for how the hucksters behave versus how somebody with some knowledge behaves, even if they don't immediately know the right answer.

I remember helping my friend's kids (high-school age) set up their AT&T DSL. They asked me a question, I smiled and took a breath to answer and they immediately told me "Stop, don't tell us! Let us make 3 guesses!". The attitude to learning and problem solving seems to be probably more important than the detailed knowledge.

I cannot erase what I know from my brain, but I'm trying to learn purely by interpersonal attitude clues how people can make a judgment about the value of the advice. The hucksters seem to have this apparent confidence in their manner, that's probably why they are called "con men" in the American parlance. The true experts tends to be more nonchalant or irreverent when talking about their area of expertise.

It is always easier to make better guesses about that in person, not through the written medium. The intonation of "Why you would do that?" can say a lot of things that are somewhat difficult to explain in writing.

I also think that it's not worth helping you because when you ask for help and then disregard the answers you get, it's just rude. This is like stopping someone in the street to get directions and then walking the opposite way.

And even worse, you end up with some ridiculous rant about the core client based on your 'technical skills'. Obviously, it has no merit and simply shows that not only you don't know, but you don't even know that you don't know.

It took ages to me too and this was before 0.0.9 when it was even slower

3-4 days to download the blockchain is not viable tho, we are losing a TON of potential nodes with such a sloppy client.

Another bullshit claim. As of this moment getaddr.bitnodes.io shows 59 full nodes listening on a non-default port, different than 8333. Obviously, the time to sync will be much longer when one's node can access only less than 1% of the global full nodes.

But my point stands: in a completely unregulated market like Bitcoin everyone has to be really vigiliant and keep their bullshit detectors tuned really sensitive. Otherwise you are going to be just another mark exploited by the cons that concentrate on this forum.

Libertarian capitalism is cruel that way. The essence of the functioning speculation markets is that there has to be a constant supply of people willing to take the "stupid" side of the trades.