Addnode bitcoin.conf

BitCoin.conf is the configuration file for both bitcoin (GUI) and bitcoind (daemon). In my bitcoin clients I usually only have one PC which runs bitcoin as a server. All others connect to it to mine. Here is an example bitcoin.conf file. Just cut, paste, edit, and ensure it is bitcoin.conf, not bitcoin.conf.txt or anything else. Also make sure the file is in the correct folder:

Windows XP:
C:\Documents and Settings\[USERNAME]\Application Data\Bitcoin\bitcoin.conf

Windows Vista & 7:
C:\Users\[USERNAME]\AppData\Roaming\Bitcoin\bitcoin.conf

Ubuntu/Linux:
/home/[user]/.bitcoin/bitcoin.conf

Mac OSX:
/Users/[user]/Library/Application Support/Bitcoin/bitcoin.conf

# bitcoin.conf configuration file. Lines beginning with # are comments.

# Network-related settings:

# Run on the test network instead of the real bitcoin network.
#testnet=1

# Connect via a socks4 proxy
#proxy=127.0.0.1:9050

# Use as many addnode= settings as you like to connect to specific peers
#addnode=69.164.218.197
#addnode=10.0.0.2:8333

# … or use as many connect= settings as you like to connect ONLY
# to specific peers:
#connect=69.164.218.197
#connect=10.0.0.1:8333

# Do not use Internet Relay Chat (irc.lfnet.org #bitcoin channel) to
# find other peers.
#noirc=1

# Maximum number of inbound+outbound connections.
#maxconnections=

# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)

# server=1 tells Bitcoin to accept JSON-RPC commands.
#server=1

# You must set rpcuser and rpcpassword to secure the JSON-RPC api
#rpcuser=user
#rpcpassword=password

# How many seconds bitcoin will wait for a complete RPC HTTP request.
# after the HTTP connection is established.
rpctimeout=30

# By default, only RPC connections from localhost are allowed. Specify
# as many rpcallowip= settings as you like to allow connections from
# other hosts (and you may use * as a wildcard character):