RE: help w/ tracert

2012-07-25 Thread David Mazzaccaro 
LOL


-Original Message-
From: Ben Scott [mailto:mailvor...@gmail.com] 
Sent: Wednesday, July 25, 2012 7:33 AM
To: NT System Admin Issues
Subject: Re: help w/ tracert

On Tue, Jul 24, 2012 at 11:59 PM, Daniel Chenault
 wrote:
>>> Paetec has a routing issue. But you already knew that.
>>
>>   Daniel wins the thread.  :-)
>
> Do I get a prize? Bottle of tequila?

  One month of free Internet service from Paetec.

-- Ben

~ 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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: help w/ tracert

2012-07-25 Thread Ben Scott 
On Tue, Jul 24, 2012 at 11:59 PM, Daniel Chenault
 wrote:
>>> Paetec has a routing issue. But you already knew that.
>>
>>   Daniel wins the thread.  :-)
>
> Do I get a prize? Bottle of tequila?

  One month of free Internet service from Paetec.

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

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

RE: help w/ tracert

2012-07-24 Thread Daniel Chenault 
Do I get a prize? Bottle of tequila? 

-Original Message-
From: Ben Scott [mailto:mailvor...@gmail.com] 
Sent: Tuesday, July 24, 2012 5:00 PM
To: NT System Admin Issues
Subject: Re: help w/ tracert

On Tue, Jul 24, 2012 at 1:47 PM, Daniel Chenault  
wrote:
> Paetec has a routing issue. But you already knew that.

  Daniel wins the thread.  :-)

-- Ben

~ 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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Re: help w/ tracert

2012-07-24 Thread Ben Scott 
On Tue, Jul 24, 2012 at 1:47 PM, Daniel Chenault
 wrote:
> Paetec has a routing issue. But you already knew that.

  Daniel wins the thread.  :-)

-- Ben

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

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

RE: help w/ tracert

2012-07-24 Thread Kim Longenbaugh 
There must be a typo in the review, because it says the book was written in 
1933.  If that's true, then the book is not an allegory, but rather some 
stunning prophecy.

TCP wasn't even a gleam in DARPA's momma's eye in 1933.

Of course, I'm relying on Wikipedia for my information about PING and TCP/IP, 
it could be off a few years.

-Original Message-
From: Yergeau, Tom [mailto:tyerg.itm...@gmail.com] 
Sent: Tuesday, July 24, 2012 3:37 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

Which can't but bring to mind the excellent review of Ping the Duck on
Amazon, wherein John Fracisco explains how the children's story is really a
brilliant allegory for the ping utility:
http://www.amazon.com/review/R2VDKZ4X1F992Q

Warning: The review has some anti-Windows comments in it.  But still worth
reading!


-Original Message-
From: Free, Bob [mailto:r...@pge.com] 
Sent: Tuesday, July 24, 2012 4:14 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

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

-Original Message-
From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
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:skra...@zetetic.net]
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 
wrote:
> Routing issue in FW probably
>
>
>
> Z
>
>
>
> Edward E. Ziots, CISSP, Security +, Network +
>
> Security Engineer
>
> Lifespan Organization
>
> ezi...@lifespan.org
>
>
>
> From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
> 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]
>
>   610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>   813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.

RE: help w/ tracert

2012-07-24 Thread Yergeau, Tom 
Which can't but bring to mind the excellent review of Ping the Duck on
Amazon, wherein John Fracisco explains how the children's story is really a
brilliant allegory for the ping utility:
http://www.amazon.com/review/R2VDKZ4X1F992Q

Warning: The review has some anti-Windows comments in it.  But still worth
reading!


-Original Message-
From: Free, Bob [mailto:r...@pge.com] 
Sent: Tuesday, July 24, 2012 4:14 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

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

-Original Message-
From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
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:skra...@zetetic.net]
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 
wrote:
> Routing issue in FW probably
>
>
>
> Z
>
>
>
> Edward E. Ziots, CISSP, Security +, Network +
>
> Security Engineer
>
> Lifespan Organization
>
> ezi...@lifespan.org
>
>
>
> From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
> 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]
>
>   610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>   813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net
>

RE: help w/ tracert

2012-07-24 Thread David Mazzaccaro 
Good to hear.

I'll keep my fingers crossed that we start seeing an improvement.

 

 

From: John Cook [mailto:john.c...@pfsf.org] 
Sent: Tuesday, July 24, 2012 4:17 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

We ended up saving a lot of money on our connection services from the
buyout, we've not (knock on wood) seen any issues since the takeover.

 

 John W. Cook

