[Jul 02 23:40:09 UTC] Connect to host 204.209.128.157:2064 failed.
Error 10060 (Attempt to connect timed out)
[Jul 02 23:40:09 UTC] Network:pen Error - sleeping for 3 seconds
[Jul 02 23:40:42 UTC] Network services are not available or not supported.
--fetch and --flush services are not available.
Nope, its still not working. Let me try a different PC on a different connection.
Marty, go to http://n0cgi.distributed.net/rc5-proxyinfo.html(it's the list of current Dnet keyservers). Then, pick a server, and add .proxy.distributed.net to the end of its name(so proxy1.mpls.mn.us would be proxy1.mpls.mn.us.proxy.distributed.net). That should allow you to be able to find a keyserver to use.
Nope. I tried setting the client on two different computers to use mika.dhs.org, clueless.2y.net, and the standard dnet keyserver. None of them goes through.
I have nearly 3000 blocks in my buff-out, though. And I have two other systems which should do 1000+ per day at another location, which are also not flushing. Nearly all of those will be randoms, though. Ah well, it should make for a nice flush when it finally starts working again.
204.209.128.157 is the correct IP address for the TA pproxy, so it isn't a DNS problem.
If you're on a LAN, your firewall may now be blocking port 2064. Try changing to port 23 on the TA proxy. That is the Telnet port and rarely gets blocked.
[Jul 03 01:00:51 UTC] Network services are not available or not supported.
--fetch and --flush services are not available.
Its still not working. I have no idea why. I tried using mika.dhs.org with port 23, and clueless.2y.net with port 80. Both times I get the same error message.
I'm fetching blocks now; I used Virge's suggestion and went with proxy1.mpls.mn.us.proxy.distributed.net. I'll fetch enough blocks for a long while now, and then flush when Mika's proxy is back online.
OK, I've refilled my buff-in. However, It seems to be ignoring my change to the configuration where I specify that it download 20000 blocks. Here's the excerpt from my .ini file:
Marty, the client, as I discovered, will only download 500 blocks. Set your packet size to 2^33 and you will download 500 blocks with 32 Work Units per block = 16000 work units, if available.
However, this is not guaranteed since there may not be that many 2^33 size blocks available, but anything higher than what you have is better...
There is some irony here. We are building for a "Megaflush" of our own. DPC'S lookout! I did get one to work through clueless, but I don't want to go around resetting every machine. Randoms are probably being done on three of my part-timers.
OK, now I have ~1.5 days supply on hand for my machines here. Two others elsewhere are probably stuck doing randoms. Engineer, I changed the preferred packet size to 2^33, but only after I already fetched. So my buffers will be enlarged tomorrow.
Sure glad I set my work system up to use Remote Buffers as well as clueless proxy (Clueless is the only one I could use since I needed port 80 to get through the firewall after installing Windows98....)...Working like a charm
Thanks again Clueless.....
P.S. Dantoo, I mentioned that in ViRGE thread about being #1 on 7/01/00;p...Hope it's a big flush!
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.