On 10/18/2012 11:35 PM, Bob Goodwin - Zuni, Virginia, USA wrote:
On 18/10/12 10:24, Ed Greshko wrote:
> Did you try....
>
> telnet
newegg.com 80
>
telnet
newegg.com 80 paralyzes the terminal, just sits there:
bobg@box9 ~]$ telnet
newegg.com 80
Trying 208.91.197.27...
Connected to
newegg.com.
Escape character is '^]'.
^C^[\
This is *correct* behavior. It shows you can connect to port 80 (http) of newegg. You
should simply do CTRL-] to "un-paralyse" your terminal.
[bobg@box9 ~]$ telnet
newegg.com
Trying 208.91.197.27...
telnet: connect to address 208.91.197.27: Connection timed out
That too is normal...since you would not expect them to accept telnet service connects on
the default port of 23.
[bobg@box9 ~]$ wget
http://secure.newegg.com/test.aspx
--2012-10-18 10:53:18--
http://secure.newegg.com/test.aspx
Resolving secure.newegg.com... 208.91.197.27
Connecting to secure.newegg.com|208.91.197.27|:80... connected.
HTTP request sent, awaiting response... 200 OK
OK.... Now this I find "interesting" ....
On your system
secure.newegg.com seems to resolve to 208.91.197.27 while on my system it
resolves to 204.14.213.188.
and....
[egreshko@meimei ~]$ host 208.91.197.27
;; connection timed out; no servers could be reached
what is your resolv.conf set to?
--
Programming today is a race between software engineers striving to build bigger and better
idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far,
the Universe is winning. -- Rick Cook, The Wizardry Compiled