Network Operations Manager

Partnership For Strong Families

5950 NW 1st Place

Gainesville, Fl 32607

Office (352) 244-1610

Cell (352) 215-6944

MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
Sent: Tuesday, July 24, 2012 4:00 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

It was never like this when they were Paetec.  They were bought by
Windstream and have gone completely downhill.

Of course, that was after we re-signed for 3 years... naturally.

 

 

From: Ziots, Edward [mailto:ezi...@lifespan.org] 
Sent: Tuesday, July 24, 2012 3:39 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

ROFL... that is utterly sad, but definitely not untypical.

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
Sent: Tuesday, July 24, 2012 3:21 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

It was Paetec (Windstream).

They weren't routing appropriately.  Only took them 6 hours to figure
that out.

 

 

 

From: Ziots, Edward [mailto:ezi...@lifespan.org] 
Sent: Tuesday, July 24, 2012 2:19 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

Routing issue in FW probably 

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
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]

  610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

  813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 3052 ms50 ms51 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

Trace com

RE: help w/ tracert

2012-07-24 Thread David Mazzaccaro 
Touché


-Original Message-
From: Free, Bob [mailto:r...@pge.com] 
Sent: Tuesday, July 24, 2012 4:14 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

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

-Original Message-
From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
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:skra...@zetetic.net]
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 
wrote:
> Routing issue in FW probably
>
>
>
> Z
>
>
>
> Edward E. Ziots, CISSP, Security +, Network +
>
> Security Engineer
>
> Lifespan Organization
>
> ezi...@lifespan.org
>
>
>
> From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
> 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]
>
>   610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>   813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  3052 ms50 ms51 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-Ente

RE: help w/ tracert

2012-07-24 Thread Ziots, Edward 
Yeah don't worry we used Paetec also so I am sure we will see the same
stuff...

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
Sent: Tuesday, July 24, 2012 4:00 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

It was never like this when they were Paetec.  They were bought by
Windstream and have gone completely downhill.

Of course, that was after we re-signed for 3 years... naturally.

 

 

From: Ziots, Edward [mailto:ezi...@lifespan.org] 
Sent: Tuesday, July 24, 2012 3:39 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

ROFL... that is utterly sad, but definitely not untypical.

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
Sent: Tuesday, July 24, 2012 3:21 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

It was Paetec (Windstream).

They weren't routing appropriately.  Only took them 6 hours to figure
that out.

 

 

 

From: Ziots, Edward [mailto:ezi...@lifespan.org] 
Sent: Tuesday, July 24, 2012 2:19 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

Routing issue in FW probably 

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
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]

  610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

  813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 3052 ms50 ms51 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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN&

RE: help w/ tracert

2012-07-24 Thread John Cook 
We ended up saving a lot of money on our connection services from the buyout, 
we've not (knock on wood) seen any issues since the takeover.

 John W. Cook
Network Operations Manager
Partnership For Strong Families
5950 NW 1st Place
Gainesville, Fl 32607
Office (352) 244-1610
Cell (352) 215-6944
MCSE, MCP+I, MCTS, CompTIA A+, N+, VSP4, VTSP4

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
Sent: Tuesday, July 24, 2012 4:00 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

It was never like this when they were Paetec.  They were bought by Windstream 
and have gone completely downhill.
Of course, that was after we re-signed for 3 years... naturally.


From: Ziots, Edward [mailto:ezi...@lifespan.org]
Sent: Tuesday, July 24, 2012 3:39 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

ROFL... that is utterly sad, but definitely not untypical.

Z

Edward E. Ziots, CISSP, Security +, Network +
Security Engineer
Lifespan Organization
ezi...@lifespan.org<mailto:ezi...@lifespan.org>

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
Sent: Tuesday, July 24, 2012 3:21 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

It was Paetec (Windstream).
They weren't routing appropriately.  Only took them 6 hours to figure that out.



From: Ziots, Edward [mailto:ezi...@lifespan.org]
Sent: Tuesday, July 24, 2012 2:19 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

Routing issue in FW probably

Z

