Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Why Named Pipes is blocked to be used as a Client Library from CCM 3.3(2)

Can someone tell me why client configuration has to be only TCP/IP instead of Named Pipes (as supported earlier) from CCM 3.3(2)? Was Named Pipes identified to have any securiy loophole? Any pointers or EDCS document explaining this change would also be very helpful.

1 REPLY
Cisco Employee

Re: Why Named Pipes is blocked to be used as a Client Library fr

Hello,

Even though Named Pipes is not enabled by default, you should still able to enable and choose it. I thought it is a SQL2000 (CM3.3) setting as opposed to SQL7.0 (CM 3.0/1/2).

Recently there has been a DDTS opened for Named Pipes issues: CSCea08798, maybe you could use that to find the DEs responsible for this piece.

-ben

93
Views
0
Helpful
1
Replies
CreatePlease to create content