Just got the error "Could not connect socket (error 0x80040038)" in emplode 2.0 B3 after trying to start a sync about an hour after initial connect via ethernet. The only changes were to song tags, nothing was being added or removed. The player had not been restarted, it was just sitting paused on my desk.

Checking netstat, no active connections exist between the empeg and my system. (I'm not sure if there normally should be while emplode sits open...). Also, the arp table on the system does show the empeg still in it's cache, and the empeg can be pinged from the desktop.

Just an update to this, I had waited to work around this error until I was less distracted at work. Anyhow, I figured I had an easy way of knowing if it was emplode or the empeg that caused the problem. I restarted the empeg, tried the sync again, and recieved the same error, instead of recieving a cookie error of any type.

And just for extra details, the system that this and the other error occured on is a Windows XP Pro machine, running 2 ethernet connections to two different networks. The empeg sits on the network that the laptop sees as number two, and both the empeg and laptop had an IP address in the same subnet of 255.255.255.0. The network has about 100-150 machines up at a time, and has two switches, one that the empeg is connected into with my laptop at my desk (thus elliminating the possibility of normal traffic being seen by the empeg). The empeg does get quite a few broadcast packets though, as it's a test network with a ton of SNMP discoveries going on, along with the typical broadcast traffic of practicially any Intel based server OS.

Looking at the errors, I believe it's some sort of network glitch in emplode it's self, due to the fact that the subnet remains accessable even after emplode dies, and a restart of only emplode fixes the problem.