7 Mar
2005
7 Mar
'05
5:48 a.m.
On Mon, 7 Mar 2005, Jules Richardson wrote:
On Sun, 2005-03-06 at 23:47 +0000, Gordon JC Pearce
wrote:
I had the same problem with my local carrier (SBC, one of the biggies,
just bought AT&T, etc.) You'd think these idiots would know when one of
their servers was acting up, but no, it took several useless calls to tech
"support" talking to people in India that really don't know what
they're
doing before I was finally connected to someone who knew what to do to fix
the problem. I was down three times in 5 days thanks to a malfunctioning
router. I'm not yet convinced the problem is fixed (it was intermittent)
but we'll see.
--
Sellam Ismail Vintage Computer Festival
------------------------------------------------------------------------------
International Man of Intrigue and Danger http://www.vintage.org
[ Old computing resources for business || Buy/Sell/Trade Vintage Computers ]
[ and academia at www.VintageTech.com || at http://marketplace.vintage.org ]
I am loath to say this, because I will almost
certainly have massive
downtime tomorrow...
I am on (nominally) dynamic IP space, on NTL cable. My IP address has
changed once, when I changed MAC addresses (built my firewall machine).
My uptime has been better than the 8-grand-per-month leased line we
had at my old job.
<rant>
Hmm. My NTL cable crapped out weekend before last and started dropping
50% of packets. Then it worked for 5 days, then started doing the same
again on Friday. Saturday the link was totally dead apart from 5 minutes
where it came back, Sunday it actually came back properly for 3 hours or
so, then did an hour of dropping 50% of data again, then fell over
completely. This morning it's up and running 100% again, but I don't
know for how long.
I'd expect a big company like NTL to have all sort of network monitoring
to detect this kind of thing and replace hardware at the first sign of
trouble (asking around, it's not just me and is affecting a fairly wide
area).