Edward E. Ziots, CISSP, Security +, Network +
Security Engineer
Lifespan Organization
ezi...@lifespan.org<mailto:ezi...@lifespan.org>

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
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]

  610 ms10 ms10 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

  710 ms10 ms11 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

  813 ms13 ms13 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

  914 ms14 ms28 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 1017 ms17 ms17 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 1117 ms17 ms17 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 1220 ms20 ms20 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 1324 ms20 ms20 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 1432 ms37 ms24 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 1524 ms24 ms35 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 1628 ms26 ms26 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 1727 ms27 ms27 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 1830 ms31 ms31 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 1931 ms30 ms32 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 2033 ms33 ms33 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 2134 ms38 ms34 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 2237 ms52 ms37 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 2337 ms37 ms37 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 2440 ms41 ms40 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 2541 ms42 ms41 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 2650 ms43 ms43 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 2744 ms44 ms44 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 2860 ms47 ms64 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 2947 ms47 ms48 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 3052 ms50 ms51 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 subscrip

RE: help w/ tracert

2012-07-24 Thread Free, Bob 
Or more apropos to the concurrent threads...pong :-]

-Original Message-
From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
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:skra...@zetetic.net]
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 
wrote:
> Routing issue in FW probably
>
>
>
> Z
>
>
>
> Edward E. Ziots, CISSP, Security +, Network +
>
> Security Engineer
>
> Lifespan Organization
>
> ezi...@lifespan.org
>
>
>
> From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
> 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]
>
>   610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>   813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  3052 ms50 ms51 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 listmana...@lyris.sunbeltso

RE: help w/ tracert

2012-07-24 Thread David Mazzaccaro 
It was never like this when they were Paetec.  They were bought by
Windstream and have gone completely downhill.

Of course, that was after we re-signed for 3 years... naturally.

 

 

From: Ziots, Edward [mailto:ezi...@lifespan.org] 
Sent: Tuesday, July 24, 2012 3:39 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

ROFL... that is utterly sad, but definitely not untypical.

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
Sent: Tuesday, July 24, 2012 3:21 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

It was Paetec (Windstream).

They weren't routing appropriately.  Only took them 6 hours to figure
that out.

 

 

 

From: Ziots, Edward [mailto:ezi...@lifespan.org] 
Sent: Tuesday, July 24, 2012 2:19 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

Routing issue in FW probably 

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
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]

  610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

  813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 3052 ms50 ms51 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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunb

RE: help w/ tracert

2012-07-24 Thread David Mazzaccaro 
Like a tennis match.


-Original Message-
From: Steve Kradel [mailto:skra...@zetetic.net] 
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 
wrote:
> Routing issue in FW probably
>
>
>
> Z
>
>
>
> Edward E. Ziots, CISSP, Security +, Network +
>
> Security Engineer
>
> Lifespan Organization
>
> ezi...@lifespan.org
>
>
>
> From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
> 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]
>
>   610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>   813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  3052 ms50 ms51 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 listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
>

~ Finally, powerful endpo

RE: help w/ tracert

2012-07-24 Thread Ziots, Edward 
ROFL... that is utterly sad, but definitely not untypical.

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
Sent: Tuesday, July 24, 2012 3:21 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

It was Paetec (Windstream).

They weren't routing appropriately.  Only took them 6 hours to figure
that out.

 

 

 

From: Ziots, Edward [mailto:ezi...@lifespan.org] 
Sent: Tuesday, July 24, 2012 2:19 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

Routing issue in FW probably 

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
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]

  610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

  813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 3052 ms50 ms51 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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbel

Re: help w/ tracert

2012-07-24 Thread Steve Kradel 
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  wrote:
> Routing issue in FW probably
>
>
>
> Z
>
>
>
> Edward E. Ziots, CISSP, Security +, Network +
>
> Security Engineer
>
> Lifespan Organization
>
> ezi...@lifespan.org
>
>
>
> From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
> 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]
>
>   610 ms10 ms10 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   710 ms10 ms11 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>   813 ms13 ms13 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>   914 ms14 ms28 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1017 ms17 ms17 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1117 ms17 ms17 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1220 ms20 ms20 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1324 ms20 ms20 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1432 ms37 ms24 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1524 ms24 ms35 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1628 ms26 ms26 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1727 ms27 ms27 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  1830 ms31 ms31 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  1931 ms30 ms32 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2033 ms33 ms33 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2134 ms38 ms34 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2237 ms52 ms37 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2337 ms37 ms37 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2440 ms41 ms40 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2541 ms42 ms41 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2650 ms43 ms43 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2744 ms44 ms44 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  2860 ms47 ms64 ms  63-138-116-13.customer.static.ip.paetec.net
> [63.138.116.13]
>
>  2947 ms47 ms48 ms  63-138-116-14.customer.static.ip.paetec.net
> [63.138.116.14]
>
>  3052 ms50 ms51 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! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

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

RE: help w/ tracert

