I have a SQL server 2000 with service pack 3 installed.
This morning I saw that its CPU utilization is about 98%
and it was broadcasting something to all network
computers.
I checked for any virus but nothing found.
Could you help me?It's most likely slammer. Have a look here:
http://www.aspfaq.com/show.asp?id=2440 SQL Slammer info
--
Andrew J. Kelly
SQL Server MVP
"payman" <paymanzafar@.yahoo.com> wrote in message
news:05fe01c3b0d0$7d80e030$a401280a@.phx.gbl...
> I have a SQL server 2000 with service pack 3 installed.
> This morning I saw that its CPU utilization is about 98%
> and it was broadcasting something to all network
> computers.
> I checked for any virus but nothing found.
> Could you help me?
Showing posts with label broadcast. Show all posts
Showing posts with label broadcast. Show all posts
Sunday, February 19, 2012
Broadcast Storm
Broadcast existence of SQL Server
Hi All:
Does anyone know where to find the property that disables the broadcast of the sql server from the point where you do not see the server show up in the list when one goes to
"New SQL Server Registration" -> "..."
beside the "Server" field. The dialog itself is titled "Registered SQL Server Properties". Assume both SQL Servers are both behind the firewall.While it isn't 100%, you can get a good start by disabling the Named Pipes Broadcast (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_97cb.asp) for SQL Server.
-PatP|||Thanks for the reg key option. For some reason I seemed to remember seeing an option where you can set this from the enterprise UI. I could be wrong but does anyone remember anything along those lines.|||Thanks for the reg key option. For some reason I seemed to remember seeing an option where you can set this from the enterprise UI. I could be wrong but does anyone remember anything along those lines.
Start->Programs->SQL Server->Server Network Utility; in the General Tab, select TCPIP. Select Properties, Check the option HIDE SERVER.
it would force SQL stop broad casting the port it's listening to.|||Start->Programs->SQL Server->Server Network Utility; in the General Tab, select TCPIP. Select Properties, Check the option HIDE SERVER.
it would force SQL stop broad casting the port it's listening to.I think that is only a choice for named instances of SQL Server.
-PatP|||I think that is only a choice for named instances of SQL Server.
-PatP
Hi. This is what BOL says.
[Hide server
Select to hide the instance of Microsoft SQL Server. When you hide an instance of SQL Server, responses to broadcasts from clients attempting to enumerate those instances of SQL Server present on the network are disabled.]
named instance is not exclusively mentioned; have to test the scenario
Does anyone know where to find the property that disables the broadcast of the sql server from the point where you do not see the server show up in the list when one goes to
"New SQL Server Registration" -> "..."
beside the "Server" field. The dialog itself is titled "Registered SQL Server Properties". Assume both SQL Servers are both behind the firewall.While it isn't 100%, you can get a good start by disabling the Named Pipes Broadcast (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_security_97cb.asp) for SQL Server.
-PatP|||Thanks for the reg key option. For some reason I seemed to remember seeing an option where you can set this from the enterprise UI. I could be wrong but does anyone remember anything along those lines.|||Thanks for the reg key option. For some reason I seemed to remember seeing an option where you can set this from the enterprise UI. I could be wrong but does anyone remember anything along those lines.
Start->Programs->SQL Server->Server Network Utility; in the General Tab, select TCPIP. Select Properties, Check the option HIDE SERVER.
it would force SQL stop broad casting the port it's listening to.|||Start->Programs->SQL Server->Server Network Utility; in the General Tab, select TCPIP. Select Properties, Check the option HIDE SERVER.
it would force SQL stop broad casting the port it's listening to.I think that is only a choice for named instances of SQL Server.
-PatP|||I think that is only a choice for named instances of SQL Server.
-PatP
Hi. This is what BOL says.
[Hide server
Select to hide the instance of Microsoft SQL Server. When you hide an instance of SQL Server, responses to broadcasts from clients attempting to enumerate those instances of SQL Server present on the network are disabled.]
named instance is not exclusively mentioned; have to test the scenario
Subscribe to:
Posts (Atom)