![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
kengrLate Friday night (ok, early Saturday morning) my cable Internet went out. The cable modem's lights were all wonky (technical term :-). But I didn't feel like dealing with customer (dis)service. So I went to bed.
When I got up, I checked and things were still not working.
So I called. The tech (of course) wanted me to reboot. And I knew he'd want me connected directly to the modem. So I dug out the laptop (crawling around under the desk to *try* to get at the cables on the back of either Windows box is out of the question).
Of course, it's an old P-133, so it takes forever to boot. And then the guy wants me to remove the TCP/IP stack for the network card. This involves doing it, rebooting, restoring it, and rebooting again. Somewhere in there (this takes a long time on this old laptop) he hung up on me.
So I called again. This time I got a different guy who listened to me description of the lights on the cable modem and told me that it was in standby mode (which apparently can happen if there are connection problems). The cable and PC Link light were on, the power light wasn't.
So he tell's me to press the power button to take it out of standby. And it takes off like nothing had ever been wrong. GRRRR!
Why couldn't the *first* tech have told me that?
I'll be glad when Comcast replaces these clowns. They've got the occasional good tech (like the second one I got). And a lot of "I have to read the script" types. :-(
Then Saturday night, I discover that my domain is down. Or rather, that the system hosting it seems unreachable. I left an AIM message for the guy who runs it and got awakened by a call rather earlier than I wanted to be (but at a not unreasonable hour for "normal" folks on a Sunday).
Seems that the outfit he'd gotten his IP address block from had gone under. He'd thought he had another week to swap the IP addresses. He didn't. So there was much frantic scrambling around, and he gave me a workaround to *fetch* my mail.
Of course, for the 12 or so hours left until the new address propagates thru the DNS servers, nobody can *send* me any mail.
Meanwhile, I spent most of Saturday trying to sort thru the many gigabytes of downloaded files I've got. In the process I cursed Microsoft many times. Seems that there's a memory leak in Windows Explorer. After using it to shuffle files for a couple of hours, the system (which started out with 70% of system resources free) would have less than 1%. And have to be rebooted.
And often have to be rebooted again as this system gets "picky" about reboots and sometimes takes two or three reboots to get a "good" one.
I spent 12-16 hours shuffling files. You do the math. :-(
But I am eliminating a lot of dupes caused by folks repacking files into different archive formats or the same format with different compression options. My dupe checker can't catch that. But when I unpack the files it can. So I'm slowly proceeding.
When I got up, I checked and things were still not working.
So I called. The tech (of course) wanted me to reboot. And I knew he'd want me connected directly to the modem. So I dug out the laptop (crawling around under the desk to *try* to get at the cables on the back of either Windows box is out of the question).
Of course, it's an old P-133, so it takes forever to boot. And then the guy wants me to remove the TCP/IP stack for the network card. This involves doing it, rebooting, restoring it, and rebooting again. Somewhere in there (this takes a long time on this old laptop) he hung up on me.
So I called again. This time I got a different guy who listened to me description of the lights on the cable modem and told me that it was in standby mode (which apparently can happen if there are connection problems). The cable and PC Link light were on, the power light wasn't.
So he tell's me to press the power button to take it out of standby. And it takes off like nothing had ever been wrong. GRRRR!
Why couldn't the *first* tech have told me that?
I'll be glad when Comcast replaces these clowns. They've got the occasional good tech (like the second one I got). And a lot of "I have to read the script" types. :-(
Then Saturday night, I discover that my domain is down. Or rather, that the system hosting it seems unreachable. I left an AIM message for the guy who runs it and got awakened by a call rather earlier than I wanted to be (but at a not unreasonable hour for "normal" folks on a Sunday).
Seems that the outfit he'd gotten his IP address block from had gone under. He'd thought he had another week to swap the IP addresses. He didn't. So there was much frantic scrambling around, and he gave me a workaround to *fetch* my mail.
Of course, for the 12 or so hours left until the new address propagates thru the DNS servers, nobody can *send* me any mail.
Meanwhile, I spent most of Saturday trying to sort thru the many gigabytes of downloaded files I've got. In the process I cursed Microsoft many times. Seems that there's a memory leak in Windows Explorer. After using it to shuffle files for a couple of hours, the system (which started out with 70% of system resources free) would have less than 1%. And have to be rebooted.
And often have to be rebooted again as this system gets "picky" about reboots and sometimes takes two or three reboots to get a "good" one.
I spent 12-16 hours shuffling files. You do the math. :-(
But I am eliminating a lot of dupes caused by folks repacking files into different archive formats or the same format with different compression options. My dupe checker can't catch that. But when I unpack the files it can. So I'm slowly proceeding.
![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png){kind=small}
no subject
Date: 2004-03-14 11:19 pm (UTC)1. Unplug/turn off your router/hub if you have one, wait a few, then plug it back in.
2. do the same thing with the friggen modem.
if none of the above fix the problem, then make the call, cause it's likely at their end. :)
no subject
Date: 2004-03-15 10:24 am (UTC)From what the second tech told me, once it gets into a situation where it thinks it has to go into standby, *only* letting it power up and then once it's gotten to that "standby" state, pressing the power button will get it working right again. Worse yet, it can be pinging by the cable company, and it'll provide an IP address to a user. It just won't pass packets!