Date: Mon, 4 Oct 1999 09:04:53 -0400 From: "Milliken, Scott" <SMilliken@sti.imshealth.com> To: "'High Voltage'" <zapper@idsmail.com> Cc: "'stable@freebsd.org'" <stable@freebsd.org> Subject: RE: @Home Connect. Message-ID: <C26E7066AAA6D211AB16006097A52FCC5F63DE@stiusatlcx1.salestech.com>
next in thread | raw e-mail | index | archive | help
One extremely important note about @Home service... make sure that you disable all of your services in inetd before ever calling them up to report outages or for any other tech support issue. The first time that I placed a call to them they port scanned me, asked why I was running apache and telnet and then informed me that I was in violation of the Acceptable Usage Policy. Also, if you call to report an outage and you list your OS as anything other than Windows 95 or Windows 98 they simply will not try to diagnose the problem from their end. You can have a Christmas tree of blinking lights on your cable modem (in Atlanta they use the Cisco uBR900) yet without the magical Win9X operating system they'll tell you that it must be a problem at your end. Good Luck, Scott Milliken -----Original Message----- From: High Voltage [mailto:zapper@idsmail.com] Sent: Sunday, October 03, 1999 5:44 PM To: FreeBSD-Stable Subject: @Home Connect. Hi Does anyone know where I can find info on how to set FreeBSD 3.3 Stable up for a @Home connect? I'm getting @Home installed this Friday and I'd like to be prepared. Thanx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C26E7066AAA6D211AB16006097A52FCC5F63DE>