Cant access outlook.com using web access via Vodafone

Forums › One New Zealand (including Vodafone, WxC, Farmside) › Cant access outlook.com using web access via Vodafone

1 | 2 | 3 | 4 | 5

1759 posts

Uber Geek
Inactive user

#1621216 2-Sep-2016 09:38

freitasm: You should not use external DNS. It impacts negatively in performance for things like YouTube and other services that use some CDN.

The Vodafone call Centre is really getting worse.

It was their cable techies that did it.

They changed my IP to see if that would fix it...when that didn't they told me to use the google DNS and that fixed it. The whole process was approx an hour on the phone talking to them. It not only corrected some bad URL's but it also corrected my ingame latency to wow servers substantially.

I do agree with you about us not having to use external DNS and in my opinion this is yet another example about the sorry state of VF cable.

Regs

4066 posts

Uber Geek

Trusted

Snowflake

#1621219 2-Sep-2016 09:43

anyone else having these problems accessing outlook.com (on Vodafone, or any other ISP)?

Sales Engineer
Snowflake
www.snowflake.com

about.me/nzregs
Twitter: @nzregs

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1621230 2-Sep-2016 09:57

Ah... Cable "techies" are third party. Talked to JohnR and he's pushing this up with the network folks.

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1621251 2-Sep-2016 10:07

Pumpedd:

My situation was fixed by Vodafone techs telling me to use Google DNS permanently.

Argh. And I lambasted Vodafone call centre in fact it wasn't them. "Cable techie" is not a Vodafone person, just a contractor. They should learn to keep their ideas to themselves. This doesn't help.

eljefe

99 posts

Master Geek

#1621283 2-Sep-2016 10:53

I will get back on the blower to VF again shortly. I am using VDSL that came via Worldxchange originally.

Thanks for all the feedback.

Cheers

Jeff

tanivula

991 posts

Ultimate Geek

Lifetime subscriber

#1621294 2-Sep-2016 11:14

Regs:

anyone else having these problems accessing outlook.com (on Vodafone, or any other ISP)?

Having a kinda similar issue with Voda. Details here.

thecatsgoolies

414 posts

Ultimate Geek

Trusted

#1621299 2-Sep-2016 11:19

Please before calling make sure DNS settings are correct

Samsung

Shop now on Samsung phones, tablets, TVs and more (affiliate link).

eljefe

99 posts

Master Geek

#1621304 2-Sep-2016 11:28

thecatsgoolies: Please before calling make sure DNS settings are correct

As I said in post 3, any advice on how I should check this would be great.

I have not changed anything on my PC or router. I have had the router for almost 2 years now. is the standard one that Worldxchange rolled out.

freitasm

BDFL - Memuneh
79263 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#1621323 2-Sep-2016 11:46

So you have not changed the DNS to Google as suggested by the technician? Good.

Also it would be good if we knew it was the old WorldxChange network from the start. It might help Vodafone to actually find where the problem lies.

Pumpedd

1759 posts

Uber Geek
Inactive user

#1621325 2-Sep-2016 11:54

Mike Hales has sent me a message saying that..

Correct should be

Primary DNS: 203.109.129.67 or 203.109.191.1
Secondary DNS: 203.109.129.68 or 203.118.191.1

These appear to be a bit different to whats been mentioned on these forums previously.

eljefe

99 posts

Master Geek

#1621326 2-Sep-2016 11:56

freitasm:

So you have not changed the DNS to Google as suggested by the technician? Good.

Also it would be good if we knew it was the old WorldxChange network from the start. It might help Vodafone to actually find where the problem lies.

I have mentioned 3 times that it was originally Worldxchange, including the 1st post.
I just got off the phone now to a VF tech and they are going look at changing the DNS remotely tonight to googles to see if that helps : )

The tech said that the problem earlier this week was due to "google-cache" ?