Problems uploading RC5 packets

[GeoffS]

I'm getting the following error:

Connect to host 127.0.0.1:25 failed
Error 10061 (Connect was rejected. Destination may be...)

when trying to connect to 127.0.0.1:25. I think this IP address is automatically determined by the software. Is there anything I can do about this? It's been happening alot lately. I seem to be able to pull packets down no problem, but can't push any up.

Any ideas?
Thanks!

 

[nukefarmer]

The address 127.0.0.1 is a special loopback address (also named localhost).
This address is always associated with your own computer.
Also it's connecting to port 25 which is where usually a mailserver is located. Did you enable the option to mail the logfile or something?
Maybe you can post your ini file to see what's wrong...

 

[Engineer]

Something is wrong....127.0.0.1 is yourself (Your PC's internal loopback IP #).. (Anyone else confirm this?)...

You could try setting your keyserver to the team RR Pproxy by adding the following to your dnetc.ini file:

[networking]
autofindkeyserver=no
keyserver=proxy.teamanandtech.com

But the above number is confusing?

 

[Beefcake]

Yeh, 127.0.0.1 is the internal loopback address thats why you are having problems, follow Engineers instructions!

 

[Kilowatt]

Unless he's trying to connect to his own PProxy on that machine, that's the IP I give my dial-up machine at home.
If that's the case, you should change the port # to 2064.

 

[GeoffS]

Thanks guys. I have changed to the TeamAnand address... let's see how that works!. My PC is behind a LinkSys Cable Router... does that have anything to do with it? I have only noticed this in the last couple of days after cracking on this PC for a couple of months. What is the url to check stats with TeamAnand. I imagine the stats on distributed.net get updated also?

Thanks!

 

[Engineer]

Yes, they get updated on D.net too!

Mika's RC5 Weekly stats page #1

Mika's RC5 Full Stats page #1

Mika's OGR Weekly stats page #1

Mika's OGR Full Stats page #1

Enjoy

 

[GeoffS]

Thanks Engineer... did my first upload with no problems. Thanks!

 

[GeoffS]

Whoops... spoke too soon... I just started having this problem with addy 127.0.0.2:25. I recently installed Win98SE fresh and have only had this problem since then. As I mentioned, I am using a cable modem through a LinkSys cable router/firewall. Anyone else getting this? I don't have the rev# of the software I am using handy, but I'm sure it is very recent...

 

[Kilowatt]

<< ...having this problem with addy 127.0.0.2:25 >>

Is this configured as your Email addy?
If it is, you need to put in your Real email address.

If this the &quot;keyserver&quot; you selected, your trying to send blocks to yourself.
That will only work if your running a pproxy on this machine.

Distributed.net's main &quot;keyservers&quot; can be conected to at: v27.distributed.net
This is the default setup.
You can leave out the port number if you wish.

Why don't you copy and paste your entire dnetc.ini config file here, so we can have a better idea what the problem is.

 

[GeoffS]

I will do that tonight. Thanks!

 

[GeoffS]

Here we are...

[parameters]
id=removed(it is correct)

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

[logging]
mail-log-max=4096
log-file=rc5log.txt
log-file-type=fifo

[rc5]
randomprefix=215
preferred-blocksize=31

[networking]
autofindkeyserver=no
keyserver=proxy.teamanandtech.com

 

[Engineer]

GeoffS,

You could try to place the IP address of Mika's directly into the dnetc.ini file:

replace the proxy.teamanandtech.com with

204.209.128.157 (mika.dhs.org - Correct me if I'm wrong anyone?) and don't rely on DNS...

That one is the most puzzling I've seen yet..?

P.S. I've been behind the Linksys Cable/DSL Router since I started RC5 with 3 PC's and never a problem....

 

[Kilowatt]

HMMM......I see:

[logging]
mail-log-max=4096 <------ this setting will email a 4096K log file to ????
log-file=rc5log.txt <------ You might change this to rc5.log not .txt
log-file-type=fifo

Are trying to email your logs to someone?
If not, just delete that line: mail-log-max=4096 and replace it with: log-file-limit=100kb
This will limit your log file to no more than 100k, so it doesn't grow to huge.

Also, change:

[rc5]
randomprefix=215
preferred-blocksize=31 <------- blocksize to 33

This will help prevent buffer fraging on the ppoxy side.

The rest looks OK.

 

[GeoffS]

Hmmm... I set the log big so that I could capture more information to try and diagnose the problem... unfortunately, error messages do not seem to be sent to the log, and I never set it back down! I'm not trying to email them anywhere... wonder if that's the problem! I notice at work I don't have that line in my config file, and I don't have that problem here... I'll have to try that tonight!

About preferred block size... when I set it to 33, I was getting one packet each connect. When I set it back down to 31, I would get lots of packets to chew on.

Thanks all! It looks very sad starting at the bottom of the heap on the Mika stats page

 

[ctll]

blocksize, + FETCH size..... (duh uh how many blocks should i fetch,(says the proggy))


[parameters]
id=ctll@netscape.net

[rc5]
preferred-blocksize=33
fetch-workunit-threshold=1000
flush-workunit-threshold=100
randomprefix=150

[networking]
keyserver=teamanandtech.dhs.org
disabled=no
dialup-watcher=disabled
interfaces-to-watch=*

[processor-usage]
priority=0

[des]
preferred-blocksize=33

[triggers]
restart-on-config-file-change=yes

 

[Kilowatt]

Like ctll said, add the line:

[rc5]
preferred-blocksize=33
fetch-workunit-threshold=1000 <----- to the number of WUs you want

A 1000 WUs will last a real long time on a slow machine.
500 might be better if you manualy flush it every other day or so.