View Full Version : Superhub Cant access / download from certain sites
Hi
Since the update of the firmware on the superhub I cant access the following site
gc.progvo.com
It was working fine yesterday bit but I can't reach it at all on any of my desktop pcs.
I can't ping it on either of my desktops but can access it via my laptop using vpn so im guessing its a dns problem.
i tried changing the dns server on my desktop and it didn't work so is the router overwiritng my desktop change ?
?
Any help much appreciated
Thanks,
DinAlt
Chrysalis
24-04-2011, 20:47
C:\Windows\system32>nslookup gc.progvo.com. 194.168.4.100
Server: cache1.service.virginmedia.net
Address: 194.168.4.100
Non-authoritative answer:
Name: gc.progvo.com
Address: 195.198.208.244
their dns is fine.
No.
Its a routing issue between virgin (and others maybe) and telia. I cannot access anything that goes through telia either.
Thanks Philipp,
So I'm not going mad - anyway of getting round it temporarily ?
nslookup gc.progvo.com
Server: cache1.service.virginmedia.net
Address: 194.168.4.100
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to cache1.service.virginmedia.net timed-out
DinAlt
no nothing you can do apart from using a vpn that has not got this current issue. I'm not sure why you cannot lookup the dns though. that might be another issue!
Chrysalis
24-04-2011, 21:15
Tracing route to benzler.smedjan.cc [195.198.208.244]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms home.gateway2 [192.168.1.1]
2 9 ms 9 ms 7 ms cpc14-leic14-2-0-gw.8-1.cable.virginmedia.com [8
2.30.112.1]
3 9 ms 9 ms 8 ms leic-core-1a-ae3-2231.network.virginmedia.net [8
2.3.33.45]
4 14 ms 12 ms 13 ms leed-bb-1a-as8-0.network.virginmedia.net [213.10
5.172.17]
5 16 ms 15 ms 15 ms 213.152.245.53
6 17 ms 17 ms 14 ms xe-0-0-0.mpr1.lhr1.uk.above.net [64.125.27.161]
7 14 ms 10 ms 15 ms ldn-b5-link.telia.net [213.248.104.37]
8 14 ms 15 ms 18 ms ldn-bb1-link.telia.net [80.91.247.91]
9 26 ms 27 ms 28 ms hbg-bb1-link.telia.net [80.91.249.11]
10 49 ms 48 ms 45 ms kbn-bb1-link.telia.net [80.91.252.109]
11 48 ms 49 ms 46 ms kbn-b4-link.telia.net [80.91.253.192]
12 51 ms 52 ms 50 ms mb-peer3-link.telia.net [80.91.253.83]
13 55 ms 52 ms 50 ms ld-h-c5-link.se.telia.net [81.228.75.72]
14 55 ms 56 ms 55 ms g-ra-c5-link.se.telia.net [81.228.93.102]
15 60 ms 58 ms 60 ms g-kt-d2-link.se.telia.net [81.228.77.236]
16 57 ms 54 ms 60 ms 90-229-62-71.link.se.telia.net [90.229.62.71]
17 *
then dead. so yeah a telia or endpoint issue as we dont know if the next hop is the last hop or not.
Yes its routing issue. dunno if its the return or forward path. I wonder if these means world of warcraft is down for the users who use that. telia is used with that isnt it?
DInalt. Theres a massive post on the community forums about WOW which is related to this as it routed through telia. Fault reference is F001586172.
Thanks again,
Well if it's affecting Wow should be enough impetus for them to fix it :)
DinAlt
craigj2k12
25-04-2011, 23:26
WoW has a known fault at the moment as i found out on the phone today when reporting a separate problem. I dont even play it but he said "yes there is a known fault with it" i was reporting slow speeds and crap ping and that was his first attempt to hand me off lol
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.