WAAS Blocking some Microsoft Services

Question

Hi,
I am currently running a WAAS POC at a bank and I have run into the following problem;
- The WAAS core device is placed in-line at the HQ and it seems to block the following Microsoft Services on all the branches that connect through this kit, Microsft Outlook MAPI, Microsoft CIFS and Microsoft Terminal Serices.
Basically remote branch users are complaning that they cannot access the Exchange server through outlook MAPI, they cannot connect to a file server to access scanned documents and they cannot connect to windows terminal services.
Apparently the Core WAE is connecting to a packeteer device that can only do half-duplex hence the WAE is giving a major error that it is running on half-duplex. There is an Tipping point IPS device after the packeeter device but the branches were working well without the WAAS kit hence ruling out that the IPS or packeteer is the problem.
What could be making the WAE to block the microsoft services and not other services like HTTP?
Urgent as Riverbed & Juniper are running a parallel POC and this might affect Cisco's WAAS image!!!
regards,
Ed

Answer 1

Hi Zach, we opened a TAC case (SR 609076799) last week, and the tac engineer said he noticed something immediately in the system report.
"I went through the system report on the Core side and saw the following messages:
A new view from the router 172.17.7.4 with the given change number: 17
New web cache in hash compute assignment 10.56.220.1
These two messages combined with Catalyst software version leads me to believe
that the Catalyst IOS could be part of the cause.
In addition to this, I would like to bring your version to the one that BU supports so that
if you continue to experience the issue after the software upgrade, it will be easier.
Please upgrade the IOS version to 12.2(18) SXF14 after making sure that the
version would be suitable for your environment."
And he explained there are known bugs with WCCP in the version of IOS I am running on the 6500's.
I'll double check to make sure we're doing l2 on the 6500's - but the hits I am referring to are on the redirect-list ACL's.
We control which traffic by subnet in the redirect ACL and I look at the counters on those ACL's to see where traffic was incrementing.
61 in was on Router A, 62 in was increminging on Router B.