I’m reading up on a switch, the Extreme Networks Summit 48si, and it has the following caution:
They can emit invisible laser radiation! How cool is that??
PS If this image cuts off the right-hand side menu, you’re probably using a sucky browser with poor CSS stylesheet support, like MSIE. It’s supposed to shrink down, and does with Firefox.
After the big switch of yesterday, I figured everything would be working great. I updated the DNS entries, and things were running fine—except in the office. For some unholy reason, our Windows 2003 domain server thinks it’s a DNS server for things other than our own internal domain. I don’t really even know how I got it fixed, but after running ipconfig /flushdns a few times, and messing around in the DNS admin stuff, I finally got it to go to the authoritative DNS servers for our web domain and fetch the new information.
So it’s okay, right? Problem fixed? Not likely. All the internal office computers picked up the change after the local domain server got kicked a few times, so they’re pinging the right server now. Outlook, however, does its own thing. Despite the fact that each computer is now resolving our mailserver’s IP address properly, Outlook is doing its own thing, and connecting to the old IP address.
Now one would think that, upon startup, Outlook should at least verify that things haven’t changed. I totally understand caching the information, but only on a per-session basis. We’re having to reboot office machines just because Outlook won’t let go of the old address.
So I must add Microsoft Outlook to my list of Astoundingly Stupid Things.