Enterprise Manager Use of Port 445

SQL Server 2005 Enterprise Manager running on a Windows 2003 member server
is constantly trying to reach the remote SQL Server on port 445. That
implies that File & Printer Sharing would be turned on at the destination
SQL Server. We do turn on File & Printer sharing lightly on servers
because of the security implications, so in this case the Enterprise Manager
cannot connect on port 445. It is still trying to do this persistently,
and even after the admin connects to the database and starts using it, the
Enterprise Manager is persisting repeatedly, forever, to connect on port
445.
What specific functionality is Enterprise Manager attempting to invoke on
the target by use of port 445? Is it something as simple as an
automatic service start request to the SQL Server service on the target
machine?
--
WillHi Will
SQL Server 2005 has Management Studio and not Enterprise Manager.
Port 445 is used in for Named Pipes, if your server is not using this
protocol it should be disabled in the server configuration tool.
John
"Will" wrote:
> SQL Server 2005 Enterprise Manager running on a Windows 2003 member server
> is constantly trying to reach the remote SQL Server on port 445. That
> implies that File & Printer Sharing would be turned on at the destination
> SQL Server. We do turn on File & Printer sharing lightly on servers
> because of the security implications, so in this case the Enterprise Manager
> cannot connect on port 445. It is still trying to do this persistently,
> and even after the admin connects to the database and starts using it, the
> Enterprise Manager is persisting repeatedly, forever, to connect on port
> 445.
> What specific functionality is Enterprise Manager attempting to invoke on
> the target by use of port 445? Is it something as simple as an
> automatic service start request to the SQL Server service on the target
> machine?
> --
> Will
>
>|||My guess is that it is SSMS that periodically check if the instance is running (service is
starting). In 2000's EM, you could configure whether to do this with the registration, but I didn't
find such an option in SSMS...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Will" <westes-usc@.noemail.nospam> wrote in message
news:OoSdnTJTDtYbFpDanZ2dnUVZ_jWdnZ2d@.giganews.com...
> SQL Server 2005 Enterprise Manager running on a Windows 2003 member server is constantly trying to
> reach the remote SQL Server on port 445. That implies that File & Printer Sharing would be
> turned on at the destination SQL Server. We do turn on File & Printer sharing lightly on servers
> because of the security implications, so in this case the Enterprise Manager cannot connect on
> port 445. It is still trying to do this persistently, and even after the admin connects to the
> database and starts using it, the Enterprise Manager is persisting repeatedly, forever, to connect
> on port 445.
> What specific functionality is Enterprise Manager attempting to invoke on the target by use of
> port 445? Is it something as simple as an automatic service start request to the SQL Server
> service on the target machine?
> --
> Will
>|||Tibor Karaszi (tibor_please.no.email_karaszi@.hotmail.nomail.com) writes:
> My guess is that it is SSMS that periodically check if the instance is
> running (service is starting). In 2000's EM, you could configure whether
> to do this with the registration, but I didn't find such an option in
> SSMS...
You can make it happen less often if you set
HKLM\Software\Microsoft\Microsoft SQL Server\90\Tools\Shell\PollingInterval
to a suitable value. The unit is apparently centiseconds. See
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=247367.
Beware that on a 64-bit machine the location is
HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90\Tools\Shell
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:1B1E5FB9-7471-4623-A237-55F873D6B7F4@.microsoft.com...
> SQL Server 2005 has Management Studio and not Enterprise Manager.
> Port 445 is used in for Named Pipes, if your server is not using this
> protocol it should be disabled in the server configuration tool.
Apparently my programmer is using a third party administrator tool. I'm
sure he also uses Enterprise Manager. Are you saying Enterprise Manager
will fail to work on a client when contact SQL Server 2005? He is managing
a production SQL Server 2000 database and just now starting to work with SQL
Server 2005 experimentally.
We already set the client and server protocols at the console of the SQL
Server 2005 computer using the SQL configuration tool, and all protocols
except for TCP and Shared Memory are disabled.
How does the client bootstrap which protocol to use to initiate connection
to the server? There is a catch 22 there where the client does not know
the server configuration regarding client protocols until after client
connects. How does the server communicate its client protocol settings
back to the client? Client is just attempting named pipes no matter what,
then backing off to TCP as a second choice, and once connection is made,
then obeying client protocol rules configured on the server?
--
Will
> "Will" wrote:
>> SQL Server 2005 Enterprise Manager running on a Windows 2003 member
>> server
>> is constantly trying to reach the remote SQL Server on port 445. That
>> implies that File & Printer Sharing would be turned on at the destination
>> SQL Server. We do turn on File & Printer sharing lightly on servers
>> because of the security implications, so in this case the Enterprise
>> Manager
>> cannot connect on port 445. It is still trying to do this persistently,
>> and even after the admin connects to the database and starts using it,
>> the
>> Enterprise Manager is persisting repeatedly, forever, to connect on port
>> 445.
>> What specific functionality is Enterprise Manager attempting to invoke on
>> the target by use of port 445? Is it something as simple as an
>> automatic service start request to the SQL Server service on the target
>> machine?
>> --
>> Will
>>|||"Erland Sommarskog" <esquel@.sommarskog.se> wrote in message
news:Xns99C728CF744BYazorman@.127.0.0.1...
> Tibor Karaszi (tibor_please.no.email_karaszi@.hotmail.nomail.com) writes:
>> My guess is that it is SSMS that periodically check if the instance is
>> running (service is starting). In 2000's EM, you could configure whether
>> to do this with the registration, but I didn't find such an option in
>> SSMS...
> You can make it happen less often if you set
> HKLM\Software\Microsoft\Microsoft SQL
> Server\90\Tools\Shell\PollingInterval
> to a suitable value. The unit is apparently centiseconds. See
> https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=247367.
> Beware that on a 64-bit machine the location is
> HKLM\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90\Tools\Shell
When I went to the appropriate location on a 32-bit machine, the
PollingInterval Value does not exist. Should I create it and what Value
type should it be?
Since my programmer is using an older management client, my guess is the
port 445 behavior we are seeing is specific to that tool and not
controllable by this registry value, but no harm in trying to change its
value and seeing effect on client behavior.
Is there really nothing that can be set on the client computer itself as a
guideline for behavior of client applications? Are applications like
Enterprise Manager and Management Studio using any specific database API
like OLEDB, or are they using proprietary protocols?
--
Will|||Will (westes-usc@.noemail.nospam) writes:
> When I went to the appropriate location on a 32-bit machine, the
> PollingInterval Value does not exist. Should I create it and what Value
> type should it be?
Yes, you need to create it. I only have it on my machine at home, but I
believe it was a DWORD. The reason I looked into this, is that I had the
same problem as in the bug report.
> Since my programmer is using an older management client, my guess is the
> port 445 behavior we are seeing is specific to that tool and not
> controllable by this registry value, but no harm in trying to change its
> value and seeing effect on client behavior.
Is that some non-MS product? In your original post you said "SQL Server 2005
Enterprise Manager", but there is no such beast. If your programmer simply
running the old Enterprise Manager from SQL 2000, simply have him to
delete that registration, or uncheck the option to display server status.
> Is there really nothing that can be set on the client computer itself as a
> guideline for behavior of client applications? Are applications like
> Enterprise Manager and Management Studio using any specific database API
> like OLEDB, or are they using proprietary protocols?
The client computer is the only place where you can set this. Obviously.
And typically it's per application, since it's the application that polls
the server.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Will (westes-usc@.noemail.nospam) writes:
> We already set the client and server protocols at the console of the SQL
> Server 2005 computer using the SQL configuration tool, and all protocols
> except for TCP and Shared Memory are disabled.
> How does the client bootstrap which protocol to use to initiate
> connection to the server? There is a catch 22 there where the client
> does not know the server configuration regarding client protocols until
> after client connects. How does the server communicate its client
> protocol settings back to the client? Client is just attempting named
> pipes no matter what, then backing off to TCP as a second choice, and
> once connection is made, then obeying client protocol rules configured
> on the server?
You control this with with SQL Configuration Manager or the Client Network
Utility in the SQL 2000 toolset. There you set up in which order the client
is to attempt which protocols.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx|||Will wrote on Thu, 11 Oct 2007 20:03:45 -0700:
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message news:1B1E5FB9-7471-4623-A237-55F873D6B7F4@.microsoft.com...
>> SQL Server 2005 has Management Studio and not Enterprise Manager.
>> Port 445 is used in for Named Pipes, if your server is not using this
>> protocol it should be disabled in the server configuration tool.
> Apparently my programmer is using a third party administrator tool. I'm
> sure he also uses Enterprise Manager. Are you saying Enterprise
> Manager will fail to work on a client when contact SQL Server 2005? He
> is managing a production SQL Server 2000 database and just now
> starting to work with SQL Server 2005 experimentally.
Enterprise Manager does not work with SQL Server 2005. SMSS will work with
SQL Server 2000 and 2005, but not version 7 or lower. Makes my job here fun,
as I'm having to support 7, 2000, and 2005 and so have to use both EM and
SMSS. It also means that there's no GUI for handling setting up replication
between 2005 and 7 either, it all has to be done using T-SQL - but it does
work :)
Dan