Yeah sorry guys, i've been pulled out of country, will solve this asap
Now we are talking!!!
I will just go ahead and delete my post once the OP has been updated.
That is the only one you need. The other three are compiled into the client, and two no longer work.
The node above is not in the client, and it is the official explorer, so when you hook up with that, it will feed connections to you. The other 3 will not make any difference to connecting, with perhaps the reiteration of 91.121.67.93 giving a double kick to the wallet. The other 2 put extra strain on it.
If a wallet thinks it has to connect to node X, a dead node, it will keep on trying.
That is why it is always best to compile generics, so as nodes change, connections do not, but A Records do.
node.example.com
then you alter the A Record when necessary and relieve the wallet of the energy and strain on the computer searching for nodes it will not find.
I updated the automatic connections in the source so it is okay if you are compiling, and I included cryptochat explorer and novaexchange's nodes.
In fact, net.cpp is used incorrectly by virtually every alt (including by me), but I won't bore with the details. But Muddafudda is good on connections if interested.
username=
password=
daemon=1
rpcallowip=127.0.0.1
rpcport=8029
port=8028
addnode=91.134.120.210
no need for "listen=1" either, as it is coded as true anyway.
