BLU Discuss list archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Could comcast be blocking port 6667 outbound?

Subject: Could comcast be blocking port 6667 outbound?
From: gcmarx at gmail.com (Gordon Marx)
Date: Fri, 2 Sep 2005 00:39:17 -0400
In-reply-to: <Pine.LNX.4.61.0509012303570.19219@mgorse.dhs.org>
References: <Pine.LNX.4.61.0509011622250.16515@mgorse.dhs.org> <200509011646.18337.gaf@blu.org> <20050802010116.52177.jc@trillian.mit.edu> <Pine.LNX.4.61.0509012151460.17333@mgorse.dhs.org> <Pine.LNX.4.61.0509012303570.19219@mgorse.dhs.org>

On 01/09/05, Mike Gorse <mgorse at mgorse.dhs.org> wrote:
> Well, I spoke too soon; it quickly stopped working.  

They're reading your email! ::tinfoil hat on::

Gordon
-- 
Gordon Marx
gcmarx at gmail.com

Follow-Ups:
- Could comcast be blocking port 6667 outbound?
  - From: bill at horne.net (Bill Horne)

References:
- Could comcast be blocking port 6667 outbound?
  - From: mgorse at mgorse.dhs.org (Mike Gorse)
- Could comcast be blocking port 6667 outbound?
  - From: gaf at blu.org (Jerry Feldman)
- Could comcast be blocking port 6667 outbound?
  - From: jc at trillian.mit.edu (John Chambers)
- Could comcast be blocking port 6667 outbound?
  - From: mgorse at mgorse.dhs.org (Mike Gorse)
- Could comcast be blocking port 6667 outbound?
  - From: mgorse at mgorse.dhs.org (Mike Gorse)

Prev by Date: Could comcast be blocking port 6667 outbound?
Next by Date: Could comcast be blocking port 6667 outbound?
Previous by thread: Could comcast be blocking port 6667 outbound?
Next by thread: Could comcast be blocking port 6667 outbound?
Index(es):
- Date
- Thread


BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Boston Linux & Unix / webmaster@blu.org