Hi. I have an application based on MS Access 2010 database that is sometimes (very) slow over the network. On my server i have a back-end DB and on a client pc i have local front-end DB. So, previously i run test speed measurements over my 1Gb lan (using Iperf tool) and this report a good speed (112 MBytes sec, optimal throughput). Running a session with wireshark shows me there is no problem on the network, but if i follow the stream between server and client i notice a (sometimes great) delay from client request and not from server response (or maybe i committed an error to read the trace? please see the picture, i'm not an expert). Thanks in advance. asked 22 Aug '16, 16:21  carlogiga |
One Answer:
Debugging by screenshots is close to impossible, but your screenshot shows that it takes the client 29 seconds from acknowledging the previous packet to think through what else it wants from the server. As such it looks as an application issue so Wireshark is not the tool to tell you more than this. answered 23 Aug '16, 06:36  sindy edited 23 Aug '16, 06:36 |
Thanks for you reply. If i can confirm a theory that proves the issues is caused by a slow response by MS Access (and not by buggy or misconfigured network) it's ok for me. Because in this case i can test other configurations like putting both front-end and back-end DB on a SSD unit on the server, for example.