[RC5} Verbindings problemen

[Erik1]

Volgensmij is mijn PIII 667 koei een beetje ziek

code:

[Jun 26 20:20:46 UTC] Completed RC5 packet 65CE8D6A:90000000 (1*2^28 keys)
                0.00:02:48.78 - [1,590,417.66 keys/sec]
[Jun 26 20:21:47 UTC] Connect to host 130.161.38.84:2064 failed.
                Error 10060 (Attempt to connect timed out)
[Jun 26 20:21:47 UTC] Network::Open Error - sleeping for 3 seconds
[Jun 26 20:22:51 UTC] Connect to host 130.161.38.67:2064 failed.
                Error 10060 (Attempt to connect timed out)
[Jun 26 20:22:51 UTC] Network::Open Error - sleeping for 3 seconds
[Jun 26 20:23:55 UTC] Connect to host 145.89.128.136:2064 failed.
                Error 10060 (Attempt to connect timed out)
[Jun 26 20:23:55 UTC] Network::Open Error - sleeping for 3 seconds
[Jun 26 20:24:59 UTC] Connect to host 145.89.128.249:2064 failed.
                Error 10060 (Attempt to connect timed out)
[Jun 26 20:24:59 UTC] Loaded RC5 random 1*2^28 packet 65E8A901:10000000
[Jun 26 20:24:59 UTC] Summary: 2 RC5 packets (2*2^28 keys)
                0.00:05:40.18 - [1.57 Mkeys/s]
[Jun 26 20:24:59 UTC] 0 RC5 packets (0 work units) remain in buff-in.rc5
[Jun 26 20:24:59 UTC] 5 RC5 packets (26 work units) are in buff-out.rc5
.....10%.....20%.....30%.....40%.....50%.....60%.....70%.....80%.....90%....100
[Jun 26 20:28:09 UTC] Completed RC5 packet 65E8A901:10000000 (1*2^28 keys)
                0.00:03:09.29 - [1,418,102.52 keys/sec]
[Jun 26 20:29:10 UTC] Connect to host 145.89.128.249:2064 failed.
                Error 10060 (Attempt to connect timed out)
[Jun 26 20:29:10 UTC] Network::Open Error - sleeping for 3 seconds

code:

[Jun 26 20:54:00 UTC] 0 RC5 packets (0 work units) remain in buff-in.rc5
[Jun 26 20:54:00 UTC] 9 RC5 packets (30 work units) are in buff-out.rc5
.....10%.....20%.....30%.....40%.....50%.....60%.....70%.....80%.....90%....100
[Jun 26 20:57:00 UTC] Completed RC5 packet 65785A32:90000000 (1*2^28 keys)
                0.00:02:59.84 - [1,492,560.22 keys/sec]
[Jun 26 20:58:01 UTC] Connect to host 145.89.128.249:2064 failed.
                Error 10060 (Attempt to connect timed out)
[Jun 26 20:58:01 UTC] Network::Open Error - sleeping for 3 seconds
[Jun 26 20:59:05 UTC] Connect to host 130.161.38.84:2064 failed.
                Error 10060 (Attempt to connect timed out)
[Jun 26 20:59:05 UTC] Network::Open Error - sleeping for 3 seconds
[Jun 26 20:59:18 UTC] Connected to distributed.net 130.161.38.67:2064...
[Jun 26 20:59:18 UTC] The keyserver says: "cow clothes?
                http://www.distributed.net/dnetware/ (ivo/2)"
[Jun 26 20:59:18 UTC] Retrieved RC5 work unit 24 of 24 (100.00% transferred)
[Jun 26 20:59:19 UTC] Sent RC5 packet 2 of 10 (20.00% transferred)
[Jun 26 20:59:19 UTC] FlushRC5::Unable to send packet (-1.168).
[Jun 26 20:59:19 UTC] Loaded RC5 4*2^28 packet 5AA0A6E4:C0000000
[Jun 26 20:59:19 UTC] Summary: 7 RC5 packets (7*2^28 keys)
                0.00:20:25.05 - [1.53 Mkeys/s]
[Jun 26 20:59:19 UTC] 6 RC5 packets (20 work units) remain in buff-in.rc5
[Jun 26 20:59:19 UTC] Projected ideal time to completion: 0.00:56:20.00
[Jun 26 20:59:19 UTC] 8 RC5 packets (29 work units) are in buff-out.rc5
.....10%.....20%.

Hij heeft ergens wel 2 packets kunnen verzenden, daarna error. Kan de verbinding ergens op het net een beetje brak zijn

code:

 2) Automatically select a distributed.net keyserver? ==> yes

[Sequence]

zet de optie die je hierboven laat zien eens op 'no' en dan heb je de opties om een keyserver in te vullen (energy.keyserver.org of chaos.keyserver.org bv.) vul bij de poort (andere optie die er vlak onder staat) in 2064 en hopla! kijk dan maar eens of ie werkt

werkt ie niet? dan is er wat verkeerd met jouw verbinding..

[Erik1]

Hij werkte met een andere keyserver, heeft alle blokken die er nog inzaten erheengeflushed. Vervolgens weer op automagisch gezet en het werkte ineens weer.

[Sequence]

Op donderdag 27 juni 2002 15:22 schreef Erik1 het volgende:
Hij werkte met een andere keyserver, heeft alle blokken die er nog inzaten erheengeflushed. Vervolgens weer op automagisch gezet en het werkte ineens weer.

dan zal er gister wel wat fout zijn geweest met of jouw verbinding of die van de betreffende dnet server..

mooi dat alles weer werkt!