![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
My bike computer wasn't working this morning, so all the way in I was thinking "OK, sensor's dead? Mount broken? Wire damaged?" But after getting to work and checking it turns out that when I repacked my front wheel bearings on the bike yesterday, I put the front wheel back on backwards so the magnet was just facing the wrong way. There's the "Duh" for the day. Flip.
I've spent several days worth of time in the last couple of weeks configuring new machines. Back-to-school time seemed like a good time to pick up cheap machines, so we picked up a couple. Jenn's machine is a replacement and the old machine is moving out of the house, so it's retaining the "Penfold" name. Mine is a new one; my old desktop "Zim" is out doing DVR duty in the living room, my laptop "Gir" is still around, though it drove me nuts trying to use it as a primary machine, so the new machine at my desk is dubbed "Daggett". I really need to get some character stickers for these machines, I keep forgetting their names. It's funny, I am not the kind to name inanimate objects; none of my machines at work have names, none of my cars, bikes, or anything else have ever had names, and I think the whole concept is kind of weird. But giving machines at work names was a habit I got into so I could more easily browse them on the network.
But for some reason WinNS hasn't worked for me on our network for a long time. It USED to work back in the Win98 days but I have never gotten it set up right after that. So I do a lot of start/run \\192.168.1.4\recordings. Not ideal but my short-term lazy is winning over long-term lazy. I suppose someday I should set it up. Windows USED to negotiate a master name server. Hmm, maybe this all came about when I moved from using a Linux box (which I had set to use Samba as the WinNS master) to using an appliance router/DHCP. Maybe there's just a setting on the router I can make, since when I log into the router IT knows all the machines names.
I've spent several days worth of time in the last couple of weeks configuring new machines. Back-to-school time seemed like a good time to pick up cheap machines, so we picked up a couple. Jenn's machine is a replacement and the old machine is moving out of the house, so it's retaining the "Penfold" name. Mine is a new one; my old desktop "Zim" is out doing DVR duty in the living room, my laptop "Gir" is still around, though it drove me nuts trying to use it as a primary machine, so the new machine at my desk is dubbed "Daggett". I really need to get some character stickers for these machines, I keep forgetting their names. It's funny, I am not the kind to name inanimate objects; none of my machines at work have names, none of my cars, bikes, or anything else have ever had names, and I think the whole concept is kind of weird. But giving machines at work names was a habit I got into so I could more easily browse them on the network.
But for some reason WinNS hasn't worked for me on our network for a long time. It USED to work back in the Win98 days but I have never gotten it set up right after that. So I do a lot of start/run \\192.168.1.4\recordings. Not ideal but my short-term lazy is winning over long-term lazy. I suppose someday I should set it up. Windows USED to negotiate a master name server. Hmm, maybe this all came about when I moved from using a Linux box (which I had set to use Samba as the WinNS master) to using an appliance router/DHCP. Maybe there's just a setting on the router I can make, since when I log into the router IT knows all the machines names.
