• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

RC5 Questions.

D

Dag

Member
After a few months I went ahead and loaded the client back on my pc. I have a few more that I can use as well, one has been cracking for a day or so now, but can't seem to upload it's blocks (it is behind a proxy, my main machine is on a nat.) Can I port those blocks over to my main machine for upload, or is there a way to set up proxy settings within the client? If I get this working I could run it on several other machine's here to help out. Here is what the client is telling me.

0.00:03:16.90 - [1,363,287.83 keys/sec]
[Sep 21 13:11:24 UTC] Network::failed to resolve name "us.v27.distributed.net"
[Sep 21 13:11:24 UTC] Network:😱pen Error - sleeping for 3 seconds
[Sep 21 13:12:01 UTC] Network::failed to resolve name "us.v27.distributed.net"
[Sep 21 13:12:01 UTC] Network:😱pen Error - sleeping for 3 seconds
[Sep 21 13:12:38 UTC] Network::failed to resolve name "us.v27.distributed.net"
[Sep 21 13:12:38 UTC] Loaded RC5 random 1*2^28 packet 65CA4F99:60000000
[Sep 21 13:12:38 UTC] Summary: 206 RC5 packets (206*2^28 keys)
0.11:16:09.69 - [1.36 Mkeys/s]
[Sep 21 13:12:38 UTC] 0 RC5 packets (0 work units) remain in buff-in.rc5
[Sep 21 13:12:38 UTC] 493 RC5 packets (493 work units) are in buff-out.rc5
.....10%.....20%.....30%.....40%.....50%.....60%.....70%.....80%.....90%....100
[Sep 21 13:15:56 UTC] Completed RC5 packet 65CA4F99:60000000 (1*2^28 keys)
0.00:03:16.91 - [1,363,218.59 keys/sec]
[Sep 21 13:16:30 UTC] Network::failed to resolve name "us.v27.distributed.net"
[Sep 21 13:16:30 UTC] Network:😱pen Error - sleeping for 3 seconds
[Sep 21 13:17:07 UTC] Network::failed to resolve name "us.v27.distributed.net"
[Sep 21 13:17:07 UTC] Network:😱pen Error - sleeping for 3 seconds
[Sep 21 13:17:44 UTC] Network::failed to resolve name "us.v27.distributed.net"
[Sep 21 13:17:44 UTC] Loaded RC5 random 1*2^28 packet 653C4D91:F0000000
[Sep 21 13:17:44 UTC] Summary: 207 RC5 packets (207*2^28 keys)
0.11:19:26.61 - [1.36 Mkeys/s]
[Sep 21 13:17:44 UTC] 0 RC5 packets (0 work units) remain in buff-in.rc5
[Sep 21 13:17:44 UTC] 494 RC5 packets (494 work units) are in buff-out.rc5
.....10%.....20%.....30%.....40%.....50%.....60%.....

Thanks for the help
Dag
 
What port number is setup in the client .ini, that you are trying to send out on?
Chances are it's blocked by the proxy your behind.

<Edit> Copy and paste your client .ini file here, we'll see what we can do.
 
To set the proxy settings doubleclick on the cow icon then rightclick
on the client window and select configure from the menu.
Then select:
2) Buffer and Buffer update options
|
6) Keyserver<->client connectivity
|
select your proxy settings..
 
Ok I am guessing you are meaning the dnetc.ini that is in my progflies\distributed.net folder?

[parameters]
id=daggur@hotmail.com

[misc]
project-priority=DES,CSC,RC5,OGR=0

that is it. I went in the command line and disabled OGR, but I couldn't find any proxy settings anywhere. Let me know where I can put them in, and if I need to tweak this any more than it is. Sorry, looking back it has been about 6 months since I have had the client running.

[edit] Ok I went in and set the proxy settings per nukefarmer's instructions, let me see if this will work. [edit]

Thanks
Dag
 
YAY! it is working now 🙂. Ok so I have my PIII 600, and my PIII 500 notebook setup. The workstation is saying it is getting 1.25 Mkeys/sec and the 500 is getting 1.35. The 600 is my work machine, so I use it quite a bit, but is there any way to speed things up a little?

Also, what works best for this? coppermines? cels? We are all dell, but I could hook up another 2 or 3 machines in the 500 range to get moving.
 
Dag,

Try adding the following to your dnetc.ini file and restarting the client. This will try to go through the http port 80 through the teams RR pproxy:


[networking]
keyserver=proxy80.teamanandtech.com:80
nofallback=true
autofindkeyserver=no

Good Luck! 🙂
 
If not set, by default it's tiring to use port 2064.

You might need to find out which proxy port your getting out to the internet with, and add that to the dnetc.ini file.

You might also want to go though the whole configuration thing, to set every aspect of your dnetc.ini file.

At the command line, cd\Your dnet folder and then dnetc -config.
Go through each one, and add what is relevant to your project. (RC5 or OGR)

<Edit> Doohh, I'm to late!
A customer came in and I had to change out his Power Supply in the middle of this post. 😉
 
Dag,
Glad to hear that you got it working! 😀

Other than not using the PC for anything else but RC5 😉, make sure you don't have a lot of unnecessary processes running that would take away CPU cycles. 3D screensavers are killers, get rid of them.

LOL Kilowatt, I did the same thing. I had actually scrolled down at one point and then saw Dag say it was working. Hehe!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top