Find a recent IP list of nodes and try this:
launch with bitcoin-qt -connect=IP
from terminal. A single IP. You will have a single connection, but since you can only sync with one anyway it does not matter. Launch regularly when done sycning.
[...]
IIRC, this procedure is not necessary any more with Bitcoin Core >0.10.0, as it gets data from multiple peers now.
last updated 2014.10.10
-------------------------------------------------------------------------------------------------
IP - location - owner[1]- speed - info/stats page[2] - testnet
-------------------------------------------------------------------------------------------------
84.200.34.113 - Freinsheim, DE, EU - Newar - 1000 mbit/s - yes - no
185.45.192.129 - Amsterdam, NL, EU - anon - 1000 mbit/s - /node.php[3] - yes
213.165.91.169 - Germany, EU - shorena - 100 mbit/s - yes - no
50.7.68.180 - New York, USA - Newar - 100 mbit/s - yes - no
5.9.24.81 - Germany, EU - zvs - unknown - no - no
178.79.173.71 - United Kingdom, EU - zvs - unknown - no - no
107.155.104.194 - Dalls, USA - zvs - unknown - no - no
106.185.32.195 - Japan, Asia - zvs - unknown - no - no
94.242.57.173 - Russia, Asia - zvs - unknown - no - no
-------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress
Regarding that list... I had to close those two (not impressed with VertVPS and Hetzner customer service / support at all).
Also, AFAIK, zvs closed his nodes on that list too.
