June 30, 2004 at 11:07 am
I want to understand more about how Named Pipes works between SQL Server and client.
I know the followings:
I'm interesting in knowing:
Thank you.
July 5, 2004 at 8:00 am
This was removed by the editor as SPAM
July 5, 2004 at 8:18 am
Check SQL Server "Books on line" for "named pipes" info, there's plenty of info there.
Max
July 5, 2004 at 9:10 am
Agree there is some info there, but dont know that it answers all of these. Let me see if I can find someone to answer.
July 5, 2004 at 10:28 am
This will explain named pipes a little better:
http://support.microsoft.com/default.aspx?scid=kb;en-us;101150
this aught to help explain what the ports are used for:
http://support.microsoft.com/default.aspx?scid=kb;en-us;150543
My impression over time of network protocols with SQL is that Named Pipes are brilliant in a LAN environment using windows authentification, if you want to use IIS or connect using TCP/IP it's probably better to go for TCP/IP which is according to some of the benchmarks I've read quite impressive too.
Identify which enviorment you fit into and only enable the bare number of protocols, for the "I don't sleep much" network or db administrator you might even want to check it all the way down to each and every connection being made. It's obviously not only a server-side performance issue.
Max
Max
July 5, 2004 at 6:22 pm
Hi Max,
Thank you for the links. I believe this link has better info on ports:
grc.com/PortDataHelp.htm
I have read most, if not all, the information regarding Named Pipes in BOL.
I believe my questions are more related to networking than SQL Server. So, the information in BOL does not really address my questions.
The reason I ask about #2 "When will Named Pipes use port 139 and when will it use port 445?" is that I have problem in establishing communication between client and SQL Server if I close port 139 and open port 445 only. (Note: I'm guessing that the problem may be related to Name Resolution.)
Thank you.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply