Jonathan N. Little wrote on 11/02/2015 23:48:
Ray_Net wrote:
Jonathan N. Little wrote on 11/02/2015 17:47:
Larry S. wrote:
..Connection and firewall? No problem on other sites.
..Java Platform "Always activate"
..Java Deployment Toolkit "Ask to activate" (didn't ask, though my
banking on-line deposit does ask)
..No adblocker.
..All plug-ins up to date (per Addons Manager)
..Doesn't work on IE either
..Tech support at the site says "WFM on Firefox"; also says the site
apparently doesn't finish loading completely for me
So, where am I? It's got to be a preference, missing software or
plugin,
something. Probably should just give up; there are other more
important
things in life!
Well just something to check since the videos do not work with a
different browser, maybe the problem is *external* to you. It took me
6 months to prove to Verizon that they had a bad board at the area's
NOC that was disrupting routing for DSL users here.
The video is being served from a media server c.brightcove.com. Try
and so a trace route and see if you get access to their server. You're
on Windows so open the command window:
WINDOWS KEY + R
enter CMD
then in command window
tracert c.brightcove.com
and see if you can reach the server.
Doesnot reach the server from my pc:
C:\Users\RAY>tracert c.brightcove.com
Tracing route to gobbles-aws-226538871.eu-west-1.elb.amazonaws.com
[54.246.112.4
4]
over a maximum of 30 hops:
8 35 ms 31 ms 33 ms 195.66.225.175
9 * * * Request timed out.
10 * * * Request timed out.
11 46 ms 46 ms 45 ms 176.32.106.36
12 58 ms 65 ms 44 ms 178.236.1.137
13 42 ms 43 ms 42 ms 178.236.0.194
14 54 ms 46 ms 42 ms 178.236.0.68
15 43 ms 43 ms 45 ms
ec2-79-125-0-81.eu-west-1.compute.amazonaws.com
[79.125.0.81]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
Looks like you got an issue there, only 10 hops here from Linux:
jonathan@gypsy:~$ traceroute -n c.brightcove.com
traceroute to c.brightcove.com (64.74.101.75), 30 hops max, 60 byte
packets
1 192.168.57.1 1.285 ms 2.468 ms 2.533 ms
2 192.168.1.1 2.704 ms 3.784 ms 4.597 ms
3 108.15.160.1 34.981 ms 36.001 ms 36.723 ms
4 130.81.174.184 38.824 ms 39.938 ms 40.889 ms
5 130.81.20.140 46.278 ms 47.005 ms 48.142 ms
6 140.222.231.203 69.852 ms 69.076 ms 67.738 ms
7 152.179.134.214 67.741 ms 68.706 ms 68.723 ms
8 63.251.128.107 69.378 ms 63.251.128.43 57.223 ms 63.251.128.107
63.538 ms
9 66.150.193.82 62.847 ms 60.641 ms 59.553 ms
10 64.74.101.75 58.985 ms 56.313 ms 57.936 ms
Or Windows:
C:\Users\Jonathan>tracert -d c.brightcove.com
Tracing route to ca.brightcove.net [64.74.101.75]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.57.1
2 <1 ms <1 ms <1 ms 192.168.1.1
3 33 ms 32 ms 33 ms 108.15.160.1
4 34 ms 107 ms 112 ms 130.81.174.184
5 38 ms 38 ms 39 ms 130.81.20.140
6 55 ms 55 ms 57 ms 140.222.231.203
7 56 ms 56 ms 57 ms 152.179.134.214
8 58 ms 57 ms 58 ms 63.251.128.107
9 58 ms 58 ms 57 ms 66.150.193.82
10 57 ms 57 ms 57 ms 64.74.101.75
Trace complete.
How did you understand that c.brightcove.com is not the same host as your ?
C:\Users\RAY>ping c.brightcove.com
Pinging gobbles-aws-226538871.eu-west-1.elb.amazonaws.com
[46.137.183.218] with
32 bytes of data:
If I use your ip-adress instead of c.brightcove.com it goes well .... Is
the DNS server of my isp BAD ?
C:\Users\RAY>tracert -d 64.74.101.75
Tracing route to 64.74.101.75 over a maximum of 30 hops
1 2 ms 1 ms 2 ms 192.168.1.1
2 25 ms 24 ms 24 ms 62.235.164.1
3 27 ms 24 ms 26 ms 91.183.244.20
4 24 ms 23 ms 24 ms 91.183.246.108
5 24 ms 25 ms 24 ms 62.115.40.97
6 32 ms 32 ms 31 ms 62.115.140.50
7 128 ms 146 ms 155 ms 80.91.251.96
8 137 ms 135 ms 133 ms 80.91.246.125
9 124 ms 120 ms 120 ms 62.115.38.110
10 243 ms 214 ms 200 ms 63.251.128.107
11 127 ms 127 ms 128 ms 66.150.193.82
12 119 ms 119 ms 121 ms 64.74.101.75
Trace complete.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
