Re: Runes of Magic ClientUpdate.exe crash???

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 2011-01-30 at 21:38 -0600, Astrauk wrote:
> Ok it said there was 100% data loss when I used ping, and when I used traceroute I got this.
> 
> 
> Code:
> Astrauks-MacBook-Pro:~ Astrauk$ traceroute rom-enus-srv.runewaker.com
> traceroute to rom-enus-srv.runewaker.com (64.127.104.210), 64 hops max, 52 byte packets
>  1  192.168.224.31 (192.168.224.31)  1.442 ms  0.758 ms  0.670 ms
>  2  76.33.0.1 (76.33.0.1)  6.956 ms  9.469 ms  43.974 ms
>  3  gig6-1.brfdwijana-rtr3.wi.rr.com (24.160.228.12)  9.801 ms  104.909 ms  52.515 ms
>  4  tge1-0-0.milwwirtco-rtr1.wi.rr.com (24.160.229.96)  8.717 ms  15.032 ms  16.324 ms
>  5  tge3-0-0.chcgil3-rtr0.mwrtn.rr.com (24.160.229.77)  131.071 ms  132.033 ms  137.528 ms
>  6  ae-6-0.cr0.chi30.tbone.rr.com (66.109.6.206)  126.918 ms  150.093 ms  128.617 ms
>  7  ae-1-0.pr0.chi10.tbone.rr.com (66.109.6.155)  154.172 ms  125.661 ms  127.906 ms
>  8  xe-10-3-0.edge2.chicago2.level3.net (4.59.28.113)  147.887 ms
>     xe-10-1-0.edge2.chicago2.level3.net (4.59.28.105)  142.363 ms  147.769 ms
>  9  vlan51.ebr1.chicago2.level3.net (4.69.138.158)  166.357 ms  163.056 ms  173.648 ms
> 10  ae-3-3.ebr2.denver1.level3.net (4.69.132.61)  73.036 ms  50.494 ms  106.316 ms
> 11  ae-1-100.ebr1.denver1.level3.net (4.69.132.37)  180.026 ms  174.283 ms  185.668 ms
> 12  ae-3-3.ebr2.sanjose1.level3.net (4.69.132.57)  412.023 ms  191.120 ms  185.051 ms
> 13  ae-1-6.bar2.sanfrancisco1.level3.net (4.69.140.153)  185.332 ms  181.529 ms  182.166 ms
> 14  ae-0-11.bar1.sanfrancisco1.level3.net (4.69.140.145)  77.351 ms  88.206 ms  60.153 ms
> 15  ae-4-4.car1.sanfrancisco1.level3.net (4.69.133.149)  194.303 ms  193.426 ms  192.172 ms
> 16  global-neto.car1.sanfrancisco1.level3.net (4.53.128.54)  188.662 ms  183.659 ms  183.854 ms
> 17  dvb-01.te-2-1.sfo1.gni.com (64.127.96.18)  195.123 ms  178.956 ms  183.238 ms
> 18  * * *
> 19  * * *
> 20  * * *
> 21  * * *
> 22  * * *
> 23  * * *
> ^C
> 
That looks like a network problem in San Francisco to me: as you can
see, the route was OK through Chicago and Denver to San Francisco.

I'd say there's some sort of network problem at runewaker.com. Running
traceroute here gets the same result as you saw. Nmap thinks
rom-enus-srv.runewaker.com is down. It could be something flaky at
NetworkSolutions, their domain host, because another NetworkSolutions
customer (Bob Cringely, the tech. blogger) is spitting tacks at their
(lack of) competence and technical support and is in the process of
moving himself elsewhere ASAP.
 
The runewaker ddmin and technical contact is

      Tang, John		john@xxxxxxxxxxxxxx
      3240 Woodbine Road
      Orange, CA 92867
      US
      714-637-3932 fax: 714-637-2803

should you want to talk to them.


Martin





[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux