RE: SQLOLEDB always uses Named Pipes

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



Hi Doug,
You may check the ProtocolOrder value in the following registry key to see
if the order is "tcp np":
HKLM\Software\Microsoft\MSSQLServer\Client\SuperSocketNetLib
If the order is right, but your clients still prefer Named Pipes, there
might be a protocol cache in Network Library.

In this case, you may try the following three methods:
1. Disable the Named Pipes protocol in the client machine by cliconfg.exe;
2. Explicitly specify tcp: prefix to your server instance name.
For example:
--specify TCP/IP as the communication protocol
osql /Stcp:CharlesSQL-01 /E

--specify Named Pipes as the communication protocol
osql /Snp:CharlesSQL-01 /E

3. Add an alias with TCP/IP protocol by using cliconfg.exe and use the
alias to connect to your SQL Server.

Hope this helps. Please feel free to let me know if you have any questions
or concerns.
Have a good day!

Best regards,
Charles Wang
Microsoft Online Community Support
=====================================================
Get notification to my posts through email? Please refer to:
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications

If you are using Outlook Express, please make sure you clear the check box
"Tools/Options/Read: Get 300 headers at a time" to see your reply promptly.


Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscriptions/support/default.aspx.
======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================






.



Relevant Pages

  • [git pull] Input updates for post-2.6.21
    ... psmouse - allow disabing certain protocol extensions ... cobalt buttons - separate device and driver registration ... wistron - add support for TravelMate 610 ... ads7846 - add support for the ads7843 touchscreen ...
    (Linux-Kernel)
  • Re: IIS - Internet Explorer - Not Prompting for Credentials
    ... protocol to perform integrated auth with IIS. ... Microsoft Online Community Support ... where an initial response from the community or a Microsoft Support ...
    (microsoft.public.inetserver.iis.security)
  • Re: locking an int
    ... I disagree is that re-inventing the wheel is a good thing. ... Most development languages have support for SOAP or even HTTP communication this day and age, ... It's the use of the ..NET-specific features that may lead to "reinventing the wheel", as if the other end-point is not a .NET application, someone will have to reimplement the .NET protocol, in an environment where doing so it very difficult. ... MS has spent a lot of time developing the remoting services in .NET and they are for the most part cross platform in the right hands and given correct architectural choices, why would you try to re-write this? ...
    (microsoft.public.dotnet.languages.csharp)
  • [PATCH 1/22] trivial: fix typo "a a" in multiple files
    ... * Returns zero if volume is all right and a a negative error code if not. ... NAT support for PPTP (Point to Point Tunneling Protocol). ...
    (Linux-Kernel)
  • oops while booting on 2.6.0test11
    ... NET: Registered protocol family 16 ... PCI: PCI BIOS revision 2.10 entry at 0xf0031, ... Linux Plug and Play Support v0.97 Adam Belay ... # Disk-On-Chip Device Drivers ...
    (Linux-Kernel)