Ahh - Hmm - my apologies for wasting anyone (and everyone's time). At the
very beginning I had asked the client

ME: "Are you using any type of proxy?"
THEM: "No"
ME: "Are you sure?"
THEM: "Yes"

Then some of our tech guys got access and also missed this (although I had
never told them to look for and examine the environment variables). Anyhow,
I finally got telnet access to the server in question. I checked the
environment variables - simply as a standard thing to do and ... they had
HTTP_PROXY and NO_PROXY set such that curl was trying to do what the
environment variables asked it to do. Therefore, the error message
CURLE_COULDNT_RESOLVE_PROXY makes immense sense since the cause was, indeed,
a proxy failure.

Anyway, thanks for all the help,

Joel

-----Original Message-----
From: Daniel Stenberg [mailto:daniel_at_haxx.se]
Sent: Wednesday, April 09, 2003 1:43 PM
To: libcurl Mailing list
Subject: RE: CURLE_COULDNT_RESOLVE_PROXY and BigIP and clustering

On Wed, 9 Apr 2003, Themmen, Joel wrote:

[quote edited]

> telnet bus-is1-vnd4a.ntrs.com 3525
>
> telnet 192.168.150.61 3525
>
> I went into Internet explorer and typed:
>
> http://bus-is1-vnd4a.ntrs.com:3525/npo.tnt/contactlist
>
> http://192.168.150.61:3525/npo.tnt/contactlist
>
> lynx http://bus-is1-vnd4a.ntrs.com:3525/npo.tnt/contactlist
>
> Then I tried:
>
> lynx http://192.168.150.61:3525/npo.tnt/contactlist
>
> And got a "Alert: Could not connect" error. This is bad.

When this failed, could you do the first telnet-to-IP again with success?

It would surprise me. I think that the load balancer gave you another IP
address for that final lynx command line with name, and then the final
command failed since that IP was no longer the one in use for the name. Or
something similar.

If lynx failed to connect, then darnit, telnet shouldn't either. And vice
versa.

So, again (I don't quite remember the initial error case anymore! is this
age
showing? ;-)), if you instead run a curl command line instead of that
initial
command line, like:

 curl http://bus-is1-vnd4a.ntrs.com:3525/npo.tnt/contactlist

What does it say?

-- 
 Daniel Stenberg -- curl, cURL, Curl, CURL. Groks URLs.
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger 
for complex code. Debugging C/C++ programs can leave you feeling lost and 
disoriented. TotalView can help you find your way. Available on major UNIX 
and Linux platforms. Try it free. www.etnus.com