Hi Prasad,
According to the screen shots provided the fin.exe process is bypassed due to Low Latency. From the admin guide this means:
- Bypassed : Low Latency. The latency between the client and the application server is less than the latency threshold, which is 10 ms by default. This threshold may be modified on the Connection Settings tab on the Configure > Clients > Networking page.
Also, I see SERVER.exe process is going to the same server or subnet as fin.exe but is bypassed due to Pre-Existing connection.
- Bypassed: Pre-existing Connection. When WAAS Mobile is started after other applications, the existing TCP connections associated with those applications will not be reset unless the “Auto Reset Connection” property has been selected for the process in the Accelerated Processes table, and hence, these pre-existing connections will be bypassed.
Lastly, I see bermote.exe is listed as Bypass Reason Unknown in one of the screen shots.
- Bypassed : Reason Unknown. This message will occur when an attempt to reset a TCP connection associated with an application that has been configured to have these connections be automatically reset (via the Accelerated Processes table on the Configure > Clients > Acceleration page) fails.
Is this client actually accessing a server that is remote for these first two processes?
For the last process, did we try to first exit the application in question and all the associated processes (beremote, and any other processes that may get started with this application), then start the WAAS Mobile client, then finally start the associated process/application?
Cheers,
Mike Korenbaum
P.S. If this answers your question please mark it as such.