2012-07-24 Thread David Mazzaccaro 
It was Paetec (Windstream).

They weren't routing appropriately.  Only took them 6 hours to figure
that out.

 

 

 

From: Ziots, Edward [mailto:ezi...@lifespan.org] 
Sent: Tuesday, July 24, 2012 2:19 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

Routing issue in FW probably 

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
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]

  610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

  813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 3052 ms50 ms51 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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

RE: help w/ tracert

2012-07-24 Thread Ziots, Edward 
Routing issue in FW probably 

 

Z

 

Edward E. Ziots, CISSP, Security +, Network +

Security Engineer

Lifespan Organization

ezi...@lifespan.org

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
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]

  610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

  813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 3052 ms50 ms51 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! ~
~   ~

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


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

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

RE: help w/ tracert

2012-07-24 Thread David Mazzaccaro 
Correct.  

Internet is down for all my remote locations.  

They all come back here via the Paetec (Windstream) MPLS network to go out 
through COX.

 

This is how it is supposed to work:

Remote office requests google.com>goes out their router>over the MPLS 
network>to Newington’s router>passes to Newington’s firewall>Cox internet

 

 

 

 

 

From: Richard Stovall [mailto:rich...@gmail.com] 
Sent: Tuesday, July 24, 2012 1:59 PM
To: NT System Admin Issues
Subject: Re: help w/ tracert

 

What prompted the trace?  Is your Internet service down?  Is Paetec your ISP?  
Your e-mail looks to have originated from 98.172.163.12, a Cox ip.

On Tue, Jul 24, 2012 at 1:43 PM, David Mazzaccaro 
 wrote:

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 <http://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 
<http://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 
<http://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 
<http://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 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

  610 ms10 ms10 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

  710 ms10 ms11 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

  813 ms13 ms13 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

  914 ms14 ms28 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

 1017 ms17 ms17 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

 1117 ms17 ms17 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

 1220 ms20 ms20 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

 1324 ms20 ms20 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

 1432 ms37 ms24 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

 1524 ms24 ms35 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

 1628 ms26 ms26 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

 1727 ms27 ms27 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

 1830 ms31 ms31 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

 1931 ms30 ms32 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

 2033 ms33 ms33 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

 2134 ms38 ms34 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

 2237 ms52 ms37 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

 2337 ms37 ms37 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

 2440 ms41 ms40 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

 2541 ms42 ms41 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

 2650 ms43 ms43 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

 2744 ms44 ms44 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.14  ]

 2860 ms47 ms64 ms  63-138-116-13.customer.static.ip.paetec.net 
<http://customer.static.ip.paetec.net/>  [63.138.116.13  ]

 2947 ms47 ms48 ms  63-138-116-14.customer.static.ip.paetec.net 
<http://customer.st

RE: help w/ tracert

2012-07-24 Thread David Mazzaccaro 
That's what I figured... Paetec is now Windstream and OH BOY what a
disaster...

They were telling me it's my firewall blocking traffic... then my
router, now admitting they have the wrong routes.

Ridiculous.

 

 

 

From: Daniel Chenault [mailto:dchena...@lgnetworksinc.com] 
Sent: Tuesday, July 24, 2012 1:47 PM
To: NT System Admin Issues
Subject: RE: help w/ tracert

 

Paetec has a routing issue. But you already knew that.

 

Daniel Chenault

dchena...@lgnetworksinc.com

 

 

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com] 
Sent: Tuesday, July 24, 2012 12: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]

  610 ms10 ms10 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  710 ms10 ms11 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

  813 ms13 ms13 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

  914 ms14 ms28 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1017 ms17 ms17 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1117 ms17 ms17 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1220 ms20 ms20 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1324 ms20 ms20 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1432 ms37 ms24 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1524 ms24 ms35 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1628 ms26 ms26 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1727 ms27 ms27 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 1830 ms31 ms31 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 1931 ms30 ms32 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2033 ms33 ms33 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2134 ms38 ms34 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2237 ms52 ms37 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2337 ms37 ms37 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2440 ms41 ms40 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2541 ms42 ms41 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2650 ms43 ms43 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2744 ms44 ms44 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 2860 ms47 ms64 ms
63-138-116-13.customer.static.ip.paetec.net [63.138.116.13]

 2947 ms47 ms48 ms
63-138-116-14.customer.static.ip.paetec.net [63.138.116.14]

 3052 ms50 ms51 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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
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 listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin<>

Re: help w/ tracert

2012-07-24 Thread Kurt Buff 
Ayup.

