Forum Discussion

Craig_Gibb_1781's avatar
Craig_Gibb_1781
Icon for Nimbostratus rankNimbostratus
Jun 15, 2014

Problem editing ofice documents in Sharepoint 2013 via ssl vpn conections using APM

Hi we are using a edge gateway cluster (using 11.4.1) for ssl vpn´s Full network access connections. We have also a internal f5 clsuter using LTM 11.5.1 from shich we publish the internal sharepoint 2013 sites. The problem is users connecting to the ssl vpn (through the edge gateways, cannot edit office documents, they open only in read only format, wheras editing couments internally works without any problem. I have searched i devcentral and have found a few threads with similar problems, pointing to thta the problem is related to webdav that is used when try to edit the office documents, the solutions have in these cases been using a peristence profile using cookies and or using a irule to catch undocumented http methods.

 

Now none of these have helped im my case, i have tried both. Teh sharepoint enviroment is a simple publication using no ssl offload, using only http. I would appreciate any ideas as to the cause and suggestions on possibel solutions.

 

/Regards Craig

 

4 Replies

  • mikeshimkus_111's avatar
    mikeshimkus_111
    Historic F5 Account

    Hi Craigg, the persistent APM cookie option must be enabled in the Access Profile settings. Also, there are bugs with both Win7 and Win8 that prevent this cookie from being honored by the WebDav client.

     

    Here is the MS hotfix for Win7: http://support.microsoft.com/kb/2936341

     

    I have installed this hotfix on multiple failing clients and it's worked every time.

     

    I am trying to track down the hotfix number for Win8. AFAIK, it was going to be included in the June 10th rollup.

     

    thanks

     

    Mike

     

    • mikeshimkus_111's avatar
      mikeshimkus_111
      Historic F5 Account
      Nevermind, I see that they just updated that same KB for Windows 8 and 8.1.
    • CGI's avatar
      CGI
      Icon for Altostratus rankAltostratus
      Hi guys thanks for the tips and information, we have found the cause in our situation, it would seem to be a IPS rule in our FW, the strange thing is that the rule itself is for ISA2006 and OTP bypass vunerability, but as soon as we disabled this rule then the editing function worked as normal. Thnaks anyway. /Craig