Jump to content

Can one of you geniuses tell me what's going on here?


o3Nicky

Recommended Posts

Tracing route to 192.205.33.186 over a maximum of 30 hops

  1    1 ms    1 ms    1 ms  192.168.1.1

  2    17 ms    20 ms    20 ms  lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]

  3  386 ms    15 ms    17 ms  ge1-0-0-204.ptn-gw1.plus.net [84.92.3.105]

  4    15 ms    17 ms    19 ms  ge-4-1.metro2-londencyh00.London1.Level3.net [21

2.113.11.41]

  5    34 ms    31 ms    31 ms  so-1-2-0.gar2.London1.Level3.net [212.113.0.118]

  6    18 ms    19 ms    21 ms  ae-0-54.bbr2.London1.Level3.net [4.68.116.98]

  7    84 ms    82 ms    82 ms  as-0-0.bbr1.NewYork1.Level3.net [4.68.128.106]

  8    84 ms    84 ms    88 ms  ae-13-51.car3.NewYork1.Level3.net [4.68.97.18]

  9    85 ms    86 ms    84 ms  ggr2-p360.n54ny.ip.att.net [192.205.33.93]

10    86 ms    86 ms    88 ms  tbr1-p032501.n54ny.ip.att.net [12.123.0.90]

11  ggr1-p360.n54ny.ip.att.net [12.123.0.57]  reports: Destination host unreachable.

odd that u go via that router

it should really route somewher eelse

try contacting att and tell them they got some problem in their routing

was just joking,

but no u cant control where ur packed go after the 1st hop

Link to comment
Share on other sites

This is what I get from Kentucky

Tracing route to cod.onfyre.net [8.2.0.172]

over a maximum of 30 hops:

  1    *        *        *    Request timed out.

  2    11 ms    10 ms    12 ms  74.128.19.241

  3    13 ms    11 ms    12 ms  74.128.16.85

  4    22 ms    13 ms    14 ms  74.128.8.97

  5    24 ms    26 ms    23 ms  so-7-1-0.gar2.Atlanta1.Level3.net [4.78.214.17]

  6    23 ms    32 ms    *    ae-32-54.ebr2.Atlanta2.Level3.net [4.68.103.126]

  7    66 ms    27 ms    *    ae-1.ebr1.Atlanta2.Level3.net [4.69.132.33]

  8    46 ms    43 ms    45 ms  ae-3.ebr1.Dallas1.Level3.net [4.69.132.81]

  9    45 ms    42 ms    57 ms  ae-12-55.car2.Dallas1.Level3.net [4.68.122.142]

10    43 ms    45 ms    42 ms  8.2.0.172

Trace complete.

C:Documents and SettingsKathleen>

Link to comment
Share on other sites

this is what i get  when i run a trace to it.

C:Documents and SettingsDonovan M. Lewis>tracert 192.205.33.186

Tracing route to 192.205.33.186 over a maximum of 30 hops

  1    1 ms    <1 ms    <1 ms  192.168.1.1

  2    11 ms    *        9 ms  65.14.252.1

  3    8 ms    9 ms    9 ms  65.14.254.93

  4    10 ms    10 ms    9 ms  66.156.253.25

  5    10 ms    11 ms    10 ms  65.83.237.136

  6    11 ms    10 ms    14 ms  65.83.236.11

  7    13 ms    9 ms    10 ms  65.83.236.20

  8    24 ms    24 ms    24 ms  65.57.174.1

  9    24 ms    72 ms    23 ms  4.68.112.45

10    41 ms    42 ms    42 ms  4.68.128.210

11    40 ms    40 ms    42 ms  4.68.121.144

12    42 ms    42 ms    42 ms  4.68.127.154

13    44 ms    43 ms    43 ms  12.123.8.114

14  12.123.8.153  reports: Destination host unreachable.

Trace complete.

Link to comment
Share on other sites

192.205.33.186

OrgName:    AT&T Bell Laboratories

OrgID:      ATT

Address:    3200 Lake Emma Road

City:      Lake Mary

StateProv:  FL

PostalCode: 32746

Country:    US

