Cisco Router Halp!

From: Wattsy (SLAYERPUNX) 6 Jul 2011 16:06
To: Ken (SHIELDSIT) 7 of 18
Oh just routine treatment for my kidney disease. Iv fed steroids, Mmmmm yummy. Erg. Month 5 now. Not going to well either.
From: Ken (SHIELDSIT) 6 Jul 2011 16:31
To: Wattsy (SLAYERPUNX) 8 of 18
Well that blows!

(hug)
From: Wattsy (SLAYERPUNX) 6 Jul 2011 17:36
To: Ken (SHIELDSIT) 9 of 18
And sucks at the same time.
From: Ken (SHIELDSIT) 6 Jul 2011 18:39
To: Wattsy (SLAYERPUNX) 10 of 18
No doubt! Well I found the culprit. Bad nic or infect machine at one of the remote sites was flooding the wan. No idea how I figured it out.
From: Serg (NUKKLEAR) 7 Jul 2011 09:24
To: Ken (SHIELDSIT) 11 of 18
Hunches are wonderful things - you get more and more of them as you age... er, I mean as you become more experienced.
From: 99% of gargoyles look like (MR_BASTARD) 7 Jul 2011 09:57
To: Serg (NUKKLEAR) 12 of 18
try telling that to Quasimodo.
From: Serg (NUKKLEAR) 7 Jul 2011 11:50
To: 99% of gargoyles look like (MR_BASTARD) 13 of 18
I'm starting to see Drew's point...
From: Ken (SHIELDSIT) 7 Jul 2011 12:54
To: Serg (NUKKLEAR) 14 of 18
It was infected. Hard for me to believe that was the cause, but I guess I'll find out today.
From: patch 7 Jul 2011 13:16
To: Ken (SHIELDSIT) 15 of 18

Your hunch was infected? Messy.

 

Google seems to suggest that it may have something to do with Kazaa or some such P2P application.

From: Ken (SHIELDSIT) 7 Jul 2011 13:25
To: patch 16 of 18
I'm usually infected with something :-P

I've seen this happen with bad NIC's but that doesn't seem to be the case. As soon as I turned it on here at the office it came up as infected. Cleaning it up now.
From: 99% of gargoyles look like (MR_BASTARD) 7 Jul 2011 17:10
To: Serg (NUKKLEAR) 17 of 18
Oi, don't get the hump with me!
From: Ken (SHIELDSIT) 7 Jul 2011 17:19
To: Serg (NUKKLEAR) 18 of 18
I meant to laugh at this, because when I read it it did make me chuckle. So...

:'-D