If you're using <0.10.0rc1 (latest as of this writing), your daemon downloads the chain from only one node. If it happens to pick a slow one you're going to download it slowly. Increasing the number of connections doesn't improve this.
Try 0.10.0rc1, which grabs the headers first and then downloads the blocks from several peers in parallel. It's WAY faster.
#1 This ^. If you can use 0.10.0rc1
#2 If you must use an older version:
#2.1 use the torrent[1][2]
#2.2 after(!) you used the torrent, connect to a single fast peer. Take one from the list below. If any of the IPs are not working, let me know. To connect to a single node use the connect=IP command, e.g. (Windows):
List of nodes:
---------------------------------------------------------------------------------------------------
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
191.236.50.217 - Virgina, US - grue - 100 mbit/s - no - no
---------------------------------------------------------------------------------------------------
!!The following nodes have been unreachable at the time of the last update and might[5] be down!!
---------------------------------------------------------------------------------------------------
eldinhadzic.org[4] - LA, USA - eldinhadz - 1000 mbit/s - no - 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
[4] IP is 173.236.158.177
[5] or reached max connections at the time of testing
[1] https://bitcointalksearch.org/topic/ann-bitcoin-blockchain-data-torrent-145386
[2] there is another one I cant seem to find atm