Quote from: Muhammed Zakir on July 21, 2014, 11:18:57 AM

Quote from: spin on July 21, 2014, 08:49:54 AM

Quote from: graphicsdump on July 20, 2014, 01:44:58 AM

Ok, taking a crazy amount of time to sync...I'll give it a go once it's done. Thanks everyone!

Turn on bitcoin on both pcs while connected to the same network. On the new pc add a connect=123.13.123.123 to the config or command line of bitcoin where you replace the ip with the lan ip of the old pc.

Sync will go much quicker as the nodes will talk to each other rather than over the internet.

Once it's done you can remove bitcoin form the old machine. Also remove the connect line from the new machine's config.

I didn't heard about this. Will this faster the syncing process(via localhost)? Should I replace the IP or add it to config?
Kindly,
MZ

If you have multiple pcs running bitcoin core on the same LAN you can make sure that they sure they sync to each other using connect or add. Otherwise you might have multiple pcs downloading the blockchain from the internet.
https://en.bitcoin.it/wiki/Running_Bitcoin

See qoute below:

Quote from: satoshi on February 16, 2010, 01:34:56 AM

Right now there isn't a port number setting to do that. It's a feature yet to be implemented. You can only set up your NAT to port-forward to one of the computers. (I said something earlier about NAT port translation, but that wouldn't work, other nodes wouldn't know to connect to that port)

If you want, as a small optimization, you could run the rest of your computers as:
bitcoin -connect=

so they get all their network communication from the first computer and don't all connect over the net individually for the same information. This saves bandwidth, although it doesn't use much bandwidth to begin with, so it wouldn't really matter unless you had tons of computers.

For redundancy in case the first computer goes down, you could have two that connect out and the rest connect to both of them. The first two are run normally, the rest are run like:
bitcoin -connect= -connect=