| Subject: | Re: Cannot Connect to SQL 2000 |
|---|---|
| From: | Adam Cameron <adam_junk@xxxxxxxxxxx> |
| Date: | Fri, 26 Oct 2007 20:52:49 +0100 |
| Newsgroups: | macromedia.coldfusion.database_access |
> In any case applying the SP probably wouldn't hurt. Yep. Patch it up, and try again. I realise Lynda said that the computer in question is a local PC, so probably is not outwardly facing (ie: onto the 'net). But this warning could still be relevant: A couple of years ago - long after SQL Slammer had done the rounds, so one might think it was no longer a problem - one of our jr developers was tasked with setting up a new SQL Server instance which ended up being outwardly facing. She didn't remember to patch it (and I - the box was my responsibility - forgot to check). It took about half an hour of uptime for it to get infected, and about 15min after that before our LAN was flattened by virus-enabled traffic trying to find other machines to infect. Suddenly 20-odd people could not work whilst we cleaned out their machines, and checked for any number of other infections. I was not popular that day (not least of all with myself!). Always... ALWAYS... make sure your SQL Servers are fully patched. I would *never* attach a machine with non-patched SQL Server even to a LAN, let alone the outside world. I cannot stress that enough. -- Adam |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Cannot Connect to SQL 2000, cf_dev2 |
|---|---|
| Next by Date: | Re: Outputting sub categories under parent from database, William At FAA |
| Previous by Thread: | Re: Cannot Connect to SQL 2000, cf_dev2 |
| Next by Thread: | Re: Cannot Connect to SQL 2000, cf_dev2 |
| Indexes: | [Date] [Thread] [Top] [All Lists] |