A bit of a lacklustre attempt here from their IT department. It doesn't even finish its sentence, perhaps meaning it goes on for ever and ever without end
This e-mail contains confidential information and is for the exclusive use of the addressee/s. If you are not the addressee, then any distribution, copying or use of this e-mail is prohibited. If received in error, please advise the sender and delete it immediately. We accept no liability for any loss or damage suffered by any person arising from use of this e-mail
Stupid Email Disclaimers makes its glorious return! And never mind that this is legalese nonsense, it's still not enforceable. (This instalment courtesy of QIT Labs.)
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
I encountered a weird problem on a Windows Server 2008 R2 install which had dual NICs on the same physical network (different subnets, DNS and gateways) - you could interrogate its SNMP agent and you wouldn't get a response even though the right community was set and you might initially see it working properly! This borkage would happen indefinitely after beginning, though punctuated with momentary spurts of correct operation (depending on which way the wind was blowing, how you looked at the box, whether you spoke softly to it...) but then arbitrarily breaking again. Intensely frustrating.
From my own analysis, as SNMP traffic is (usually) UDP, the responses were being routed through the wrong interface (Windows' SNMP agent binds automatically to all interfaces on 0.0.0.0:161 and doesn't care about interface order or metrics, even if you define custom metrics -- though you can force it by setting metrics on your connections' default gateways). The incorrectly-identified replies to SNMP requests were also being caught by the firewall (for whatever reason), even though it has the appropriate SNMP rules to allow ingress/egress traffic on UDP 161 and 162 (trap traffic).
But guess what, for once MS has actually issued a fix for this! It's on the Microsoft site via the snappily-named article "Incorrect source IP address is returned in the SNMP response in Windows 8, Windows Server 2012, Windows 7, Windows Server 2008 R2, Windows Vista, and Windows Server 2008". I've applied this to the servers I'm setting up monitoring for, and it works beautifully.
Big kudos to "mobilenow" who linked to this hotfix on the Solarwinds Thwack forum and explained the hotfix was produced after they opened a bug case after similarly trawling the net during production of their ServerSilo monitoring product. Probably worth checking them out.
Hopefully this avoids you wasting as much time as I spent trying to fix this...
Once upon a time, I received the gift of my first very own PC from doting parents. Whilst this was long after getting my first computer (the first was an amazing Acorn A3000, fondly called "The Beast") I still remember the PC's specs well: a Pentium III 450 (on a riser card!), Voodoo Banshee, 128 MB of blazing SDRAM and a 10 GB hard drive. ("I'll never fill all this disk space...")
However, the best thing about that computer: the humble keyboard. After using one ages before getting my own, I knew immediately it was an awesome peripheral. The Microsoft Natural Keyboard Elite (model A11-00337, M/N E06402COMB) is just about everything a hardcore computer-er-y person would ever want: incredibly ergonomic; devoid of a zillion pointless 'hotkey' and Function buttons; a lovely muted yet definitive keypress response, a wrist rest angled 'just right'... and even made in Mexico. ¡Olé!
This little keyboard is a resilient little bugger and it's still trucking. Just some of its previous adventures:
- Half a dozen LAN parties
- Half a dozen housemoves
- Years of frustrated / angry / drunk / careless / overzealous users... (Well, user)
- An entire pint of orange juice (poured into it by yours truly, by accident)
- Countless knocks, drops and bumps, some from considerable height
- Several kilos of toast
- Evidently, several pounds of hair, or two tribbles (we'll get to that)
Add to that the fact that it's both PS/2 (USB with included adapter) AND off-white plastic (mine's beige from age!), all being told it should have died a long time ago. HOWEVER, it just refuses to go! It's amazing and I think I may actually have real feelings of love and concern for this keyboard. Or I might be drunk again. Who can tell.
The only thing it's missing are its little rubber feet from the underside of the front, easily solved with a little bit of (vintage) bluetack. I think you can even reorder those parts from Microsoft.
ANYWAY! I began to wonder, 'what's inside my favourite keyboard of all time? Perhaps it would work like a boxfresh unit if I took it apart and hosed out the rubbish?' (because when you can hear crumbs rattling round inside, it's time to get the desk-vac). Soon, nothing else was to be done except take it apart. And take it apart I did...
If you're still out there... Get in touch.