+100

Set up wireshark/tshark on the server, if you can, and set up a fairly
large ring buffer.

Wireshark gives you the truth - you just have to know how to read it.

Kurt

On Fri, Jan 16, 2015 at 11:35 AM, Kennedy, Jim
<[email protected]> wrote:
> I would drop wireshark in on a couple of workstations and log the
> traffic…get them to write down exact time when it occurs on one of those
> stations.  I would also toss some performance monitors on the server.
>
>
>
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Jimmy Tran
> Sent: Friday, January 16, 2015 2:24 PM
>
>
> To: [email protected]
> Subject: RE: [NTSysADM] troubleshoot possible network connectivty issues
>
>
>
>
>
> 1.       Program is Dentrix G5.
>
> 2.       Client / Server with a SQL backed by FairCom (c-treeACE SQL
> Database).
>
> 3.       Server is running ESXi 5.5 with Sever 2008 R2.
>
> 4.       ESXi datastore is on an external QNAP NAS on encrypted disks.
>
> 5.       Their support is useless with this issue.
>
>
>
> Three specific issues are:
>
> 1.       When the patient is finished, they will sign a form with a signing
> pad in the exam room.   The form is saved and you can see both signatures.
> Doctor goes back to her office and views that form, only one shows up.  If
> you go back to the exam computer it will show two until you close and
> re-open.  The 2nd signature now disappears.  This is completely random.
>
> 2.       X-rays are taken from a patient and each image is labled.  They
> save the patient chart.  Doctor goes back to her office to view the x-rays,
> the images are there but not labeled.  She closes and reopens the chart in
> her office and the labels now show.
>
> 3.       Sometimes the office experiences a lot of sluggishness while using
> the dental software on all 15 machines.  When I do a file transfer test of a
> 250MB file, it could take anywhere from 9-30 seconds.  It varies on
> different machines.  When the “sluggishness” is not there, the speeds range
> from 6-20 seconds.  When on the server doing the same test, it takes 3
> seconds.
>
>
>
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Kennedy, Jim
> Sent: Friday, January 16, 2015 11:02 AM
> To: [email protected]
> Subject: RE: [NTSysADM] troubleshoot possible network connectivty issues
>
>
>
> Tell us about the design of the dental software.  Is it a web
> app…client/server…SQL backend? What is saved where and how.
>
>
>
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Jimmy Tran
> Sent: Friday, January 16, 2015 2:01 PM
> To: [email protected]
> Subject: RE: [NTSysADM] troubleshoot possible network connectivty issues
>
>
>
> Slowness while launching their Dental software.  Doesn’t happen all the
> time.  Certain things within the application is not appearing after they are
> clearly being saved.  I’m thinking there is a connectivity issue on the
> network causing the network causing all this.
>
>
>
>
>
> From: [email protected] [mailto:[email protected]]
> On Behalf Of Micheal Espinola Jr
> Sent: Friday, January 16, 2015 10:44 AM
> To: ntsysadm
> Subject: Re: [NTSysADM] troubleshoot possible network connectivty issues
>
>
>
> These are vague problem descriptions for a tool recommendation.  Slowness of
> what, in which application, while doing what?  Which work not being saved,
> to what, and in what manner?
>
>
> --
> Espi
>
>
>
>
>
> On Fri, Jan 16, 2015 at 8:07 AM, Jimmy Tran <[email protected]> wrote:
>
> Hi All,
>
>
>
> Do you have any favorite network troubleshooting tools you recommend?  My
> client keeps complaining about slowness and work not being saved.  I have a
> feeling it could be cabling or a faulty switch.  The switch is not managed
> so I do not have any monitoring tools there.  A ping test comes back ok
> after a few hours so I’m looking for some more advance tools that can be run
> 24/7 on all machines in the office.
>
>
>
> I’m not looking to monitor anything on the machines, other than packet loss
> or connectivity issues.  What are you favorite tools or suggestions?
>
>
>
> TIA
>
>
>
> -JT
>
>
>
>


Reply via email to