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