Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Fragmented Packets on Network
Message
From
05/09/2011 06:35:09
 
 
To
05/09/2011 03:50:22
General information
Forum:
Visual FoxPro
Category:
Installation, Setup and Configuration
Environment versions
Visual FoxPro:
VFP 9 SP2
OS:
Windows 7
Network:
Windows 2003 Server
Database:
Visual FoxPro
Application:
Desktop
Miscellaneous
Thread ID:
01522697
Message ID:
01522702
Views:
62
>I have a client with a large network 25+ workstations, running a vertical market application.
>
>They are having speed issues with their network - not just my application, but general speed.

>Their network specialist have advised;
>
>
>"We have installed WireShark on a workstation and on the server to try and find the cause of the problem.  It was noted that there are a lot of ‘Fragmented Packets’ going between the workstation and the server.
>
>We isolated the source of the ‘Fragmented Packets’ by excluding all networked devices and creating a restricted network consisting of only the broadband router, the server and the workstation connected via a Gigabyte switch.  Initially there was no ‘Fragmented Packets’, however, as soon as <VFP application> was run the ‘Fragmented Packets’ started again.
>
>It seems clear to us that there is a problem with the way  <VFP application>  is communicating with the network and therefore we need to work together to try and resolve the problem."
>
>
>I am not a network specialist, does anyone know how VFP woudl cause fragmented packages and why this would be an issue?
>
>Is there anything I could do to resolve/change this?
>
>Gary.

Is the network slow when your application is *not* running?
Is the application running on any other similar sized networks without problems?

Fragmentation occurs when the IP packet is larger than the MTU. There's obviously some overhead involved in breaking down and re-assembling the packet but I don't think this should account for a *huge* slowdown. If VFP *is* responsible then sheer volume being sent over the wire is more likely to be the problem....
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform