Re: paging all socket geniuses

On Jul 30, 1:43 am, Kenny <kentil...@xxxxxxxxx> wrote:
D Herring wrote:
Kenny wrote:
I sent the following to Franz but as you will see it does not look
like anything to with anything other than how badly screwed up
Windows, my laptop, or me or all three are... so what would you check
first given the following? Does the computer name coming back instead
of an IP address mean make-socket did not find... well, when I forgot
to move the ethernet cable over it rightly complained specifically
about the absence of a network... ah, but there is the local network
and the Al Gore Superhighway.  Well, I am too dumb on sockets even to
tell the monkets what to try, any guesses welcome.

Quick terms:
s3.amazonaws.com - domain name (gets looked up in DNS)
72.21.207.241 - IP address (resolved from above)
smokinjoe - network node hostname

Since the timing is consistent, I suspect a timeout somewhere in the
network stack.

The address resolution may be borked.  In a command shell, type `ping
s3.amazonaws.com`

Ok. It says it will talk to s3-1.amazonaws.com and mentions an IP
address. Then times out. The bad news is that it does this on the
machine that /can/ get to S3 as well (and I quickly dove in via the app
to confirm S3 is still up -- they have had issues lately. <g>)

So this is still interesting. HTH do the successful systems get past the
timeout, and why cannot SMOKINJOE do the same?...

...and `ping 72.21.207.241` (or whatever IP the first
ping finds).

No surprise I spose, but this too times out.


as the earlier reply pointed out:

.. Note that this address doesn't seem to respond to pings,

Ping was a nice courtesy of a tamer Internet of the past. Most
machines and firewalls are configured to block all ICMP traffic (which
is used for ping among other things) most machines no longer respond
to external ICMP requests. [wouldn't it be nice if the Internet could
just get along, and people wouldn't try to break stuff. alternately
if our programs couldn't be broken so easily too, that would also
work.]

The earlier reply was just trying to see what IP address the name was
resolved to (and make sure that was consistent), which ping tells you
before it tries to send the ping request. The more appropriate way to
identify how your computer is resolving names is to use "nslookup"
which is the *nix program name, I don't know if Windows ships with it,
but cygwin has it.
So you could do:

$>nslookup s3.amazonaws.com
Non-authoritative answer:
Server: xxx.xxx.xxxxxxxx.xxx
Address: xxx.xxx.xxx.xxx

Name: s3-1.amazonaws.com
Address: 72.21.211.100
Aliases: s3.amazonaws.com

(it tells you first who you are talking to for a DNS server (I just
blocked out mine, no need to broadcast that) and then it tells you who
that name server thinks you are referring to on the Internet at
large.)



Try running `tracert s3.amazonaws.com` to see if one hop between the
laptop and amazon is being slow.

This can tell you more than just slow - look at the paths your
multiple machines are taking. Are they the same?

The other thing not mentioned here is presumably your laptop has
multiple network interfaces? Or potentially connects to the Internet
differently than your other machines?

If so the traffic could be routed differently. For example, when I
VPN into my office, I don't have to route all of my traffic through
the VPN interface. I can set it to send only addresses that are in
work-related IP ranges through the VPN, and other requests can be sent
through the regular network interface directly to their destination
without first having to bounce through the VPN.

SO even on one machine www.google.com can work and s3-1.amazonaws.com
might not. Now these settings like I am talking about should be
regardless of what program you are using. On smokinjoe can you get to
the Amazon page with a web browser? (you said you could get to the
public internet, but weren't specific about where) It's possibly your
connection routes some traffic different, or even just drops some
traffic.

The easy way to compare bulk network settings between windows
computers is to open up an command window and run "ipconfig /all" you
should see all the network interfaces listed, and many of their
properties, like the DNS servers being used. Compare the two
computers.



Bartending school sounds like more fun. :)

Why tend? when you could bar-hop, or just bar-sit still and drink for
that matter.


good luck,
Kevin
.

Relevant Pages

  • RE: Serious Security Issue in Windows XP SP2s Firewall
    ... option to limit it to your internal network IP addresses. ... Serious Security Issue in Windows XP SP2's Firewall ... > connect to the Internet via dial-up or ISDN. ... > the dial-up connection as soon as you were connected to the Internet. ...
    (Focus-Microsoft)
  • Fw: Serious Security Issue in Windows XP SP2s Firewall
    ... Serious Security Issue in Windows XP SP2's Firewall ... > connect to the Internet via dial-up or ISDN. ... > network at home: Often, we did not even encounter password protection. ... > the dial-up connection as soon as you were connected to the Internet. ...
    (Focus-Microsoft)
  • [Full-Disclosure] RE: M$ - so what should they do?
    ... >isn't a basic windows design piece. ... or getting their machines loaded with adware and spyware ... heart of the problem of machines connected to the Internet, ...
    (Full-Disclosure)
  • Serious Security Issue in Windows XP SP2s Firewall
    ... PC-WELT discovers and fixes serious security issue in Windows XP SP2 ... Internet via dial-up or ISDN. ... Internet Connection Sharing of the PC ... network at home: Often, we did not even encounter password protection. ...
    (Bugtraq)
  • Re: upgrading frm XP Home to Pro
    ... Windows XP Home - unless ... The machines in question would access the central file repository ... Windows XP Home computers using very quickly (unless you record a lot of ... connects to the Internet, but I bet there is some sort of Cable/DSL Router ...
    (microsoft.public.windowsxp.general)