cant log on to megashares.com

[#1]

I use megashares on a regular basis but cant log on via plusnet I can get megashares.com but if I click to log on it wont connect and returns unavailable.  This happens when the adress starts with do1 for example http://d01.megashares.com/myms_login.php
I can log in at work no problem so it has to be an issue with plusnet . It only started around a week ago.
Please help

[#2]

I can't reach the site either but tracert gets there:

C:\Users\John>tracert d01.megashares.com
Tracing route to d01.megashares.com [71.5.11.11]
over a maximum of 30 hops:
  1    <1 ms    <1 ms     1 ms  tg582 [192.168.1.254]
  2    38 ms    37 ms    36 ms  lo0-central10.ptn-ag04.plus.net [195.166.128.193]
  3    38 ms    37 ms    37 ms  link-b-central10.ptn-gw02.plus.net [212.159.2.142]
  4    37 ms    37 ms    37 ms  xe-8-2-0.ptw-cr02.plus.net [212.159.0.118]
  5    37 ms    47 ms    38 ms  ae2.ptw-cr01.plus.net [195.166.129.4]
  6    38 ms    37 ms    37 ms  te9-4.ptn-gw01.plus.net [195.166.129.33]
  7    38 ms    37 ms    37 ms  tun0.ptn-gw01.plus.net [212.159.2.101]
  8    37 ms    42 ms    37 ms  te2-1.gr9.plus.net [212.159.2.110]
  9    38 ms    37 ms    37 ms  195.99.126.138
 10    40 ms    38 ms    38 ms  host213-121-193-136.ukcore.bt.net [213.121.193.136]
 11    43 ms    39 ms    42 ms  host213-121-193-64.ukcore.bt.net [213.121.193.64]
 12    39 ms    39 ms    39 ms  mgre.customer.bt.net [194.72.9.2]
 13    84 ms    38 ms    39 ms  t2c3-xe-10-0-0-0.uk-eal.eu.bt.net [166.49.168.1]
 14    39 ms    38 ms    39 ms  t2c1-ge8-0-0.uk-eal.eu.bt.net [166.49.237.17]
 15    39 ms    39 ms    39 ms  t2c2-p3-0-0.uk-lon1.eu.bt.net [166.49.208.210]
 16    40 ms    39 ms    39 ms  t2c3-xe-0-3-1-0.uk-lon1.eu.bt.net [166.49.237.246]
 17     *        *        *     Request timed out.
 18   124 ms   118 ms   118 ms  vb1042.rar3.nyc-ny.us.xo.net [207.88.13.202]
 19   191 ms   190 ms   190 ms  te-3-0-0.rar3.washington-dc.us.xo.net [207.88.12.74]
 20   190 ms   190 ms   190 ms  te-11-0-0.rar3.sanjose-ca.us.xo.net [207.88.12.69]
 21   201 ms   185 ms   186 ms  ae0d0.mcr1.fremont-ca.us.xo.net [216.156.0.138]
 22   189 ms   190 ms   189 ms  209.116.66.222
 23   188 ms   187 ms   187 ms  d01.megashares.com [71.5.11.11]
Trace complete.

It does work from another non-Plusnet connection.
I notice the routing goes via BT - I bet that is significant!

[#3]

agreed, i can do a traceroute but can't access the site via PN but can on another connection

traceroute to d01.megashares.com (71.5.11.11), 64 hops max, 52 byte packets
 1  10.0.1.1 (10.0.1.1)  1213.175 ms  3.367 ms  2.989 ms
 2  lo0-central10.pcl-ag04.plus.net (195.166.128.185)  18.151 ms  17.565 ms  38.273 ms
 3  link-b-central10.pcl-gw02.plus.net (212.159.2.174)  16.959 ms  29.244 ms  17.510 ms
 4  xe-0-2-0.pcl-cr02.plus.net (212.159.0.206)  16.752 ms  16.318 ms  17.094 ms
 5  ae2.pcl-cr01.plus.net (195.166.129.6)  18.327 ms  16.666 ms  18.352 ms
 6  ae1.ptw-cr01.plus.net (195.166.129.0)  41.681 ms  21.368 ms  35.179 ms
 7  te9-4.ptn-gw01.plus.net (195.166.129.33)  17.958 ms  17.528 ms  17.114 ms
 8  tun0.ptn-gw01.plus.net (212.159.2.101)  19.126 ms  17.702 ms  17.123 ms
 9  te2-1.gr9.plus.net (212.159.2.110)  18.556 ms  20.670 ms  17.689 ms
10  195.99.126.138 (195.99.126.138)  16.904 ms  20.280 ms  35.623 ms
11  core2-te0-9-0-14.faraday.ukcore.bt.net (213.121.193.136)  25.736 ms
    core1-te0-15-0-10.ealing.ukcore.bt.net (109.159.254.206)  24.488 ms
    core2-te0-9-0-14.faraday.ukcore.bt.net (213.121.193.136)  18.717 ms
12  core1-te0-4-0-3.ealing.ukcore.bt.net (62.172.103.185)  20.297 ms
    transit1-pos2-1.ealing.ukcore.bt.net (194.72.9.2)  19.531 ms
    core1-te0-4-0-3.ealing.ukcore.bt.net (62.172.103.185)  19.479 ms
13  transit1-pos2-1.ealing.ukcore.bt.net (194.72.9.2)  20.382 ms  19.229 ms
    t2c3-xe-9-2-0-0.uk-eal.eu.bt.net (166.49.168.25)  38.877 ms
14  t2c3-xe-9-2-0-0.uk-eal.eu.bt.net (166.49.168.25)  21.658 ms  18.894 ms  19.579 ms
15  t2c1-ge14-0-0.uk-eal.eu.bt.net (166.49.237.29)  21.094 ms  18.947 ms  18.407 ms
16  t2c2-p3-0-1.uk-lon1.eu.bt.net (166.49.208.110)  18.337 ms  19.587 ms  19.686 ms
17  t2c3-xe-0-3-1-0.uk-lon1.eu.bt.net (166.49.237.246)  19.725 ms  20.259 ms  19.635 ms
18  vb1042.rar3.nyc-ny.us.xo.net (207.88.13.202)  103.940 ms * *
19  vb1042.rar3.nyc-ny.us.xo.net (207.88.13.202)  123.941 ms  99.266 ms  93.058 ms
20  te-3-0-0.rar3.washington-dc.us.xo.net (207.88.12.74)  174.180 ms  165.785 ms
    te-11-0-0.rar3.sanjose-ca.us.xo.net (207.88.12.69)  171.156 ms
21  te-11-0-0.rar3.sanjose-ca.us.xo.net (207.88.12.69)  168.790 ms  167.499 ms
    ae0d0.mcr1.fremont-ca.us.xo.net (216.156.0.138)  166.653 ms
22  209.116.66.222 (209.116.66.222)  168.821 ms
    ae0d0.mcr1.fremont-ca.us.xo.net (216.156.0.138)  166.654 ms  167.544 ms
23  d01.megashares.com (71.5.11.11)  167.915 ms
    209.116.66.222 (209.116.66.222)  168.678 ms  168.564 ms

[#4]

I suspect this has something to do with it:

Quote from: jelv

7    38 ms    37 ms    37 ms  tun0.ptn-gw01.plus.net [212.159.2.101]

The traffic's getting routed via our IWF proxy.
An internal problem has been raised to address this (ref: 77193).

[#5]

i thought the iwf proxy had iwf in its host name, has that changed or am I remembering incorrectly?

[#6]

So does this mean I will be able to access it soon? . It dosnt actually come up with the iwf security warning just says its unavailable. ? Thanks for all the replies.

[#7]

there isn't an iwf warning, that's part of the problem. the secret list remains secret...

[#8]

Quote from: flamazine

So does this mean I will be able to access it soon?

Yes. I'll post back here once it's fixed.

[#9]

Should be sorted now.

[#10]

is the same thing that's stopping me getting into https://www.three.co.uk/My3Account/Login

?
I have to ask because it used to work fine, then it stopped working on one pc but worked fine through another but now it fails every time I try no matter which machine I use (different OS's different browsers) unfortunately I don't have the ability to try from a different connection though

[#11]

Bit of a delayed response but I can load that website without problems.

[#12]

I can load the website but I cant login, its not a massive problem as I can use the various handsets to login with, I know that others have had a similar issue with the 3 website but I don't know if its ISP related or just a problem with the website hence my asking 

[#13]

I'm on three for my mobile service and can log in without issue, so it doesn't appear to be a general issue.

[#14]

then its probably something in the pc settings I have causing it, good to know but really annoying to find and fix /