Flush::Bad Packet Acknolowledgment
Anyone else recieving this error?
[Dec 02 03:04:50 UTC] Connected to 220.127.116.11.in-addr.arpa:8080...
[Dec 02 03:04:50 UTC] FlushCSC::Bad packet acknowledgement. (0.168)
I was getting it from work and now also from home. I tried sending directly to D'net and got same result. It appears to happen 90% of the time for me, or send a few blocks and stop.
I believe socalgal had somewhat of the same problem...you may want to look back at past posts and see what they came up with...
Yes, I was having that same problem awhile back when my ISP was flaky for about a week. Are you having ISP problems?
Let me guess. Your using version .432 GUI? You are also going though a proxy or firewall?
If that is the case. You are just finding some of the networking bugs that are in the .432 GUI client. That is one of the reasons why it was replaced with the .436 GUI client. Eversince .436 the GUI client has been dog slow. That is why so many use the .432 GUI client still.
I used to have horrible problems with that at one point. Had to go back to an incredibly old client version to get it to send more than 1-2 blocks in every hour. The newest client seems to have solved that problem though. This was only at work, through a local proxy server. If you are getting it both home and work, it may be a sign of a problem with the client you are running, or a coincedence of internet problems both places.
i had this problem on one of my systems and that was becuase i had the timeout in the network config set to too small a number, (i had it set to 5 or 10 when the default is 60)...
New Security Features Planned for Firefox 4
Another Laptop Theft Exposes 21K Patients' Data
Oracle Hits to Road to Pitch Data Center Plans
Microsoft Preps Array of Windows Patches
Microsoft Nears IE9 Beta With Final Preview
Simplified Analytics Improve CRM, BI Tools
Android Passes RIM as Top Mobile OS in 2Q
VMware Updates Hyperic System Management
File Monitoring Key to Enterprise Security
LinkedIn Snaps Up SaaS Player mSpoke