Does named pipes use ports to communicate? Named pipes i use: http://msdn.microsoft.com/en-us/library/aa365150%28VS.85%29.aspx
445 is not a SQL port, is a SMB port. It is involved in SQL Server only if you use named pipes protocol, as named pipes are over SMB and this in turn uses 445 for 'SMB over IP', aka. as SMB 'NETBIOSless' as opposed to the old NetBIOS based SMB, which uses 137-139.
In General, TCP/IP protocol is better in a slow LAN, WAN, or dial-up network. The Named Pipes protocol can be a better choice when the network speed is high, as it offers more functionality, easier to use, and have more configuration options.
A named pipe is a logical connection, similar to a TCP session, between a client and server that are involved in a Common Internet File System (CIFS)/SMB/SMB Version 2 and Version 3 connection.
Yes, when communicating with remote machines it uses ports 137 and 139 UDP and potentially 445 TCP.
Locally pipes are implemented via MMF (memory mapped files).
Essentially some of the facilities used in the CIFS/SMB protocol are also used for named pipes when communicating with remote machines.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With