It's the same error that I posted about (and just recently brought back up top). The only thing that solved it was to isolate the empeg off the network, or sync on my home network.

I'm waiting on the next release beta to see if it has changed much. If not, I'll probably see if anyone at empeg wants a packet dump of the network to gauge the traffic. The empeg sits on a lab network, so it gets pelted with tons of SNMP discover traffic, and all kind of Windows broadcast noise/DHCP requests.