How NOT to kill large emails.

When someone sends a 176MB email which takes up your bandwidth, its advisable not to kill the email and send a NonDeliveryReport as the NDR contains the 176MB of data in it too……It’s taken 1.5days of our full bandwidth since this email was sent until I could see it in the mail queue and cancel it again. For some reason the email didn’t appear in the queue so I couldn’t see it attempting to be sent and therefore kill it. In the meantime I’ve had everyone screaming at me as their vpn connections into the office were unusable!
Now its time to go home at last!

My wireless mouse is still

My wireless mouse is still playing up – synching the two radio buttons is having less of an effect. The problem is very intermittent. I’m beginning to wonder if another company in the building has either brought a similar mouse or purchased a lot of RF equipment. In the meantime I’m going to have to reformat the pc as it’s getting slower and slower. My profile on the w2k machine is what makes the machine crash every other time I start explorer or attempt to browse in any way. Logging on as administrator has no problem. Spent part of the day preparing my w2k boot cd so I can install most apps off the one set of media. Shame office won’t fit on the cd!

Exchange is back and running

Exchange is back and running in the office and all the users were really happy – for 30 minutes.. Then the other techie pulled the plug on the servers for the best part of the day whilst they were all cabled up correctly in the cable management trays (would have been nice if this had been done whilst the servers were unusable – but thats IT timing for you 🙂

Got my wireless mouse working

Got my wireless mouse working again after it stopped working. For some reason (I think the batteries must have got flat as I forgot to place it back in the charger) the mouse wouldn’t talk to the base unit. A quick reset on the mouse AND the baseunit and it started working again. I was getting worried as I really didn’t want to go back to a corded version.

Interesting to see that I

Interesting to see that I got another security email from microsoft due to the patches that were originally issued in Oct 2002 which would have prevented against the slammer worm that crippled the internet over the weekend. At least this time the hackers were sensible in that they waited until everyone went home. That way they could almost guarantee they would get maximum exposure as the only people who are likely to run Microsoft SQL2000 are business’s and most admin guys are going to be safely home on a Friday night. And if they are not good enough admins to have already patched their servers, then they are not likely to have pagers to be called in to fix the problem. One of my (backup) isp’s was pretty badly crippled – a lot of their servers were unavailable although they did send me an email to say they were pulling the plug on people who had bad servers – don’t blame them.
So just how long is it going to be before they manage to crash all of the root servers? Incidentally I dcpromo’d my home server last night and it killed my local network as it made itself a dns server, stopped dns and dhcp working from my router and also refused to forward dns requests onto the internet for me. As I didnt have time to work that one out, it was a quick dcpromo back to a standalone server until I have time to read up on dns in w2k.