Post reply

TCP/IP and NamedPipes

  • March 12, 2009 at 4:59 am

    #200778

    Hello.

    In my SQL-Server 2005x64 i have connections TCP/IP and NamedPipes from the same VB6 application from different hosts.

    Any idea?

    Thanks.

  • March 12, 2009 at 5:33 am

    #958194

    TCP\IP is used for all the network cnnections.NAMED PIPES is used for connections within your machine.

  • March 12, 2009 at 6:01 am

    #958230

    Thanks Grasshopper

    All remote conections are outside de server.

    There are over 500 conections TCP/IP and 3 or 4 Named pipes connections for the same application.

    I don't understand...

  • March 12, 2009 at 6:22 am

    #958246

    Hi,

    Does you VB application use DSN? It is possible to configure those to use Named Pipes instead of TCP. SQL Server will communicate over either protocol. If you don't want to use named pipes you can disable it in SQL Server Configuration Manager.

    Thanks.

    Mohit.

    [font="Arial"]---

    Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
    Microsoft FTE - SQL Server PFE

    * Some time its the search that counts, not the finding...
    * I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]

    How to ask for help .. Read Best Practices here[/url].

  • March 12, 2009 at 6:30 am

    #958252

    Yes, my VB app uses DNS name to connect.

    But, How is it possible that some hosts are connected with TCP/IP and others with the named pipes protocol?

    On the other hand, what can happen if the named pipes is disabled?

    Thanks a lot!

  • March 12, 2009 at 7:07 am

    #958271

    Far as I know it is automatic ... SQL Server can be configured to give priority to Named Pipe or TCP/IP connections. If you disable Named Pipes, and the client computer cannot use TCP/IP the connection will be failed. Thanks.

    Ref: http://msdn.microsoft.com/en-us/library/aa178138(SQL.80).aspx

    Ref: http://msdn.microsoft.com/en-us/library/aa213760(SQL.80).aspx

    [font="Arial"]---

    Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
    Microsoft FTE - SQL Server PFE

    * Some time its the search that counts, not the finding...
    * I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]

    How to ask for help .. Read Best Practices here[/url].

  • March 12, 2009 at 10:06 am

    #958474

    I wouldn't turn it off unless you are pretty sure nothing uses named pipes...

    Our entire vendor software uses NAMED PIPES and crashes with TCP/IP when we went live on it...and it was the TCP/IP wasn't configured in their connections so we had to wait for the fix which is ready to be tested thankfully.

    So please be careful not to disable unless you know the vendor software works on both.

    We also had another issue that if we used fully qualified name of server SQL1.DOMAIN\INSTANCE this gave us TCP/IP entries and if we used SQL1 this was Named Pipes.

    Also you can do CLCONFIG and set up the alias here to force the SQL just to use named pipes vs TCP/IP if you want to without going into SQL and unchecking the connections.

    Hope that helps..........i had so much fun with these connections lately.

  • March 13, 2009 at 1:49 am

    #958931

    Thanks everyone.

    I'll try configure the connection whit the full domain name of the server.

  • March 13, 2009 at 7:39 am

    #959099

    What does your VB app use to connect? ODBC?

    ---------------------------------------------
    [font="Verdana"]Nothing is impossible.
    It is just a matter of time and money.[/font]

  • March 13, 2009 at 7:59 am

    #959114

    OK. I think my brain is still a bit asleep, so I missed the DSN answer.

    And because I have not been dealing with ODBC for quite some time if my answer is not quite right, I am sorry. 🙂

    You use DSN so it is ODBC right?

    When you configure the ODBC you may chose the network protocol to be used. I bet the few clients had the ODBC sources created or modified to use the Named Pipes as a default network protocol.

    It is always the client who choses the protocol to conenct to the server. The default network protocol could be changed outside of ODBC as well because it is a layer or two below ODBC.

    ---------------------------------------------
    [font="Verdana"]Nothing is impossible.
    It is just a matter of time and money.[/font]

  • March 13, 2009 at 8:13 am

    #959125

    Yes forgot that one too the ODBC itself...

  • September 24, 2009 at 9:52 am

    #1058130

    I need some help with this topic. The SQL/Server 2005 computer communicates with the DB through ODBC using Named Pipes without a problem. A remote computer connects to the DB through ODBC via TCP/IP, but fails with Named Pipes (1326, Does not exist or access denied ...).

    Firewalls are turned off on both PC's. Nothing seems out of line in Surface Area Configuration. I need a Named Pipes ODBC source on the remote computer.

    thx in advance ...

  • September 25, 2009 at 6:35 am

    #1058416

    Make sure the fully qualified name is being used i.e SQLSERVERNAME.DOMAIN Check with DNS people what they set it as and try IP instead. Make sure SQL is set up to acept both name pipes and tcp/ip on the surface area configuration if not that one it the other tool for sql i forget the name as im not looking at SQL right now

Viewing 13 posts - 1 through 12 (of 12 total)

You must be logged in to reply to this topic. Login to reply