Problems accessing webmail http error

Forums › Spark New Zealand (including Skinny and BigPipe) › Problems accessing webmail http error

Taxi1966

8 posts

Wannabe Geek

#42637 8-Oct-2009 15:31

Hi - hoping to get some help please. I am using Windows XP on a home computer using Telecom Broadband. Up until a few days ago I used to be able to access my work emails using HTTPS://webmail.(my company).co.nz. It would take me into a log on screen where I would enter my work log in and password and then allow me to access my work email. Now when I try, I get to the log on screen but when I enter my logon and password it comes up with this error: HTTP/1.1 501 Not Implemented.
I have tried to unclik the http 1.1 option in tools/internet options/advanced as suggested on another site but no luck. Any suggestions?
Thanks

ResponseMediaNZ

518 posts

Ultimate Geek
+1 received by user: 196

ID Verified

Trusted

#262423 8-Oct-2009 15:40

Has your work recently upgraded to a newer verson of Exchange?

Try adding a /owa at the end

Taxi1966

8 posts

Wannabe Geek

#262427 8-Oct-2009 15:45

Not sure about the upgrade - its possible.

To the end of what? :-)

ResponseMediaNZ

518 posts

Ultimate Geek
+1 received by user: 196

ID Verified

Trusted

#262428 8-Oct-2009 15:46

make it https://webmail.domainname.co.nz/owa

That is if you are getting a outlook webaccess login screen or office outlook web access

Taxi1966

8 posts

Wannabe Geek

#262430 8-Oct-2009 15:52

You are a genuis! That got me to the same log in screen but this time entering my password etc actually got me into my work email. Fantastic. thank you very much.
Just for my own interest does this mean there had been an upgrade of some kind?

ResponseMediaNZ

518 posts

Ultimate Geek
+1 received by user: 196

ID Verified

Trusted

#262431 8-Oct-2009 15:55

No problems :) glad to help, and Normally this would indicate some chanage to the companies exchange server, you possibly have even seen then change in client.

It could also be they are testing somthing new and just needed unset the redirect to /owa