![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Mar. 2nd, 2005
(no subject)
Mar. 2nd, 2005 08:37 pmHmm.
So after managing to wedge small but significant parts of windows by pulling the wireless card out without stopping it first, my laptop seems to have screwed up small but significant bits to do with networking.
Why else would I get "Destinaiton host unreachable" when trying to ping something in the same subnet, and actually manage to make ping.exe crash when trying 127.0.0.1? Not to mention the shell restarting every time I tried to get at the network connections to beat them into submission. Oh, and it then going down with a "Hard error" on shutdown.
Well, I've rebooted it, and am now ready to attack the networking again.
Or not... as it's now working fine. Hmm. Must be some really funky race condition involving the networking hardware, windows, the tcp stack, and the ibm networking software.
Or just my laptop hates me.
So after managing to wedge small but significant parts of windows by pulling the wireless card out without stopping it first, my laptop seems to have screwed up small but significant bits to do with networking.
Why else would I get "Destinaiton host unreachable" when trying to ping something in the same subnet, and actually manage to make ping.exe crash when trying 127.0.0.1? Not to mention the shell restarting every time I tried to get at the network connections to beat them into submission. Oh, and it then going down with a "Hard error" on shutdown.
Well, I've rebooted it, and am now ready to attack the networking again.
Or not... as it's now working fine. Hmm. Must be some really funky race condition involving the networking hardware, windows, the tcp stack, and the ibm networking software.
Or just my laptop hates me.
(no subject)
Mar. 2nd, 2005 08:50 pmOkay, now my desktop is being moody. The network cable *is* plugged in - I can see the 3 green lights on the switch which mean it is talking to the network card. So why does it think the cable isn't in?
Right, let's try unplugging it from both ends.
Okay, the switch has lit up green. Windows is still refusing to see the friggin' cable! And I'd rather not restart this machine, as it's the one that I'm a) connected to the internet on; b) playing music from; and c) typing this on. Grumblegrumblegrumble...
*curses windows*
Okay, what is up with this thing? It's even sending packets across! I can ping the laptop across this connection!
Ah sod it, restart.
Right, let's try unplugging it from both ends.
Okay, the switch has lit up green. Windows is still refusing to see the friggin' cable! And I'd rather not restart this machine, as it's the one that I'm a) connected to the internet on; b) playing music from; and c) typing this on. Grumblegrumblegrumble...
*curses windows*
Okay, what is up with this thing? It's even sending packets across! I can ping the laptop across this connection!
Ah sod it, restart.
(no subject)
Mar. 2nd, 2005 09:28 pmFinally got the two to talk sensibly. What I want to know is why they were working with NetBIOS disabled on the laptop quite well until just now. Maybe it's because I've yet to make a blood sacrifice to the laptop. Then again, the desktop has claimed some blood from me (those metal punch-outs leave nice sharp edges behind just waiting to catch a hand stuck through the hole), and that doesn't seem to have improved its tempermanent.
Of course, now my laptop will be plotting revenge, and will probably end up doing it's usual stunt of completely failing to recognise a length of Cat5, or for that matter a 802.11b card, next time I get it to do anything vaguely network-related. Knowing past experience, I'll probably get fed up and go back to the stone age of NetBEUI and water-powered 386 computers. They were more reliable, too.
Of course, now my laptop will be plotting revenge, and will probably end up doing it's usual stunt of completely failing to recognise a length of Cat5, or for that matter a 802.11b card, next time I get it to do anything vaguely network-related. Knowing past experience, I'll probably get fed up and go back to the stone age of NetBEUI and water-powered 386 computers. They were more reliable, too.
