![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Sep. 27th, 2004 05:06 pmI haven't posted lately because... our router died. Kaboom!
Well, less kaboom that a complete failure to respond. See, I was upgrading firmware. (And I'm sure y'all already know the ending to any computer story that begins with upgrading firmware.) And I got a click-to-continue screen... and then the connection timed out. And so I waited a bit, since it might have been rebooting... and the connection timed out again. So I whipped out the wireless computer (rule one: always upgrade firmware from a wired computer) and ... couldn't find any connection at all. Nary a network to be seen, not even a "default" or a "wireless." And the wired computer still timed out trying to reach the IP of the router it was connected to.
So I ended up spending somewhere in the vicinity of an hour and a half on the phone with the D-Link folks, attempting to convince them that it had, in fact, gone kaboom. And not just a little kaboom. The first guy was an ass and didn't know tech worth shit. He kept accusing me of not doing things right when his "solutions" didn't work. And he didn't even ask me the most basic questions ("Are the lights still flashing?" and "Is the WLAN light on?"). And I had to explain to him three or four times, minimum, that I had been connected one second and then the connection went dead post-firmware upgrade. He kept saying things like "okay, what if you unplug the power for thirty seconds?" and I'd say "I did that" and he'd say "well, do it again" and I'd do it again, and when it didn't work he'd say "are you sure you unplugged it from the power?" Grrrrr. Then he started being all accusatory and trying to tell me it was a problem with my computer, and wanted me to run winipconfig on the wired computer. And naturally it didn't work (duh! it can't reach the IP address of the router, buddy, and nothing changed on the computer, so bite me). But then I accidentally hung up on him (no, really an accident. but probably subconsciously not so much.) and phoned again and ended up with a much nicer guy who had me try a manual reset just the once and then, once he understood that the wired computer and the wireless computer couldn't detect the router's existence, gave me an rma number. Eeeesh.
So currently, we have no router, and can only connect to the internet through the verizon modem one computer at a time! So sad.
Well, less kaboom that a complete failure to respond. See, I was upgrading firmware. (And I'm sure y'all already know the ending to any computer story that begins with upgrading firmware.) And I got a click-to-continue screen... and then the connection timed out. And so I waited a bit, since it might have been rebooting... and the connection timed out again. So I whipped out the wireless computer (rule one: always upgrade firmware from a wired computer) and ... couldn't find any connection at all. Nary a network to be seen, not even a "default" or a "wireless." And the wired computer still timed out trying to reach the IP of the router it was connected to.
So I ended up spending somewhere in the vicinity of an hour and a half on the phone with the D-Link folks, attempting to convince them that it had, in fact, gone kaboom. And not just a little kaboom. The first guy was an ass and didn't know tech worth shit. He kept accusing me of not doing things right when his "solutions" didn't work. And he didn't even ask me the most basic questions ("Are the lights still flashing?" and "Is the WLAN light on?"). And I had to explain to him three or four times, minimum, that I had been connected one second and then the connection went dead post-firmware upgrade. He kept saying things like "okay, what if you unplug the power for thirty seconds?" and I'd say "I did that" and he'd say "well, do it again" and I'd do it again, and when it didn't work he'd say "are you sure you unplugged it from the power?" Grrrrr. Then he started being all accusatory and trying to tell me it was a problem with my computer, and wanted me to run winipconfig on the wired computer. And naturally it didn't work (duh! it can't reach the IP address of the router, buddy, and nothing changed on the computer, so bite me). But then I accidentally hung up on him (no, really an accident. but probably subconsciously not so much.) and phoned again and ended up with a much nicer guy who had me try a manual reset just the once and then, once he understood that the wired computer and the wireless computer couldn't detect the router's existence, gave me an rma number. Eeeesh.
So currently, we have no router, and can only connect to the internet through the verizon modem one computer at a time! So sad.
