Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Could any expert in WAAS Mobile see this question?

Hi everybody!

I succesfully installed WAAS Mobile in a customer. Everything worked fine with WAAS, except for a particular application. WAAS Mobile is not working with a particular client/server Application. When WAAS Client is running, the Application Client is not able to connect to the Application Server.

Analyzing the packets capture with Wireshark, I observed that the first 3 packets are not being redirected to the WAAS Mobile Server. It is going straight to the Application Server.

At first I thought that I needed to add another process to the Proxied Process list in WAAS. But using the TCPView software I can see that the process that is sending the first packets is the one that I already added to the Proxied Process list.

The question is: Is it normal for these first packets not passing through WAAS Mobile Server? Or all the packets of the process should be redirected to the WAAS Mobile Server? Could this problem be a bug? What is the best way to troubleshoot this?



New Member

Re: Could any expert in WAAS Mobile see this question?

First of all, individual packets are not passed thru to the WAAS Mobile Server. All TCP connections for accelerated applications are terminated on the client. The packet content is encapsulated and passed to the WAAS Mobile Server using a UDP connection on port 1182. The fact that you saw packets going to the application server means that the applicaiton in question is not being optimized for whatever reason. To determine the reason, please generate a client and server System Report directly after exercising the problem application with WAAS Mobile. Either open a TAC case for the issue or send the system reports to the Cisco SE assigned to your account. The system reports can then be analyzed to determine why the application is being bypassed.