Re: [OS2Wireless] Tracerte, Delays and Unreachable Site
Date:
Wed, 14 Apr 2010 20:04:26 -0400
To:
OS/2 Wireless Users Mailing List <os2-wireless_users@2rosenthals.com>
hi there...what is the default route on the ecs box?
what is the DNS servers on ecs set to?
On 04/14/2010 07:10 PM, Hakan wrote:
> Base Case
> I am unable to use tracerte to trace the route to salesforce.com from
> my T43p laptop running evS 1.2R connected to Verizon's network via a
> Netgear Wireless-N 300 Router (WNR2000v2) and then a Westell DSL modem.
> Tracerte does not supply me with any information after the 2nd hop
> which is the Westell modem, after that it simply displays '*' at each
> hop. Pinging salesforce.com from the same computer shows a time of 240
> ms. Browsing this particular site in Firefox 3.5.9 or 3.6.3 is slow and
> inconsistent, meaning that the pages do not always load and many
> attempts have to be made to successfully load a page. I can reach other
> websites fine. Nslookup fails with the following message:
>
> *** Can't find server name for address 10.20.30.1: Non-existent
> host/domain
> *** Default servers are not available
>
10.20.30.1 must be the netgear and looks like it is being used as a
local DNS. Where does it get DNS from?
let's tart with this stuff/
leon
> A machine running Windows connected to the same Netgear router and
> Westell DSL modem traces the route in 11 hops. Pinging salesforce.com
> shows here a consistent time of 85 ms. No problems browsing. Nslookup
> results in the same error message as above but also displays the IP
> address of salesforce.com.
>
> All of the above is also true, on both machines, when trying to reach
> the IP address, 204.14.234.33, directly.
>
> Case 2
> I connected the T43p running eCS directly to the Netgear router using a
> cable and rebooted. I am still not able to trace the route to
> salesforce.com, nor is nslookup any more helpful than above, either
> when looking up the domain or using the above IP address. However, and
> importantly, the ping time is now down to 80 ms on this system as well.
>
> The conclusion is that using this particular wireless adapter under eCS
> (and on this particular computer) results in a signficant degradation
> in latency.
>
> Scenario 3
> I now connected the T43p directly to the Westell DSL modem. The ping
> time stays at 80 ms, nslookup now works correctly (for both the domain
> and the IP address with no error messages) but tracerte still does not
> show any valid information beyond the Westell DSL modem.
>
> Can anyone suggest the reason for any or all of the above? A setting in
> the Netgear router which is not entirely compatible with eCS? An effect
> of using the Genmac driver where the communication is so slow that
> something times out at a low level? Something not compatible in the DSL
> modem or elsewhere on the Verizon network? Something else?
>
> Many thanks.
>
>
>
>
>
back to list