Failure to connect error

I recently got a new computer that I use to connect to a SQL 2000 Server and
as soon as I started connecting to the server using QA and EM, the Air Force
base communications center called saying they were showing 1700 failure to
connect messages on ports, 1134,139, and 445. I connect just fine with no
errors and performance is just fine. I am assuming my new computer has some
protocol enabled that is sending broadcast messages to the server on these
ports that are not required and also on the bases hit list. Any Ideas?OK,,,Found the culprit. I had Server State polling turned on. This is
located under Tools_Opotions of the Enterprise Manager. Seems my machine wa
s
going out every second on port 1434 and the firewall was responding on port
445 saying no can do. I think the Slammer virus used 1434 so thats why it wa
s
disabled. Also I had NetBios enabled in the TPC/IP properties.
"AkAlan" wrote:

> I recently got a new computer that I use to connect to a SQL 2000 Server a
nd
> as soon as I started connecting to the server using QA and EM, the Air For
ce
> base communications center called saying they were showing 1700 failure to
> connect messages on ports, 1134,139, and 445. I connect just fine with no
> errors and performance is just fine. I am assuming my new computer has som
e
> protocol enabled that is sending broadcast messages to the server on these
> ports that are not required and also on the bases hit list. Any Ideas?