I had the same problem, with additional information that there was a network problem (although my network was ok).
For me, the problem was that my own user is a limited / regular user and does not have administrator rights. I received a UAC invitation when I tried to get a license, and I raised this process to use a separate administrator account, but that did not work.
What worked, however, was logging out of my regular user, logging in as my administrator account, and trying to get a developer license this way.
Thus, it is obvious that running as a privileged user is not what VS2013 appreciates in scenarios like this. I'm not sure why there is a difference between elevating a process through UAC and logging in as an elevated user.
source share