Yeah I really think it is something simple like seed nodes, I am not 100% about it, but I have heard they limit you to 500 blocks when it is busy, and so seems strange that it is going in 500 block increments.
I also think the daemon=1 tag in the .conf could help... Though again not 100% about it.
EDIT: It is moving slowly, 500 blocks at a time... So it'll get there
I am not sure how daemon=1 could help, as that allows it to take and send rpc calls remotely and run in the background. I'm not an expert in the code, but to my knowledge that function is unrelated to syncing.
I've had the problem with a few coins, and usually you just deal with restarting it several times. Once it's fully synced, as long as you don't let it get way behind, it seems to be a non issue. Though some coins have specific points they stick at, while other's it's the number of blocks like this example.
Oh okay, I thought running it as a daemon specifies it as a node, as you run all coind wallets with -daemon but you're probably right.
In this case I didn't let it get way behind, re-downloading the blocks was a requirement. We had the same thing with Netcoin recently when moving to POS. And sure it could be something as simple as that, the only reason I thought of seed nodes was because in this case the number of blocks is 500... Again could mean nothing. Merely making a suggestion that might help.
