Loosing block to unknown proxy!

[The Reaper]

Well Jayor's proxy must have been down this morning and my blocks got dumped to some unknown proxy (The keyserver says: "Cuidado, hay Llamas !proxy1.fll.fl.us.distributed.net). This is the second time this has happened and now I'm out 3000 blocks. The blocks from the first time never even showed up in my Dnet stats and I'm figuring todays wont ether. How can I stop this?

 

[Fingers]

you can make a copy of your buff out file and send 1 tot he proxy and one strait to dnet just to make sure it gets counted.

 

[Jani]

Your blocks went directly to dnet. If you want you can disable this feature.

-> configure (right click)
-> 2) Buffer and Buffer Update Options
-> 6) Keyserver<->client connectivity options
-> 5) Disable fallback to a distributed.net keyserver? ==> yes

and then few times 0

 

[The Reaper]

I don't have that option, these are my options under 6) Keyserver<->client connectivity options
1) Network Timeout (seconds) ==> 60 (default)
2) Automatically select a distributed.net keyserver? ==> no
3) Keyserver hostname ==> jator.2y.net
4) Keyserver port ==>
5) Keyserver is a personal proxy on a protected LAN? ==> no
6) Firewall/proxy protocol ==> none/transparent/mapped
7) Use HTTP encapsulation even if not using an HTTP proxy? ==> no
8) Always use UUEncoding? ==> no
9) Dialup-link detection ==> Normal mode
Any ideas?

 

[GeoffS]

Neither do I... and I'm on the most recent... 463 (isn't it?)

Geoff

 

[bphantom]

5) Keyserver is a personal proxy on a protected LAN? ==> no

Set #5 to 'yes' and it will restrict your client to Jator's.

Brad..

 

[HeavyIron]

Rats!

Brad beat me to the answer 😛

 

[The Reaper]

Is that right? I want to dump to Jator's and maybe have Mika's as a backup. Thanks for the replies.