NetRange:  192.205.0.0 - 192.205.255.255

CIDR:      192.205.0.0/16

NetName:    NETBLK-ATT

NetHandle:  NET-192-205-0-0-1

Parent:    NET-192-0-0-0-0

NetType:    Direct Allocation

NameServer: OHCU.OH.MT.NP.ELS-GMS.ATT.NET

NameServer: WYCU.WY.BR.NP.ELS-GMS.ATT.NET

NameServer: MACU.MA.MT.NP.ELS-GMS.ATT.NET

Comment:   

RegDate:    1992-08-03

Updated:    1997-11-04

RTechHandle: JD2290-ARIN

RTechName:  Davis, John

RTechPhone:  +1-513-352-7285

RTechEmail:  [email protected]

OrgTechHandle: IAA8-ARIN

OrgTechName:  IP Address Administrator

OrgTechPhone:  +1-407-805-7323

OrgTechEmail:  [email protected]

  ARIN WHOIS database, last updated 2006-05-27 19:10

  Enter ? for additional hints on searching ARIN's WHOIS database.

and shug7272, you ARE A genius, but don't tell anyone

Link to comment
Share on other sites

Can you guys ping cod.onfyre.net ? How come I've never had to go through a router like (192.205.xx.xxx) to get anywhere?

It seems like it shouldn't be there.

OrgName:    Level 3 Communications, Inc.

OrgID:      LVLT

Address:    1025 Eldorado Blvd.

City:      Broomfield

StateProv:  CO

PostalCode: 80021

Country:    US

NetRange:  8.0.0.0 - 8.255.255.255

CIDR:      8.0.0.0/8

NetName:    LVLT-ORG-8-8

NetHandle:  NET-8-0-0-0-1

Parent:   

NetType:    Direct Allocation

NameServer: NS1.LEVEL3.NET

NameServer: NS2.LEVEL3.NET

Comment:   

RegDate:   

Updated:    2004-06-04

OrgAbuseHandle: APL8-ARIN

OrgAbuseName:  Abuse POC LVLT

OrgAbusePhone:  +1-877-453-8353

OrgAbuseEmail:  [email protected]

OrgTechHandle: ARINC4-ARIN

OrgTechName:  ARIN Contact

OrgTechPhone:  +1-800-436-8489

OrgTechEmail:  [email protected]

OrgTechHandle: TPL1-ARIN

OrgTechName:  Tech POC LVLT

OrgTechPhone:  +1-877-453-8353

OrgTechEmail:  [email protected]

  ARIN WHOIS database, last updated 2006-07-16 19:10

  Enter ? for additional hints on searching ARIN's WHOIS database.

Link to comment
Share on other sites

What it looks like to me is a bad link between 2 routers (12.123.6.37 & 192.205.33.186) within the AT&T network.  This usually indicates that there is some load balancing occuring, which usually means that some devices are down due to maintenance.  This sort of thing usually clears up within 48 hours.  I would suggest performing another trace after 48 hours, and if this is not cleared up by then, call your ISP. 

On occassion, my ISP has not helped me with similar issues, because after a certain point, they will claim that it is outside of their network.  In this instance, you would have to contact the NOC of the network directly.  WaterRTBH has provided their contact from the WHOIS information.  Just provide them with a trace.  But be sure to give it enough time to rule out a maintenance window.

Link to comment
Share on other sites

What it looks like to me is a bad link between 2 routers (12.123.6.37 & 192.205.33.186) within the AT&T network.  This usually indicates that there is some load balancing occuring, which usually means that some devices are down due to maintenance.  This sort of thing usually clears up within 48 hours.  I would suggest performing another trace after 48 hours, and if this is not cleared up by then, call your ISP. 

On occassion, my ISP has not helped me with similar issues, because after a certain point, they will claim that it is outside of their network.  In this instance, you would have to contact the NOC of the network directly.  WaterRTBH has provided their contact from the WHOIS information.  Just provide them with a trace.  But be sure to give it enough time to rule out a maintenance window.

You made me look smart, I want to hump your leg now :P

any luck yet o3Nicky ??

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...