Time to call and yell.

On Tue, Jul 24, 2012 at 10:47 AM, Daniel Chenault <
dchena...@lgnetworksinc.com> wrote:

>  Paetec has a routing issue. But you already knew that.
>
> ** **
>
> Daniel Chenault
>
> dchena...@lgnetworksinc.com
>
> [image: Description: Description: cid:image001.jpg@01CCF24C.F9B05160]
>
> ** **
>
> *From:* David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
> *Sent:* Tuesday, July 24, 2012 12: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]
>
>   610 ms10 ms10 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>   710 ms10 ms11 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>   813 ms13 ms13 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>   914 ms14 ms28 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  1017 ms17 ms17 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  1117 ms17 ms17 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  1220 ms20 ms20 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  1324 ms20 ms20 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  1432 ms37 ms24 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  1524 ms24 ms35 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  1628 ms26 ms26 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  1727 ms27 ms27 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  1830 ms31 ms31 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  1931 ms30 ms32 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  2033 ms33 ms33 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  2134 ms38 ms34 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  2237 ms52 ms37 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  2337 ms37 ms37 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  2440 ms41 ms40 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  2541 ms42 ms41 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  2650 ms43 ms43 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  2744 ms44 ms44 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  2860 ms47 ms64 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  2947 ms47 ms48 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  3052 ms50 ms51 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! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>
> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin<>

Re: help w/ tracert

2012-07-24 Thread Richard Stovall 
What prompted the trace?  Is your Internet service down?  Is Paetec your
ISP?  Your e-mail looks to have originated from 98.172.163.12, a Cox ip.

On Tue, Jul 24, 2012 at 1:43 PM, David Mazzaccaro <
david.mazzacc...@hudsonmobility.com> wrote:

> **
>
> 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]
>
>   610 ms10 ms10 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>   710 ms10 ms11 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>   813 ms13 ms13 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>   914 ms14 ms28 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  1017 ms17 ms17 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  1117 ms17 ms17 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  1220 ms20 ms20 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  1324 ms20 ms20 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  1432 ms37 ms24 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  1524 ms24 ms35 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  1628 ms26 ms26 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  1727 ms27 ms27 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  1830 ms31 ms31 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  1931 ms30 ms32 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  2033 ms33 ms33 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  2134 ms38 ms34 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  2237 ms52 ms37 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  2337 ms37 ms37 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  2440 ms41 ms40 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  2541 ms42 ms41 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  2650 ms43 ms43 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  2744 ms44 ms44 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  2860 ms47 ms64 ms  63-138-116-13.
> customer.static.ip.paetec.net [63.138.116.13]
>
>  2947 ms47 ms48 ms  63-138-116-14.
> customer.static.ip.paetec.net [63.138.116.14]
>
>  3052 ms50 ms51 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! ~
> ~   ~
>
> ---
> To manage subscriptions click here:
> http://lyris.sunbelt-software.com/read/my_forums/
> or send an email to listmana...@lyris.sunbeltsoftware.com
> with the body: unsubscribe ntsysadmin
>

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

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

RE: help w/ tracert

2012-07-24 Thread Daniel Chenault 
Paetec has a routing issue. But you already knew that.

Daniel Chenault
dchena...@lgnetworksinc.com
[Description: Description: cid:image001.jpg@01CCF24C.F9B05160]

From: David Mazzaccaro [mailto:david.mazzacc...@hudsonmobility.com]
Sent: Tuesday, July 24, 2012 12: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]

  610 ms10 ms10 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

  710 ms10 ms11 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

  813 ms13 ms13 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

  914 ms14 ms28 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 1017 ms17 ms17 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 1117 ms17 ms17 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 1220 ms20 ms20 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 1324 ms20 ms20 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 1432 ms37 ms24 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 1524 ms24 ms35 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 1628 ms26 ms26 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 1727 ms27 ms27 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 1830 ms31 ms31 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 1931 ms30 ms32 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 2033 ms33 ms33 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 2134 ms38 ms34 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 2237 ms52 ms37 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 2337 ms37 ms37 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 2440 ms41 ms40 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 2541 ms42 ms41 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 2650 ms43 ms43 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 2744 ms44 ms44 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 2860 ms47 ms64 ms  63-138-116-13.customer.static.ip.paetec.net 
[63.138.116.13]

 2947 ms47 ms48 ms  63-138-116-14.customer.static.ip.paetec.net 
[63.138.116.14]

 3052 ms50 ms51 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! ~
~   ~

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

~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~   ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin<>