I'm working at home today, and our webmail server has wandered off into the weeds again. The server crew is looking at it (a problem between our Exchange Front-End Server and the back-end Exchange boxes -- the lead suspect is the addition of a bunch of direct traffic from Treo users {in response to a DST-related problem with Verizon's synch service for Treos [stupid congresscritter]}).
...That rather suddenly leaves me without my primary means of communication. Well, there was a bunch of non-correspondence oriented stuff I wanted to look at... I guess I'll do that.
...That rather suddenly leaves me without my primary means of communication. Well, there was a bunch of non-correspondence oriented stuff I wanted to look at... I guess I'll do that.
- Current Music:Random ambient
Profile
netcurmudgeon- netcurmudgeon
- House of Hum
Comments
The SNET/SBC/AT&T (whatever company it is today) box is a mile from us, but it takes 2 hours to report something broken, since you must first slog through endless Level 1 disservice personnel in another country and CONVINCE them that it's not your line nor PC nor router that's broken.
How did you get all that information of why your connection is gone? I'm impressed.
I spent some time with the server guys two days ago helping with troubleshooting. They thought that they had the problem licked Tuesday night, but it came back again this morning...
...since you must first slog through endless Level 1 disservice personnel in another country and CONVINCE them that it's not your line nor PC nor router that's broken.
I really, really, wish that there was some way to signal to these folks "I'm not a marching moron like nine out of ten other people you've talked to." Of course, these Level 1 people get so little training, and have such rigid scripts to follow, that if you whip genunine telco jargon on them (in an attempt to prove that you know what of you speak) they're usually just lost.
There is no way to win.
are they Sentient--Human???