Originally posted by Dont Hurt Me
I thought this thing only was only hitting window machines/servers so that would mean that Mac- - - - - - is not running Macs! WHAT![]()
Originally posted by eric_n_dfw
While I'd love to lie this at M$'s feet - they did, aparently, put out a patch 6 months to a year ago (depending on which report you read) and enough idiot MCSE's didn't bother to install it!![]()
What's worse. Those people put those SQL Servers up available over the internet. SQL Servers are meant to be a BACK END server. An optimal SQL Server configuration would be:Originally posted by eric_n_dfw
While I'd love to lie this at M$'s feet - they did, aparently, put out a patch 6 months to a year ago (depending on which report you read) and enough idiot MCSE's didn't bother to install it!![]()
Originally posted by krossfyter
or some korens?
That's not a good thing. I'm sure that Microsoft.com took as much abuse, if not MUCH more, yet it was up the entire night and it did not receive any performance hit. Engineering the network for speed and response is important. Rejecting traffic for unnecessary ports are important; apparently, Apple did not do this.Originally posted by Sedulous
I was up all night and was shocked Apple Store was affected by this.
I believe that this bug slowed internet traffic in general. If a site is already busy, the extra draw from the bug might make a site inconsistantly available.