Feb 13, 2009 · Named Pipes has to use NTLM. Until SQL Server 2008, there is no option to use anything but. And even in SQL Server 2008, it means being aware of a potential additional SPN that's not needed for ...

Jun 18, 2011 · Check the Configuration Manager for SQL Server. Someone may have turned off Named Pipes as a protocol. EDIT: Also, check the box that the application is running on.

Sep 24, 2003 · Named Pipes will travel across whatever protocols the OS is using. For instance, if the OS is configured to use TCP/IP, Named Pipes will travel across it. So from a network perspective it won't ...

Sep 19, 2010 · Named pipes and TCP\IP both have networking advantages, TCP\IP is more resilient and generally preferred. There's reams of info on this if you look around "Ya can't make an omelette without ...

Feb 13, 2009 · Named pipes are a way to pass information between two processes. Think of like an electronic form of the mail tubes used at bank teller windows. You put a 'packet' of information into the tube and ...

Oct 23, 2002 · If the server application is running locally on the computer running an instance of Microsoft® SQL Server™ 2000, the local Named Pipes protocol is an option. Local named pipes runs in kernel ...

Sep 26, 2009 · Named Pipes. Named Pipes is an authenticated protocol. This means that any time a user attempts to open a connection to the SQL Server via Named Pipes, the Windows NT authentication process occurs ...

Jun 24, 2004 · On my system users connect with Named pipes one day, TCP/IP the next and named pipes the following day. At the moment I have 2 users on named pipes and 40 on TCP/IP.

Nov 1, 2011 · The timeout is, I suspect, coming from trying TCP/IP and then falling back to named pipes. Is this an older connection or is it using the newer SNAC client? Viewing 9 posts - 1 through 8 (of 8 total)

2017-07-14 08:22:55.01 Exception Message: Named Pipes Provider: Could not open a connection to SQL Server [5]. Sue_H - Thursday, July 13, 2017 4:04 PM Was the snapshot ever generated?