This FUCKING SQLSlammer keeps getting me - GoFuckYourself.com

hybrid · 04-05-2003, 07:16 AM

Anyone know how to keep it out for good?

My firewall keeps shutting down whenever it hits. I'm using McAfee.

bigdog · 04-05-2003, 07:28 AM

what is it excatly?

NineNine · 04-05-2003, 07:45 AM

Sounds like a shitty firewall. Just close that port. It's the port that SQL Server communicates on... I think at least one of 'em is 1733. Or just ignore it. It can't hurt you if you have SQL Server updated and secured, or if you don't have SQL Server at all.

hybrid · 04-05-2003, 07:49 AM

I don't know how to close any ports....there does'nt seem to be an option for that on my firewall.

SQLSlammer is the bug that hit the net about a month ago, it was on the news and shit.

Any suggestions for better firewalls?

Loch · 04-05-2003, 07:49 AM

Just run the latest win2k updates and sql server updates.
That is good enough.

Or get a real firewall, can recomend Cisco.
For a software firewall use Sygate firewall that keeps it out as well.
www.sygate.com

Lensman · 04-05-2003, 08:10 AM

Here's how to fix it. You need to patch SQL Server with the patch published, or better yet, install Service Pack 3. The problem is that the the patch requires Service Pack 2 and if you haven't installed SP2, the patch will not work and SQL won't see your data. The bigger problem is that installing SP2 will start SQL server and the slammer will kick in before the install completes.

So the only fix is for your host to install SP2 and SP3 with the network cable unplugged on your box. Then you're fine.

hybrid · 04-05-2003, 05:47 PM

Thanks, Lens

04-05-2003, 07:16 AM	#1
hybrid So Fucking Banned Join Date: Jul 2002 Location: Backseat of a Ford Escort Hatchback Posts: 3,253	This FUCKING SQLSlammer keeps getting me Anyone know how to keep it out for good? My firewall keeps shutting down whenever it hits. I'm using McAfee.

04-05-2003, 07:49 AM	#5
Loch Confirmed User Industry Role: Join Date: Feb 2002 Location: Canada Posts: 7,674	Just run the latest win2k updates and sql server updates. That is good enough. Or get a real firewall, can recomend Cisco. For a software firewall use Sygate firewall that keeps it out as well. www.sygate.com __________________ Contact us for Beta store access (4000 HD/SD productions) - Editing - Encoding/Post production ICQ - 277 862 930 E-mail casper /@/ cool-content.com

04-05-2003, 07:28 AM	#2
bigdog Confirmed User Join Date: Jul 2001 Posts: 6,964	what is it excatly?

04-05-2003, 07:45 AM	#3
NineNine So Fucking Banned Join Date: Sep 2002 Posts: 256	Sounds like a shitty firewall. Just close that port. It's the port that SQL Server communicates on... I think at least one of 'em is 1733. Or just ignore it. It can't hurt you if you have SQL Server updated and secured, or if you don't have SQL Server at all.

04-05-2003, 08:10 AM	#6
Lensman GFY Chaperone Join Date: Jan 2001 Location: Adult.com Posts: 9,846	Here's how to fix it. You need to patch SQL Server with the patch published, or better yet, install Service Pack 3. The problem is that the the patch requires Service Pack 2 and if you haven't installed SP2, the patch will not work and SQL won't see your data. The bigger problem is that installing SP2 will start SQL server and the slammer will kick in before the install completes. So the only fix is for your host to install SP2 and SP3 with the network cable unplugged on your box. Then you're fine.

04-05-2003, 05:47 PM	#7
hybrid So Fucking Banned Join Date: Jul 2002 Location: Backseat of a Ford Escort Hatchback Posts: 3,253	Thanks, Lens