Re: sql server2000; TCP/IP vs Named Pipes



are you sure that you're not just having periodic domain name failures?

what's your DNS strategy?



"Greg Linwood" <g_linwood@xxxxxxxxxxx> wrote in message
news:OHrwxyzcHHA.4308@xxxxxxxxxxxxxxxxxxxxxxx
Hi Andre

wireshark.org have an excellent protocol analyser. It will reveal any
protocol errors at either TCP layer or TDS which might be the case if you
have incompatible client side driver libraries.

As far as proving the application is poorly coded - this seems a strange
approach to me as the application appears to work fine on one protocol but
not another. Why not just sort out what's going on at the network level
first before deciding there's something wrong with the application design?

Regards,
Greg Linwood
SQL Server MVP
http://blogs.sqlserver.org.au/blogs/greg_linwood

"Andre Gibson" <AndreGibson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0410AF1F-EFF4-463D-ABDB-64776008E651@xxxxxxxxxxxxxxxx
Hello all,
My company is running an application that uses sql server 2000 sp3. Sql
server 2000 is configured to accept only TCP/IP (port 1433) or Named
Pipes.
We prefer to use TCP/IP but we are having issues with users losing there
connection to the DB if they use TCP/IP. The problem is sporadic, and I
am
tring to find a definitive way to rule out the database as the cause of
this
problem. Moreover those machines that have problems with TCP/IP seem to
work
with Named Pipes (at least for a time)

- How can I prove this isn't the DB?
- Could the application, if poorly coded contribute to this problem?
- How can I prove that the application is poorly coded?
- How can I isolate the problem to th network? Can anyone recommend free
easy to use network tools that can detect the network issue

regards,

Andre




.



Relevant Pages

  • Re: windows xp and 2000 home network
    ... > reinstall of the TCP/IP protocol. ... > 2) Right-click the network connection, ... > 4) Click Protocol, and then click Add. ... > This answer applies to computers that connect to a cable modem or DSL ...
    (microsoft.public.windowsxp.network_web)
  • Re: Umstieg von Access auf SQL-Server
    ... > Bei Port 1433 sabber ich dann immer gleich Named Pipes. ... Nein, TCP/IP. ... How To Change SQL Server Default Network Library Without ... How To Set the SQL Server Network Library in an ADO Connection String ...
    (microsoft.public.de.vb.datenbank)
  • Re: Download corruption - anyone advise please?
    ... *has* to be something protocol related at this point. ... your primary network connection from the network settings control panel ... you have anything other than TCP/IP in that list (excluding MS ... Interfaces\] and then an entire reg search for MTU...nothing. ...
    (uk.comp.homebuilt)
  • Re: XP sharing issue
    ... - Both PCs NodeType displays Unknown when running ipconfig /all. ... >>I have a local network sharing a gateway for internet access. ... Use only one protocol for File and Printer Sharing. ... Double click Internet Protocol (TCP/IP). ...
    (microsoft.public.windowsxp.network_web)
  • REVIEW: "The TCP/IP Guide", Charles M. Kozierok
    ... guide to the TCP/IP (Transmission Control Protocol/Internet Protocol) ... II-1 examines the network interface layer, ...
    (rec.arts.books.reviews)

Loading