Comcast Contact
Can someone clueful from comcast.net contact me offlist please? Thank you. -G
RE: Seeking Comcast Contact: need to troubleshoot packet loss and/or asymmetric routing issue between Comcast Onvoy
I've forwarded your message to the appropriate team within Comcast. - Alain. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig D. Rice Sent: Thursday, August 02, 2007 9:30 AM To: nanog@merit.edu Subject: Seeking Comcast Contact: need to troubleshoot packet loss and/or asymmetric routing issue between Comcast Onvoy For four months dozens of our users who are Comcast subscribers have had difficulty reaching St. Olaf College's and Carleton College's network services. We have worked through everything we can think of with our Onvoy (regional ISP) network engineers. We have isolated the problem a couple of Comcast's IP subnets, but need a contact within Comcast to further troubleshoot. The behavior in a nutshell: -- User A on Comcast Subnet B browses to www.stolaf.edu (http or https, other web sites on-site and @carleton.edu behave the same). Our access_log shows an initial GET / of our homepage, then very slow (if any) subsequent requests (for our stylesheet or homepage images). Ping's look fine; traceroute's look as reasonable. Telnet's to port 80 and other services do seem to respond, albeit very slowly. User A has the same problem with access @carleton.edu but can access everything else (including other Onvoy customers) without any trouble whatsoever. If User A then removes his Linksys router and connects his computer directly to the cable modem, he acquires an IP address in Comcast Subnet C. Then, everything works fine, including access to www.stolaf.edu and www.carleton.edu. He puts the Linksys router back in (which still has the IP address in Comcast Subnet B), and the problem returns. The problem IP subnets are completely consistent. Known WORKING IP Subnets: 75.72.0.0, 24.x Known NON-WORKING IP Subnets: 71.x, 73.x -- We have already attempted the usual troubleshooting and have eliminated user problems, computer problems, server problems, cable modem problems, and Linksys router problems. Traceroutes have been somewhat inconclusive since Onvoy blocks ICMP within its network. So, why just St. Olaf and Carleton services? We are on a shared physical link from Onvoy, though on different VLANs. Onvoy has verified everything they can (routing, packet loss, etc.) between them and us, and I'm not sure what additional questions I can ask of them to test. Suggestions? Maybe Comcast has a broken transparent proxy on part(s) of their network? But they have told us they have nothing like this anywhere on their network. Maybe there is some asymmetric routing somewhere, though all the investigation there has come up empty. A third possibility is some kind of packet loss, but there is little if any evidence of that. So, we are really at a loss and seek any suggestions you all might have. And a contact in Comcast network engineering would be especially useful to continue our troubleshooting. With thanks, Craig -- Craig D. Rice Associate Director of Information Systems [EMAIL PROTECTED]Information and Instructional Technologies +1 507 786-3631 St. Olaf College +1 507 786-3096 FAX 1510 St. Olaf Avenue http://www.stolaf.edu/people/cdr Northfield, MN 55057-1097 USA
Seeking Comcast Contact: need to troubleshoot packet loss and/or asymmetric routing issue between Comcast Onvoy
For four months dozens of our users who are Comcast subscribers have had difficulty reaching St. Olaf College's and Carleton College's network services. We have worked through everything we can think of with our Onvoy (regional ISP) network engineers. We have isolated the problem a couple of Comcast's IP subnets, but need a contact within Comcast to further troubleshoot. The behavior in a nutshell: -- User A on Comcast Subnet B browses to www.stolaf.edu (http or https, other web sites on-site and @carleton.edu behave the same). Our access_log shows an initial GET / of our homepage, then very slow (if any) subsequent requests (for our stylesheet or homepage images). Ping's look fine; traceroute's look as reasonable. Telnet's to port 80 and other services do seem to respond, albeit very slowly. User A has the same problem with access @carleton.edu but can access everything else (including other Onvoy customers) without any trouble whatsoever. If User A then removes his Linksys router and connects his computer directly to the cable modem, he acquires an IP address in Comcast Subnet C. Then, everything works fine, including access to www.stolaf.edu and www.carleton.edu. He puts the Linksys router back in (which still has the IP address in Comcast Subnet B), and the problem returns. The problem IP subnets are completely consistent. Known WORKING IP Subnets: 75.72.0.0, 24.x Known NON-WORKING IP Subnets: 71.x, 73.x -- We have already attempted the usual troubleshooting and have eliminated user problems, computer problems, server problems, cable modem problems, and Linksys router problems. Traceroutes have been somewhat inconclusive since Onvoy blocks ICMP within its network. So, why just St. Olaf and Carleton services? We are on a shared physical link from Onvoy, though on different VLANs. Onvoy has verified everything they can (routing, packet loss, etc.) between them and us, and I'm not sure what additional questions I can ask of them to test. Suggestions? Maybe Comcast has a broken transparent proxy on part(s) of their network? But they have told us they have nothing like this anywhere on their network. Maybe there is some asymmetric routing somewhere, though all the investigation there has come up empty. A third possibility is some kind of packet loss, but there is little if any evidence of that. So, we are really at a loss and seek any suggestions you all might have. And a contact in Comcast network engineering would be especially useful to continue our troubleshooting. With thanks, Craig -- Craig D. Rice Associate Director of Information Systems [EMAIL PROTECTED]Information and Instructional Technologies +1 507 786-3631 St. Olaf College +1 507 786-3096 FAX 1510 St. Olaf Avenue http://www.stolaf.edu/people/cdr Northfield, MN 55057-1097 USA
Re: Seeking Comcast Contact: need to troubleshoot packet loss and/or asymmetric routing issue between Comcast Onvoy
On 8/2/07, Craig D. Rice [EMAIL PROTECTED] wrote: We have already attempted the usual troubleshooting and have eliminated user problems, computer problems, server problems, cable modem problems, and Linksys router problems. Traceroutes have been somewhat inconclusive since Onvoy blocks ICMP within its network. Craig, This rings a bell. Do they block the mandatory ICMP fragmentation-needed messages? Try this: on your web server, reduce the MTU from 1500 bytes to 1400 bytes and see if the affected comcast users can now access your web server. Regards, Bill Herrin -- William D. Herrin [EMAIL PROTECTED] [EMAIL PROTECTED] 3005 Crane Dr.Web: http://bill.herrin.us/ Falls Church, VA 22042-3004
Re: Seeking Comcast Contact: need to troubleshoot packet loss and/or asymmetric routing issue between Comcast Onvoy
At 09:30 AM 8/2/2007, Craig D. Rice wrote: For four months dozens of our users who are Comcast subscribers have had difficulty reaching St. Olaf College's and Carleton College's network services. We have worked through everything we can think of with our Onvoy (regional ISP) network engineers. We have isolated the problem a couple of Comcast's IP subnets, but need a contact within Comcast to further troubleshoot. (snip) Either your firewall/router or the customer's firewall/router is blocking PMTUD packets. Fragment needed, but don't fragment bit set. Look at your ICMP access list and make sure you are allowing: permit icmp any any unreachable from any Internet address. I suspect an overzealous firewall admin is blocking all icmp. Read the acronym to him/her and explain that some icmp is necesary for the Internet to work. -Robert Tellurian Networks - Global Hosting Solutions Since 1995 http://www.tellurian.com | 888-TELLURIAN | 973-300-9211 Well done is better than well said. - Benjamin Franklin
Re: Seeking Comcast Contact: need to troubleshoot packet loss and/or asymmetric routing issue between Comcast Onvoy
Robert Boyle wrote: Either your firewall/router or the customer's firewall/router is blocking PMTUD packets. I suspect an overzealous firewall admin is blocking all icmp. Which you can't do anything about if the overzealous firewall admin is at the other end of the connection. My repeated, first-hand experience has been that several of the better-known web sites out there will happily send out 1500-byte packets with DF set, then ignore the DEST_UNREACH/FRAG_NEEDED icmp responses they get. If you're on the client end of this, you're sunk unless you initiate the connection specifying a lower MSS. Linux has a nifty iptables option (clamp-mss-to-pmtu) to rewrite the MSS in TCP SYN packets when forwarding a packet onto a link with a lower MTU than the MSS in the packet. Works like a charm. If every packet forwarding device on the Internet did this, PMTUD would not be needed. As is, PMTUD is simply broken, due to widespread firewall misconfiguration. As in so many other cases of Internet misbehavior, you can avoid being part of the problem, but you can't be the solution. Jim Shankland
Re: Seeking Comcast Contact: need to troubleshoot packet loss and/or asymmetric routing issue between Comcast Onvoy
On Thu, Aug 02, 2007, Jim Shankland wrote: Linux has a nifty iptables option (clamp-mss-to-pmtu) to rewrite the MSS in TCP SYN packets when forwarding a packet onto a link with a lower MTU than the MSS in the packet. Works like a charm. If every packet forwarding device on the Internet did this, PMTUD would not be needed. As is, PMTUD is simply broken, due to widespread firewall misconfiguration. As in so many other cases of Internet misbehavior, you can avoid being part of the problem, but you can't be the solution. .. non-TCP traffic? Adrian
Re: Seeking Comcast Contact: need to troubleshoot packet loss and/or asymmetric routing issue between Comcast Onvoy
Adrian Chadd wrote: On Thu, Aug 02, 2007, Jim Shankland wrote: Linux has a nifty iptables option (clamp-mss-to-pmtu) to rewrite the MSS in TCP SYN packets when forwarding a packet onto a link with a lower MTU than the MSS in the packet. Works like a charm. If every packet forwarding device on the Internet did this, PMTUD would not be needed. As is, PMTUD is simply broken, due to widespread firewall misconfiguration. As in so many other cases of Internet misbehavior, you can avoid being part of the problem, but you can't be the solution. .. non-TCP traffic? Hmm; I've never actually heard of anybody doing PMTUD on non-TCP traffic, though it's possible. Does anybody actually do it? Jim Shankland
Re: Seeking Comcast Contact: need to troubleshoot packet loss and/or asymmetric routing issue between Comcast Onvoy
On Thu, 02 Aug 2007 18:33:16 PDT, Jim Shankland said:
Hmm; I've never actually heard of anybody doing PMTUD on non-TCP
traffic, though it's possible. Does anybody actually do it?
AIX 5.2 and earlier supported it for UDP (we're getting out of the AIX
business, so I can't speak to what 5.3 does). Basically, it would send out a
gratuitous 64K ICMP Echo Request with DF set, and waited to see what came back.
I ended up turning it off all over, simply because we didn't have enough
UDP-based services that actually hit frag issues to make a difference.
---
'man no' (Network Options) says:
no { -a | -d Attribute | -o Attribute [ =NewValue ] }
udp_pmtu_discover Enables or disables path MTU discovery for UDP applications.
UDP applications must be specifically written to utilize path MTU discovery. A
value of 0 disables the feature, while a value of 1 enables it. This attribute
only applies to AIX 4.2.1 or later. udp_pmtu_discover is a runtime attribute. In
versions prior to AIX 4.3.3, the default value is 0 (disabled); in AIX 4.3.3 and
later versions, the default value is 1 (enabled).
---
The manpage lies - It has to be specifically written to *benefit from* PMTUD.
It would go ahead and do it, and then 98% of the UDP programs wouldn't change
their behavior. So all you got was lots of gratuitous ICMP mobygrams.
It *may* have made a small difference during a short window, when NFS-over-TCP
support was still rare, and the 4500-octet FDDI MTU was sometimes to be found.
pgpM2BhhEjM7a.pgp
Description: PGP signature
Need a Comcast contact
If you work for Comcast and have the ability to investigate routing problems in the northwest, please contact me off-list. An odd routing issue has been affecting your customers and ours for about the last month and I am still trying to determine exactly what's going on and how to fix it. (I've already tried all the Comcast NOC numbers and emails that I can find, from the NOC database, peering database, WHOIS information, etc, and as a Comcast customer I've also tried to go through the standard support channels. If anyone here thinks they have a resource that I haven't tried, please let me know.) -John
Re: Comcast contact for the East Coast
On Wednesday 07 March 2007 22:57, Dennis Dayman wrote: Dennis Dayman wrote: Stephen Kratzer wrote: On Friday 02 March 2007 20:58, Ashe Canvar wrote: Could someone from Comcast please contact us ([EMAIL PROTECTED]). Customers behind Comcast on the east coast cannot get to our 216.219.126.0 prefix in Santa Barbara, CA. Comcast's peering with Cox on ashbbbrj02-ae0.0.r2.as.cox.net may be to blame. Regards, Ashe Canvar Network Engineer -- Citrix Online (AS16815) 5385 Hollister Avenue Santa Barbara, CA 93111 USA -- We've been having a similar issue since last Friday; Comcast customers are unable to get to our 66.59.96.0/24 prefix through Ashburn, Virginia. Could someone from Comcast also contact us at [EMAIL PROTECTED] Also, anyone happen to know of a publically accessible Comcast looking glass? Thanks, Stephen Kratzer Network Engineer II CTI Networks, Inc. Comcast ops folks said they have stated a network change was made last Friday which should have addressed this; are you still having the problem and if so, when the most recent time was they ask? -Dennis The issue seems to have been resolved. Thank you.
Re: Comcast contact for the East Coast
Stephen Kratzer wrote: On Friday 02 March 2007 20:58, Ashe Canvar wrote: Could someone from Comcast please contact us ([EMAIL PROTECTED]). Customers behind Comcast on the east coast cannot get to our 216.219.126.0 prefix in Santa Barbara, CA. Comcast's peering with Cox on ashbbbrj02-ae0.0.r2.as.cox.net may be to blame. Regards, Ashe Canvar Network Engineer -- Citrix Online (AS16815) 5385 Hollister Avenue Santa Barbara, CA 93111 USA -- We've been having a similar issue since last Friday; Comcast customers are unable to get to our 66.59.96.0/24 prefix through Ashburn, Virginia. Could someone from Comcast also contact us at [EMAIL PROTECTED] Also, anyone happen to know of a publically accessible Comcast looking glass? Thanks, Stephen Kratzer Network Engineer II CTI Networks, Inc. I shot this over to Comcast security who can get their op folks on it.
Re: Comcast contact for the East Coast
Dennis Dayman wrote: Stephen Kratzer wrote: On Friday 02 March 2007 20:58, Ashe Canvar wrote: Could someone from Comcast please contact us ([EMAIL PROTECTED]). Customers behind Comcast on the east coast cannot get to our 216.219.126.0 prefix in Santa Barbara, CA. Comcast's peering with Cox on ashbbbrj02-ae0.0.r2.as.cox.net may be to blame. Regards, Ashe Canvar Network Engineer -- Citrix Online (AS16815) 5385 Hollister Avenue Santa Barbara, CA 93111 USA -- We've been having a similar issue since last Friday; Comcast customers are unable to get to our 66.59.96.0/24 prefix through Ashburn, Virginia. Could someone from Comcast also contact us at [EMAIL PROTECTED] Also, anyone happen to know of a publically accessible Comcast looking glass? Thanks, Stephen Kratzer Network Engineer II CTI Networks, Inc. Comcast ops folks said they have stated a network change was made last Friday which should have addressed this; are you still having the problem and if so, when the most recent time was they ask? -Dennis
Re: Comcast contact for the East Coast
On Friday 02 March 2007 20:58, Ashe Canvar wrote: Could someone from Comcast please contact us ([EMAIL PROTECTED]). Customers behind Comcast on the east coast cannot get to our 216.219.126.0 prefix in Santa Barbara, CA. Comcast's peering with Cox on ashbbbrj02-ae0.0.r2.as.cox.net may be to blame. Regards, Ashe Canvar Network Engineer -- Citrix Online (AS16815) 5385 Hollister Avenue Santa Barbara, CA 93111 USA -- We've been having a similar issue since last Friday; Comcast customers are unable to get to our 66.59.96.0/24 prefix through Ashburn, Virginia. Could someone from Comcast also contact us at [EMAIL PROTECTED] Also, anyone happen to know of a publically accessible Comcast looking glass? Thanks, Stephen Kratzer Network Engineer II CTI Networks, Inc.
Comcast contact for the East Coast
Could someone from Comcast please contact us ([EMAIL PROTECTED]). Customers behind Comcast on the east coast cannot get to our 216.219.126.0 prefix in Santa Barbara, CA. Comcast's peering with Cox on ashbbbrj02-ae0.0.r2.as.cox.net may be to blame. Regards, Ashe Canvar Network Engineer -- Citrix Online (AS16815) 5385 Hollister Avenue Santa Barbara, CA 93111 USA --
Re: Comcast contact for the East Coast
On Fri, 2007-03-02 at 17:58 -0800, Ashe Canvar wrote: Could someone from Comcast please contact us ([EMAIL PROTECTED]). Customers behind Comcast on the east coast cannot get to our 216.219.126.0 prefix in Santa Barbara, CA. Comcast's peering with Cox on ashbbbrj02-ae0.0.r2.as.cox.net may be to blame. I'm presently hanging off of Comcast in Atlanta (76.17.105.x) and I can ping traceroute and ping 216.219.126.1 -Jim P. signature.asc Description: This is a digitally signed message part
RE: Comcast contact for the East Coast
Could someone from Comcast please contact us ([EMAIL PROTECTED]). Customers behind Comcast on the east coast cannot get to our 216.219.126.0 prefix in Santa Barbara, CA. Comcast's peering with Cox on ashbbbrj02-ae0.0.r2.as.cox.net may be to blame. COX has created ticket HD015981407 for this issue. A show route shows us that traffic destined for target IP 216.219.126.0 is going from ASHBBBRJ02 to ASHBBBRJ01, and then directly to the Equinix Public Peering Switch in Ashburn, and then stopping. I will be contacting Equinix shortly to continue troubleshooting. -J. Andrew Parris NOC Engineer Data Network Operations Center Cox Communications (AS 22773) 1-888-326-9266, Opt. 1 mailto:[EMAIL PROTECTED] AIM: coxnocandpa
Re: Comcast contact for the East Coast
On Fri, 02 Mar 2007 21:08:58 -0500 Jim Popovitch [EMAIL PROTECTED] wrote: On Fri, 2007-03-02 at 17:58 -0800, Ashe Canvar wrote: Could someone from Comcast please contact us ([EMAIL PROTECTED]). Customers behind Comcast on the east coast cannot get to our 216.219.126.0 prefix in Santa Barbara, CA. Comcast's peering with Cox on ashbbbrj02-ae0.0.r2.as.cox.net may be to blame. I'm presently hanging off of Comcast in Atlanta (76.17.105.x) and I can ping traceroute and ping 216.219.126.1 As can I from Comcast in NJ. --Steve Bellovin, http://www.cs.columbia.edu/~smb
Re: Comcast contact
Anshuman: A good place to start for operational contacts is both the puck.nether.net site and the www.peeringdb.com. i found this: http://puck.nether.net/netops/nocs.cgi?ispname=comcast and this: (you can log in as a guest)... https://www.peeringdb.com/private/participant_view.php?id=822 now go get them peter cohen. On 9/25/06, Anshuman Kanwar [EMAIL PROTECTED] wrote: Can someone from comcast contact me off list please ? Thanks, Ansh Kanwar Lead Network Engineer -- Citrix Online (AS16815) 5385 Hollister Avenue Santa Barbara, CA 93111 USA --
Comcast contact
Can someone from comcast contact me off list please ? Thanks, Ansh Kanwar Lead Network Engineer -- Citrix Online (AS16815) 5385 Hollister Avenue Santa Barbara, CA 93111 USA --
Comcast contact available?
It seems you are null-routing traffic heading towards our /20. If there are any comcast chaps on this list, please drop me a mail - this has been going on for a few days now and we're having trouble getting it escalated to someone with sufficient access to check it. Thanks, Ras
Comcast contact also.
Also looking for a Comcast contact for mail abuse issues. Please reply off-list. Brian.
Comcast contact
Looking for a Comcast contact. Please reply off-list. Jeff.
Comcast Contact
Could someone from Comcast please email me off list. Ross Hosman [EMAIL PROTECTED]
Re: Comcast Contact
On Wednesday April 13 2005 08:04, Ross Hosman wrote: Could someone from Comcast please email me off list. Ross Hosman [EMAIL PROTECTED] http://www.nanog.org/email.html Follow directions.. -- Scott Grayban Security/Abuse Engineer FCT Enterprises -- www.fctsupport.com
Re: Comcast Contact
On 4/13/05, Ross Hosman [EMAIL PROTECTED] wrote: Could someone from Comcast please email me off list. Ross Hosman [EMAIL PROTECTED] If you have an AS, get yourself an inoc-dba phone. Easiest way to contact network operators that I know of. -- Suresh Ramasubramanian ([EMAIL PROTECTED])
NOC-DBA Phone (was Re: Comcast Contact)
I have one, and its cool. However the time I *really* needed it was because I couldn't reach a particular AS... and of course neither could my INOC-DBA phone (sigh...). -Jeff On Wed, 2005-04-13 at 23:12, Suresh Ramasubramanian wrote: On 4/13/05, Ross Hosman [EMAIL PROTECTED] wrote: Could someone from Comcast please email me off list. Ross Hosman [EMAIL PROTECTED] If you have an AS, get yourself an inoc-dba phone. Easiest way to contact network operators that I know of. -- = Jeffrey I. Schiller MIT Network Manager Information Services and Technology Massachusetts Institute of Technology 77 Massachusetts Avenue Room W92-190 Cambridge, MA 02139-4307 617.253.0161 - Voice [EMAIL PROTECTED]
Re: INOC-DBA Phone (was Re: Comcast Contact)
On Thu, 14 Apr 2005, Jeffrey I. Schiller wrote: I have one, and its cool. However the time I *really* needed it was because I couldn't reach a particular AS... and of course neither could my INOC-DBA phone (sigh...). There are several ways around that... Probably the easiest is to have your INOC-DBA phone number ring not only the SIP phone on your NOC desk, but a couple of commercial gateways like Vonage and BroadVoice and so forth, which would not, under most circumstances, all be affected by the same outage. One hopes. They would then ring PSTN numbers for you. Another way around the problem, which has been the most common one historically, is to put the INOC-DBA phones on different DSL/cable providers' lines run into your NOC, as well as on your own network. Three phones, reached through three ASNs, and _something_ should ring. A third way, which only a few ISPs have done, is to run a separate infrastructure out to a few exchanges, just to support those VoIP calls. That probably only makes sense if you're doing it anyway, for broader VoIP peering. -Bill
Comcast Contact. (was: RE: AOL scomp)
Pardon my interruption of the ongoing discussion of SMTP trust models and FUSSPs (which I think is very important BTW), but if there is somebody from Comcast here that can help us solve an immediate related issue, please contact me or one of my postmasters off list? Normal channels have been attempted unsuccessfully, for a problem that has been repeating itself every few days for the past two months. --chuck goolsbee digital.forest inc, seattle, wa http://www.forest.net [EMAIL PROTECTED] - [EMAIL PROTECTED] - 206-838-1630 xt2001 - AIM:chuckgoolsbee or [EMAIL PROTECTED] - [EMAIL PROTECTED] - 877-720-0483 xt 2002 Thanks. --
Comcast Contact
Can somebody at comcast.net with a clue about possible ip routing problems please contact me off-list.
Re: Need Comcast contact
On Mon, 1 Mar 2004, Brian Bruns wrote: Anyone happen to know of a contact for Comcast's mail server administrators? I need to discuss an issue with them about their mail servers mailbombing my systems from a joe job. Good luck...the last time I had to contact their email admins, it took two days to get ahold of someone with a clue. They apparently outsource their email. James Smallacombe PlantageNet, Inc. CEO and Janitor [EMAIL PROTECTED] http://3.am =
Need Comcast contact
Anyone happen to know of a contact for Comcast's mail server administrators? I need to discuss an issue with them about their mail servers mailbombing my systems from a joe job. Thanks. -- Brian Bruns The Summit Open Source Development Group Open Solutions For A Closed World / Anti-Spam Resources http://www.sosdg.org The Abusive Hosts Blocking List http://www.ahbl.org
[OT] Need Comcast Contact
Emails sent *from residential comcast subscribers* to any '@voicenet.com' address have been disappearing in the Comcast network since Sunday, Feb 31. There are no bounces or errors of any kind. Mail sent directly to other domains with the same MX record and even to individual machines within the MX record themselves work fine, it is only when the envelope recipient states /[EMAIL PROTECTED]/ does the mail simply disappear (i.e. mail sent to [EMAIL PROTECTED] disappears while mail sent to [EMAIL PROTECTED] goes through fine as well as [EMAIL PROTECTED]). My company as well as our customers and Comcast customers have together made many, many phone calls and sent many emails and we cannot get ahold of anyone with any semblance of a clue and nobody seeems to have the ability to put us in contact with anyone in your systems and/or network admins (level 1-3 techs, managers and even case resolution specialists). Can someone please contact me off-list in regards to this situation? Has anyone else had similar problems? Thanks. -- Tim Wesemann Voicenet Systems Administration
Re: [OT] Need Comcast Contact
Well sure, they are sent on a date that doesn't exist. Feb 31 can never happen. Pardon, that should have read Sunday, Feb 01 2004 AD (Chinese year of the monkey). =] -- Tim Wesemann Voicenet Systems Administration
