[PROXYPER] Proxy connection :Unable to send request

Keef keef at keef.yi.org
Thu Mar 9 22:31:36 EST 2000


the machine you are on is localhost.  I'm not sure, but I assume it asks for
a hostname because sometimes network IP's can be similar to Inet IP's (in
the lower classes)
----- Original Message -----
From: DHS <dx7 at earthlink.net>
To: <proxyper at lists.distributed.net>
Sent: Thursday, March 09, 2000 10:23 PM
Subject: Re: [PROXYPER] Proxy connection :Unable to send request


Can someone address why the Client parameter 2/6/3 is asking for "Host Name"
over the IP Addy of the NIC/Machine that the PerProxy is located on?
I ask because I run a Client and my LAN's PerProxy on the same machine. I
have been running with all Client's parameter 2/6/3 set to the IP Addy of
the PerProxy's machine/NIC. It has been working very well.
This seems very subtle, but I don't get the significance.
Thanks,
Duncan

-----Original Message-----
From: Chuck <RC5 at atthe.net>
To: proxyper at lists.distributed.net <proxyper at lists.distributed.net>
Date: Wednesday, March 08, 2000 22:03 PM
Subject: Re: [PROXYPER] Proxy connection :Unable to send request


>This behavior resulted from client config settings
>2/6/2  auto select key server
>2/6/3 host name and
>2/6/4 port
>were set to connect directly to a key server and not to the proxy.
>so the client was looking for the key server for keys, not the proxy
>but after it connected to the key server it sent the packets through the
proxy
>because the proxy settings were set properly
>all works well now
>
>
>At 05:41 PM 3/1/00 -0800, you wrote:
>>personal proxy "ver 313 win32"
>>the problem is that the clients can ONLY connect and download  work units
>>to the proxy when that client's machine is connected
>>to the internet by modem "packets are not going out over the modem
>>connection on the client machine"  otherwise they run out of packets and
>>give this error:
>>
>>[Mar 01 07:00:08 UTC] 52 RC5 packets (189 work units) remain in
buff-in.rc5
>>[Mar 01 07:00:08 UTC] Projected ideal time to completion: 0.16:44:51.00
>>[Mar 01 07:00:08 UTC] 17 RC5 packets (64 work units) are in buff-out.rc5
>>
>>[Mar 01 07:00:45 UTC] Connected to distributed.net:80
>>                       via HTTP proxy 192.168.168.5:999
>>[Mar 01 07:00:46 UTC] FetchRC5::Unable to send request (-1.168).
>>
>>even the machine that is running the proxy has to have a modem connection
>>to get packets to and from the client
>>when each machine is connected by modem everything works perfectly
>>this seems like a DNS problem but am at a loss as how to fix it
>>
>>
>>Happy Cracking
>>Chuck at AtThe.net
>
>
>
>
>
>Enter to Win ! an Easter Basket ~ Coffee ~ Biscotti Drawing on April 12th
>Gift baskets Overflowing with Delicious Freshly-Roasted Coffee, Premium
>Euphoria Chocolates, Flavored Syrups, and other Goodies...     At way below
>retail prices !!      Visit  HTTP://www.coffeeismydrugofchoice.com  and get
>a buzz...
>--
>To unsubscribe, send 'unsubscribe proxyper' to
majordomo at lists.distributed.net
>
>

--
To unsubscribe, send 'unsubscribe proxyper' to
majordomo at lists.distributed.net


--
To unsubscribe, send 'unsubscribe proxyper' to majordomo at lists.distributed.net



More information about the proxyper mailing list