Or more apropos to the concurrent threads...pong :-]

-----Original Message-----
From: David Mazzaccaro [mailto:[email protected]] 
Sent: Tuesday, July 24, 2012 12:43 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

Like a tennis match.


-----Original Message-----
From: Steve Kradel [mailto:[email protected]]
Sent: Tuesday, July 24, 2012 3:30 PM
To: NT System Admin Issues
Subject: Re: help w/ tracert

Routing loops are not that unusual when folks get to (badly) configuring 
routing, although it's most unfortunate when absolutely all your outbound 
traffic gets stuck in the loop...
When a.b.c.13 has a.b.c.14 as its default gateway, and a.b.c.14 has
a.b.c.13 as *its* default gw... there ya go.

--Steve

On Tue, Jul 24, 2012 at 2:18 PM, Ziots, Edward <[email protected]>
wrote:
> Routing issue in FW probably
>
>
>
> Z
>
>
>
> Edward E. Ziots, CISSP, Security +, Network +
>
> Security Engineer
>
> Lifespan Organization
>
> [email protected]
>
>
>
> From: David Mazzaccaro [mailto:[email protected]]
> Sent: Tuesday, July 24, 2012 1:44 PM
>
>
> To: NT System Admin Issues
> Subject: help w/ tracert
>
>
>
> When I run a tracert to google, here are the results... any
suggestions from
> the group?
>
> Its like it just bounces between these two hosts...
>
> Tracing route to google.com [74.125.224.161]
>
> over a maximum of 30 hops:
>
>   1     1 ms    <1 ms    <1 ms  {local IP Address removed}
>
>   2     3 ms     3 ms     3 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   3     4 ms     4 ms     4 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>   4     7 ms     8 ms     7 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   5     7 ms     7 ms     7 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>   6    10 ms    10 ms    10 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   7    10 ms    10 ms    11 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>   8    13 ms    13 ms    13 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   9    14 ms    14 ms    28 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  10    17 ms    17 ms    17 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  11    17 ms    17 ms    17 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  12    20 ms    20 ms    20 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  13    24 ms    20 ms    20 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  14    32 ms    37 ms    24 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  15    24 ms    24 ms    35 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  16    28 ms    26 ms    26 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  17    27 ms    27 ms    27 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  18    30 ms    31 ms    31 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  19    31 ms    30 ms    32 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  20    33 ms    33 ms    33 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  21    34 ms    38 ms    34 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  22    37 ms    52 ms    37 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  23    37 ms    37 ms    37 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  24    40 ms    41 ms    40 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  25    41 ms    42 ms    41 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  26    50 ms    43 ms    43 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  27    44 ms    44 ms    44 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  28    60 ms    47 ms    64 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  29    47 ms    47 ms    48 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  30    52 ms    50 ms    51 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
> Trace complete.
>
>
> .
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to [email protected]
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here:
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin


.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to [email protected]
with the body: unsubscribe ntsysadmin

Reply via email to