no acceleration after stopping and starting wccp

Answered Question
Jun 23rd, 2010
User Badges:

I acceleration was working fine between my data center and a branch.  (I was copying files from my data center PC to a PC at the branch).   I wanted to demonstrator how much slower CIFS copies are without acceleration so I stopped wccp on the branch router (no ip wccp 61 redirect-list wae-nme, no ip wccp 62 redirect-list wae-nme).  As expected, the CIFS copies then were much slower.


Then I restarted WCCP (ip wccp 61 redirect-list wae-nme, ip wccp 62 redirect-list wae-nme), BUT now the connection from my workstation at the data center to the branch shows up as pass through.


A show stat conn on the branch NME shows other CIFS connections from other branch hosts, but my PC's connection is stuck in pass through.  How do I get my PC's connection to accelerate again?


All WAAS devices are on 4.1.7.

Correct Answer by Zach Seils about 6 years 11 months ago

Tod,


CIFS sessions do a decent job of reconnecting when there is a failure at the transport (TCP) layer.  It's likely that WAAS sees that the connection was already established (your ConnType would be PT In Progress).  You have to close the CIFS session (net use * /delete) and restart the transfer.


Regards,

Zach

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Zach Seils Thu, 06/24/2010 - 06:15
User Badges:
  • Cisco Employee,

Tod,


CIFS sessions do a decent job of reconnecting when there is a failure at the transport (TCP) layer.  It's likely that WAAS sees that the connection was already established (your ConnType would be PT In Progress).  You have to close the CIFS session (net use * /delete) and restart the transfer.


Regards,

Zach

Tod Larson Thu, 06/24/2010 - 06:50
User Badges:

The net use command worked perfectly.  Thank you.

Actions

This Discussion

Related Content