Post reply

Disallow Named Pipes

  • August 17, 2005 at 10:09 am

    #187049

    Hi everyone.

    Been tasked to "disallow access over named pipes" to our SQL 2000 SP4 .

    Is this just a case of removing the Named Pipes protocol from both the Client and Server Network Utility ?

    What should I be aware of in doing this , just so I can let the developers know ?

    We have planned to test this after each removal , is this a good idea or a bit over keen ?

    Any advice appreciated so I can get a better understanding.

    Cheers

  • August 17, 2005 at 11:14 am

    #582839

    We did that a few years ago .... No problems that I recall

  • August 18, 2005 at 12:47 am

    #582921

    I would have said the same up until a recent problem has forced us to use named pipes.  Issues can occur using Named instances of sql server and options are use named pipes or fix the port that TCP will use.  Some people fix the port because of firewall requiremrents.  Also some apps need or expect to be able to connect over named pipes.

    Derek

  • August 18, 2005 at 3:36 am

    #582944

    Many thanks for the replies everyone , would anyone be able to confirm that I have detailed the correct proceedure to disallow named pipes please.

     

    Cheers

  • August 18, 2005 at 3:37 am

    #582945

    I did the same some time ago on all our servers. No problems. Just to be sure there will be no issues, I queried sysprocesses table periodically for a week or so before removal to ensure there's nobody/nothing connected through Named Pipes.

    select distinct net_library from master..sysprocesses

  • August 18, 2005 at 6:13 am

    #582975

    Thanks Martin

    Ran that during some testing on another server, not exactly sure what I am seeing.

    Returns 3 rows.

    1           

    2 LPC        

    3 Named Pipes

    Do I need to check to see that the named pipes entry is removed after named pipes have been removed from both Client and server utilities ?

  • August 18, 2005 at 6:25 am

    #582977

    You just go into the Server netowkr utility and stop SQL listening on named pipes.

    It makes no difference to your clients for XP and later MDAC versions because they are set to try tcp first then np.

    Older clients with MDAC 2.5 and before (maybe 2.6) need the protocal order changing.

    It's all server side.

    In my last place, all named pipes were off except for some legacy apps - everything was tcp only, 30 servers.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply