Bad Packet Acknowledgment

[socalgal]

I leave PC on all day, but offline. I come home, log online and proceed to send packets in and get these Bad Packet Acknowledgments on every other packet, it seems.

Lately my transmission has been very slow during the part of day I attempt to send and I think this is causing the problem.

I find that if I close RC5 and open it later when the thruput is better, it goes through fine. Meanwhile, I'm not crunching. [img]/forum/frown.gif[/img]

Anyway. Is there a resolution to this other than having to wait for a better thruput? Or, am I stuck...

[cwizard]

Hello Socalgal:

The bad packet thing happens from time to time with me. I use the .432 GUI client; works great, simple to operate. And, never falls back as a simple option.

I don't know what causes the bad packet problem as such. More than likely a network issue not related to the client. When it happens to me, I simple keep flushing until it's done. Has nothing to do with crunching as far as I know, and I've crunched about a million blocks since January (3/4 under another e-mail). So, keep flushing until it all goes.... and keep on crunching too.



[This message has been edited by cwizard (edited 10-05-99).]

[izzzy12k]

Set up for a larger buff-in. And just wait until your connection is better. If you finish 500 blocks too fast, then get the newer client and setup for RC5 8*2^33. That should last you till you can upload/download.

izzzy12k

[Virus]

v2.7105.328 - 334 clients had a lot of network connection problems. I remember I had problems even getting it to work through a transparent web proxy. This is the main reason those clients aren't available on d.net anymore. They fixed these problems in v2.7105.336, but it made the client crack slower then the previous ones.

If you are using these clients and are having connection problems. I recommend you upgrade to the lastest CLI version.

[socalgal]

I think I have deeper problems than just Bad Packets - my 3rd attempt to post this reply..

Anyway.

Thanks for all your quick reponses! [img]/forum/smile.gif[/img]

Running: RC5DES v2.7112.444 CTR 99072212...

If I am reading you all correctly, then I'll just change my connection mode and keep crunching til the connect is better...

Besides, I have to figure something out, I have to catch back up to codybear... [img]/forum/wink.gif[/img]

Thanks... [img]/forum/smile.gif[/img]

Edit: Will be checking some other options concerning ISP.


[This message has been edited by socalgal (edited 10-06-99).]

[codybear]

Hi there...I'm running the same client as you are and darn close to the same setup...you are at 527 i believe and I'm at 515 and have had no problem at all flushing and fetching and have not seen any 'bad packets' yet....took me a while to figure out how to get on virus page but I'm sure once you work out the bugs you will catch me...

but


i do have two systems that are not complete(no modems or cd) but enough so that they will crunch....I just need to get them going and use my main system to send the packets...then I will be hell to catch

[socalgal]

Hi codybear [img]/forum/smile.gif[/img]

I believe the Bad Packet problem is due to Earthlink's network/server problems this week. Hopefully this will be resolved when I go DSL in a couple of weeks..

Actually, I lowered my FSB to 112 so I'm at 504 for now - will change that stats page when I get home from work, thanks for the reminder. Without much extra cooling, my chip is getting pretty warm, so I'm more comfortable notching it down a bit.

Meanwhile, I've got NetZero installed to use to dump the packets. It seemed to work well last night.

[img]/forum/smile.gif[/img]

[bkehoe]

Sysopt seems very slow to me today. I am able to access other U.S sites, e.g. Windows Update and download at the usual speed, but I find I have to wait a while for a page to load here.

No bad packets though.

Brendan

[izzzy12k]

SysOpt appears to be fine on my end.

I did have a bad sugar packet this morning though. [img]/forum/smile.gif[/img]

-izzzy12k