From: "Sam Lewis" <os2-wireless_users@2rosenthals.com>
MIME-Version: 1.0
In-Reply-To: <list-2372006@2rosenthals.com>
References: <list-2372006@2rosenthals.com>
Date: Wed, 14 Apr 2010 22:56:15 -0500
Message-ID: <m2w438498021004142056h12841fe6g72c9147416657d61@mail.gmail.com>
Subject: Re: [OS2Wireless] Tracerte, Delays and Unreachable Site
To: "OS/2 Wireless Users Mailing List" <os2-wireless_users@2rosenthals.com>
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Apr 14, 2010 at 8:45 PM, Hakan
<os2-wireless_users@2rosenthals.com> wrote:
> Yes but in my e-mail I gave information for the eCS box /and/ a Win box
> in the same location - both should use the same DNS server since it is
> supplied by the Netgear/Westell. Also, did both of you read through the
> other two cases which sheds additional light on the problem?

Well we/I don't know that your different computers and even different
Ethernet interfaces are using the same DNS servers.  You can
statically assign DNS servers to each interface, wired and wireless.
So it may be possible that each computer/OS you are using as well as
each interface has a different DNS server setup.  I would at least
verify what each interface and OS is using.

Or your router could be getting bogged down for some reason that may
not be clear which could cause the high latency.

Now for your trace route problem I haven't a clue why the one in OS/2
doesn't work.  All trace route does is send an ICMP packet to the
destination starting with a TTL of 1 and then incrementing by one for
each hop until it finally reaches the destination and displays
information for each hop.  So it is a mystery to me why trace route
would work on one OS but not the other.  If a piece of gear was
configured to not respond to ICMP packets then you should just get the
* and it should move on to the next hop after a timeout regardless of
what OS it was run under.

The evidence you provided seems to lead to DNS server's, or the router
CPU being loaded down in one configuration IF it is handling the DNS
for your network.

I could be completely off base and be missing something.  But I don't
know what router setting would effect latency between pinging an IP
address vs. domain name or discriminate between Wired and Wireless
interfaces.  Also if your router is handling DNS I would not allow
that.  I had recently had issues with the CPU being loaded down on a
Linksys router at one location and when put in a different location
doing the same thing it wasn't loaded down, so it is possible for
consumer grade routers to get bogged down when you least expect it.
My two cents worth,
Sam

P.S.  I just reread your base case.  Are you saying that you got the
same results when using IP Address vs. domain name?  At any rate I
think the trace route and you latency/reliability issues are two
separate things.
Sam