howartp Posted October 18, 2011 Posted October 18, 2011 Hi, For quite a while now, both myself and my line manager have had several problems trying to view/update calls on SupportNet. We can always log in ok and get to the Calls list, but trying to add a note to any call will kill the session and thus display a 'you cannot view this page' type notice because I'm (supposedly) no longer logged in. All I can get out of Capita is to get my IT guys to check the ISA settings. Well I am the IT guy, and we don't have an ISA server. Has anyone else ever experienced problems where a cookie/session will just time-out when navigating the site? If I go home it works perfectly fine, so it obviously is something in school but I haven't got a clue where to start looking. I'm sure it started before we got our Smoothwall box installed, but might be wrong there. Any suggestions? Peter
vikpaw Posted October 18, 2011 Posted October 18, 2011 I know that it's not very good at handling when you have more than one tab open and also it gets confused when you don't end the session after logging out. I find it works better when i do that. I still use multiple tabs on the forum and after an update to a thread it goes funny and brings up the wrong page. Other than that, no problems. Do you have a fixed ip that is shown outbound, or is it possible it's dynamic or flipping between two which might cause them to think the connection was broken..
howartp Posted October 18, 2011 Author Posted October 18, 2011 Hi vikpaw, I regularly use multiple tabs, but only ever one open on SupportNet at once, and I don't use their forums. I'll check with logging out all sessions, clearing cookies etc and using a single tab and see what happens then report back. AFAIK I know we only send out one IP; we do have three or four inbound IPs but I think only one is used for outbound traffic. Peter
howartp Posted October 18, 2011 Author Posted October 18, 2011 Hi again, Having paid more attention to where the button is trying to send me when pressing it (by looking at the source code) I've found the problem. It's linking to "IssueDetails.aspx?id=Guardian: shellcode removedGuardian: shellcode removedGuardian: shellcode removed" - which tells me it's obviously Guardian (part of our Smoothwall) which is causing the problems. I've therefore found where the setting is and overrode it so it's now working as it should do. Thanks for your reply anyway. Peter
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now