Hi all bit of a strange issue this really.
One of our employees has come to us and said that he accesses a local councils webmail using their OWA. Everything had been working fine up until a couple of weeks ago where by when he would log in it would instantly log him back out.
Now I can't seem to suss out what the problem is as we haven't changed anything to do with our internet connection/router settings etc, but he says it works fine from anywhere else.
I've tried getting him to use different machines, different browsers, different OS's, setting to public or private machine and it still does the same, it just logs him out as soon as he puts his username and pass in.
He said hes spoken to their IT dept and said it must be an issue at our end, which it would seem to be the case as he can access it fine from other places just when hes in our office - but I can't put my finger on what is causing it. A quick Google suggests it could be server side configuration that needs changing but that doesnt explain why he can access it fine elsewhere so i'm almost certain it must be something at our end.
Anyone any ideas what could be causing this? They are using Exchange 2003 OWA from the looks of it!
One of our employees has come to us and said that he accesses a local councils webmail using their OWA. Everything had been working fine up until a couple of weeks ago where by when he would log in it would instantly log him back out.
Now I can't seem to suss out what the problem is as we haven't changed anything to do with our internet connection/router settings etc, but he says it works fine from anywhere else.
I've tried getting him to use different machines, different browsers, different OS's, setting to public or private machine and it still does the same, it just logs him out as soon as he puts his username and pass in.
He said hes spoken to their IT dept and said it must be an issue at our end, which it would seem to be the case as he can access it fine from other places just when hes in our office - but I can't put my finger on what is causing it. A quick Google suggests it could be server side configuration that needs changing but that doesnt explain why he can access it fine elsewhere so i'm almost certain it must be something at our end.
Anyone any ideas what could be causing this? They are using Exchange 2003 OWA from the looks of it!