Re: paging all socket geniuses
- From: Kenny <kentilton@xxxxxxxxx>
- Date: Wed, 30 Jul 2008 02:43:08 -0400
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.
.. Note that this address doesn't seem to respond to pings, so you can kill ping once it resolves the address. Both commands should take the same time to start; if the first is slower, then it could be your DNS settings.
Try running `tracert s3.amazonaws.com` to see if one hop between the laptop and amazon is being slow.
Also compare the DNS section of the "Network settings" (control panel) against the good machines, try disabling any firewall software, and possibly even antivirus.
Ah, yes, the classic: what is different? I will eradicate everything, trembling all the while that whatever it is might be so common amongst my target audience that it may not be appropriate for real-world systems. But one working system is administered Seriously, so maybe I will be OK.
My concern is that I am doing a roll-out now and wonder how many
other people will have the same problem because of some oddity on
their system.
I get that feeling every time someone uses Windows. ;)
Another idea is to attach a C debugger to lispworks and check what system calls are taking so long.
Bartending school sounds like more fun. :)
Wireshark is an excellent packet sniffer.
Cool, that came up first in my googlery.
thx for all the good ideas,
kt
.
- Follow-Ups:
- Re: paging all socket geniuses
- From: K Livingston
- Re: paging all socket geniuses
- From: Rob Warnock
- Re: paging all socket geniuses
- References:
- paging all socket geniuses
- From: Kenny
- Re: paging all socket geniuses
- From: D Herring
- paging all socket geniuses
- Prev by Date: Re: Collecting like-labelled sublists of a list
- Next by Date: [PEPM 2009] Preliminary CFP
- Previous by thread: Re: paging all socket geniuses
- Next by thread: Re: paging all socket geniuses
- Index(es):
Relevant Pages
|
