Icy Phoenix

     
 

Tracert - Ping Icy Phoenix

Tracert - Ping Icy Phoenix

Article
Reply with quote    Download Post  
Post Tracert - Ping Icy Phoenix 
 
There appears to be some users who are experiencing problems with the Icy Phoenix Server.

For interest - And for MG's benefit, these are the results from:

1. Online Tracert Service.

 1  75.125.232.57 (75.125.232.57)  0.474 ms  0.521 ms  0.379 ms
 2  et2-5.ibr01.hstntx1.theplanet.com (207.218.223.5)  0.489 ms  0.349 ms  0.201 ms
 3  xe-9-0-0.bar2.Houston1.Level3.net (4.78.10.29)  0.504 ms  0.360 ms  0.453 ms
 4  ae-0-11.bar1.Houston1.Level3.net (4.69.137.133)  0.464 ms  0.548 ms  0.458 ms
 5  ae-13-13.ebr1.Dallas1.Level3.net (4.69.137.138)  5.772 ms  13.666 ms  18.172 ms
 6  ae-4-90.edge2.Dallas3.Level3.net (4.69.145.204)  5.449 ms  5.431 ms  5.695 ms
 7  Tiscali-Level3.Dallas3.Level3.net (4.68.110.158)  5.687 ms  5.872 ms  5.724 ms
 8  so-2-1-0.mil19.ip4.tinet.net (213.200.81.98)  135.567 ms  135.572 ms  135.364 ms
 9  inet-gw.ip4.tinet.net (213.200.68.22)  146.063 ms  143.014 ms  143.334 ms
10  Po1.bf2-swr1.net.inet.it (212.239.110.62)  143.343 ms  145.986 ms  144.084 ms
11  po2.wf2-swr2.net.inet.it (212.239.110.94)  144.867 ms  144.765 ms  144.591 ms
12  212.239.108.194 (212.239.108.194)  144.576 ms  144.726 ms  144.578 ms
13  213.92.84.92 (213.92.84.92)  144.575 ms  145.283 ms  144.827 ms
14  evolution.supermoby.net (213.92.85.170)  144.869 ms  144.750 ms  144.817 ms


2. From Adelaide - Australia:

Tracing route to icyphoenix.com [213.92.85.170]
over a maximum of 30 hops:

  1     2 ms     1 ms    <1 ms  10.1.1.1
  2    19 ms    18 ms    18 ms  nexthop.sa.ii.net [203.173.60.88]
  3    20 ms    18 ms    18 ms  gi0-1-703.ade-pipe-bdr2.ii.net [203.215.10.10]
  4    19 ms    44 ms    19 ms  po1.ade-pipe-bdr1.iinet.net.au [203.215.20.137]
  5    48 ms    48 ms    49 ms  gi15-1-2.syd-mas-core1.iinet.net.au [203.215.20.70]
  6    48 ms    48 ms    47 ms  34023.sydp06.cu.reach.com [134.159.160.57]
  7    48 ms    48 ms    48 ms  i-10-0.sydp-core02.bi.reach.com [202.84.220.149]
  8   159 ms   163 ms   161 ms  i-3-3.siko-core01.bx.reach.com [202.84.143.150]
  9   161 ms   161 ms   160 ms  i-2-0.siko07.bi.reach.com [202.84.148.142]
 10     *        *        *     Request timed out.
 11   195 ms   197 ms   194 ms  if-15-0-0-954.core2.S9R-Singapore.as6453.net [209.58.96.97]
 12   228 ms   227 ms   227 ms  if-10-0-0.core2.CFO-Chennai.as6453.net [116.0.84.21]
 13   251 ms   251 ms   253 ms  if-11-0-0.core2.MLV-Mumbai.as6453.net [216.6.13.13]
 14   808 ms   873 ms   642 ms  if-9-0-0.mcore3.L78-London.as6453.net [216.6.13.30]
 15   406 ms   407 ms   406 ms  if-2-0-0.core3.MLT-Milan.as6453.net [195.219.158.57]
 16   408 ms   407 ms   406 ms  Port-channel1.core3.MLT-Milan.as6453.net [195.219.158.14]
 17   406 ms   406 ms   406 ms  ge3-9.wf1-gsr2.net.inet.it [212.239.110.66]
 18   417 ms   419 ms   418 ms  po2.wf2-swr2.net.inet.it [212.239.110.94]
 19   418 ms   417 ms   419 ms  212.239.108.194
 20   421 ms   419 ms     *     213.92.84.92
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.
Trace complete.



Pinging icyphoenix.com [213.92.85.170] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 213.92.85.170:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),




For those wishing to contribute to this thread, go to the Command Prompt and enter:

XP:

tracert icyphoenix.com > C:\tracert.txt - Enter (This may take a long time - be patient until it's finished).

ping icyphoenix.com > C:\ping.txt - Enter

After it's finished you should have tracert.txt and ping.txt on your c:\drive.

Vista:

tracert icyphoenix.com > tracert.txt

After it's finished you should have tracert.txt in Users\YOU\tracert.txt

Do the same with ping.



 
Last edited by Guest on Wed 26 Aug, 2009 15:39; edited 3 times in total 
   
Inactive User [ Tue 25 Aug, 2009 10:18 ]
Icy Phoenix is an open source project, you can show your appreciation and support future development by donating to the project.

Support us


Tracert - Ping Icy Phoenix

Comments
Reply with quote    Download Post  
Post Re: Tracert - Ping Icy Phoenix 
 
Thx Lopa.

This should clear thingĀ“s up a bit

this is what i got so far

 dibujo_1251198707_204296



 
spydie - View user's profile Send private message  
spydie [ Tue 25 Aug, 2009 10:24 ]
Reply with quote    Download Post  
Post Re: Tracert - Ping Icy Phoenix 
 
I must be getting old spydie, because there's an easier way to do it with DOS - That I had forgotten about.

Check out the first post.



 
   
Inactive User [ Tue 25 Aug, 2009 15:12 ]
Reply with quote    Download Post  
Post Re: Tracert - Ping Icy Phoenix 
 
Server was down again

This is the result:

 dibujo_1251283567_900910



 
spydie - View user's profile Send private message  
spydie [ Wed 26 Aug, 2009 12:46 ]
Reply with quote    Download Post  
Post Re: Tracert - Ping Icy Phoenix 
 
Thanks for reporting...

I think I will move to another server soon... we will then need to check it again.



 
Mighty Gorgon - View user's profile Send private message  
Mighty Gorgon [ Thu 27 Aug, 2009 20:41 ]
Reply with quote    Download Post  
Post Re: Tracert - Ping Icy Phoenix 
 
spydie wrote: [View Post]
Server was down again

This is the result:

 dibujo_1251283567_900910


I said that before... and there is even a worse fail regardering it, but it is not on the server itself....

And if someone not on the staff asks... "Not telling".



 
novice programmer - View user's profile Send private message  
novice programmer [ Sun 06 Sep, 2009 03:07 ]
Display posts from previous:    

HideWas this topic useful?

Post new topic  Reply to topic  Page 1 of 1