WCCP trouble with Fortigate 1000C to Riverbed Steelhead

[Mizzouri]

We' re having issues getting WCCP to function with the Riverbed (V4.0 MR3 Patch 11). What we' re seeing is that incoming traffic does hit the Riverbed and heads out as expected but when it returns it is not directed back to the Riverbed by the Fortigate. Has anyone had any luck with WCCP? FW2 (1) # get service-id : 61 router-id : 10.10.10.157 group-address : 0.0.0.0 server-list : 10.10.10.158 255.255.255.255 authentication : disable forward-method : any return-method : any assignment-method : any Riverbed shows connected as L2 and HASH. The Riverbed is directly connected to the Fortigate and wccp is enabled on that port. Policy is built for the traffic with wccp enabled. All of this was configured as suggested on pages 34-35: http://docs.fortinet.com/fgt/archives/4.0/techdocs/FortiGate_Administration_Guide_01-400-89802-20090424.pdf port 15 = Riverbed I would think that the incoming traffic from 172.16.82.6 would hit port15 before it went back to the source (172.16.65.238). 11.668138 Vlan_1001 in 172.16.65.238.61329 -> 172.16.82.6.443: syn 4133542165 11.668155 port15 out 172.16.65.238.61329 -> 172.16.82.6.443: syn 4133542165 11.668385 port15 in 172.16.65.238.61329 -> 172.16.82.6.443: syn 4133542165 11.668385 Vlan_1001 in 172.16.65.238.61329 -> 172.16.82.6.443: syn 4133542165 11.668396 wan1 out 172.16.65.238.61329 -> 172.16.82.6.443: syn 4133542165 11.693193 wan1 in 172.16.82.6.443 -> 172.16.65.238.61329: syn 2513619920 ack 4133542166 11.693202 Vlan_1001 out 172.16.82.6.443 -> 172.16.65.238.61329: syn 2513619920 ack 4133542166 11.693203 Internal_Po300 out 172.16.82.6.443 -> 172.16.65.238.61329: syn 2513619920 ack 4133542166 11.693204 port23 out 172.16.82.6.443 -> 172.16.65.238.61329: syn 2513619920 ack 4133542166 11.693685 Vlan_1001 in 172.16.65.238.61329 -> 172.16.82.6.443: ack 2513619921 11.693695 wan1 out 172.16.65.238.61329 -> 172.16.82.6.443: ack 2513619921