We are having a very strange issue. When we access our application via local lan the panels work fine. The web service calls work fine. When we access the app through a CISCO VPN Client connection. The web service calls work, the Profile and Authentication service calls work, but the WARP Panel Update calls don't work. Not only do the requests time out, but it also causes the VPN to disconnect. Can you help us figure out why the WARP panel could cause the VPN connection to close?
This is no longer an issue, upgrading to a newer version of the VPN client fixed this.
Hi Jeff,
I have a customer with a similar problem. It is not easy to make them believe it can be a VPN issue rather than a programming issue.
What version of Cisco VPN experienced the problem and what version fixed it?
We've upgraded the client from 4.6.02.0011 to 4.8.02.0010 and the problem appears to have gone away.
Thanks Jeffrey. I will take this to my client.
Our team spoke too soon. We are still experiencing problems even after upgrading to a later version of the VPN client. We have even tried increasing the MTU size from 1300 to 1320. We thought it got better, but it did not and we are still experiencing the application hanging on certain actions (without a discernable pattern), disconnect errors, and related issues.
Other applications that are not using ASP.NET with Infragistics are using the same VPN without issue.
I wouldn't mess with your MTU size for a webpage problem thats just asking for trouble...
3 Questions for you:A: What kind of encryption are you using on your VPN?B: Have you tried making a simple web page that does a simple xmlget via javascript and see if it gets broken.C: Are you using a content filtering system.