This defect affects not only BOINC 6.6.36, I've seen it with prev BOINC versions too.
Also I've seen it on different hosts under different OSes.
Common part is:
internet connection for host in question was provided via native windows ICF (internet connection sharing).
Surely, in such hanging state not only BOINC manager can;t communicate with daemon, science apps can't too. That is, when internet connection (not network connection!) is unavailable, BOINC's work on server completely blocked.
See this thread http://boinc.berkeley.edu/dev/forum_thread.php?id=4101 for network configuration description and more thorough description of situation in whole