"Andre Gibson" <AndreGib***@discussions.microsoft.com> wrote in message
news:0410AF1F-EFF4-463D-ABDB-64776008E651@microsoft.com...
> 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

"Greg Linwood" <g_linw***@hotmail.com> wrote in message
news:OHrwxyzcHHA.4308@TK2MSFTNGP02.phx.gbl...
> 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" <AndreGib***@discussions.microsoft.com> wrote in message
> news:0410AF1F-EFF4-463D-ABDB-64776008E651@microsoft.com...
> > 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
>
>