Author Topic: Sites not rendering correctly  (Read 1451 times)

Silvermane

  • Jr. Member
  • **
  • Posts: 90
    • View Profile
Sites not rendering correctly
« on: July 11, 2011, 03:37:34 PM »
Some sites aren't rendering correctly, others are slow.

LinkedIn for example, renders as text only.

Tested on two different machines, and five different browsers.

Using a 3G access hotspot with the same machines works fine.


MediacomDallas

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 10324
    • View Profile
Re: Sites not rendering correctly
« Reply #1 on: July 11, 2011, 03:40:00 PM »
This is a problem we are currently investigating. Can you run the following tests in the command prompt and paste the results here?

Ping yahoo.com
Ping yahoo.com l 1400 -f
Ping yahoo.com l 1492 -f

Also, do the same set of commands for linkedin and any other websites you're having issues with.

Silvermane

  • Jr. Member
  • **
  • Posts: 90
    • View Profile
Re: Sites not rendering correctly
« Reply #2 on: July 11, 2011, 03:52:34 PM »

C:\>ping yahoo.com

Pinging yahoo.com [69.147.125.65] with 32 bytes of data:

Reply from 69.147.125.65: bytes=32 time=34ms TTL=50
Reply from 69.147.125.65: bytes=32 time=38ms TTL=50
Reply from 69.147.125.65: bytes=32 time=33ms TTL=50
Reply from 69.147.125.65: bytes=32 time=33ms TTL=50

Ping statistics for 69.147.125.65:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 38ms, Average = 34ms

C:\>ping -l 1400 -f yahoo.com

Pinging yahoo.com [69.147.125.65] with 1400 bytes of data:

Request timed out.
Reply from 69.147.125.65: bytes=1400 time=36ms TTL=50
Reply from 69.147.125.65: bytes=1400 time=36ms TTL=50
Reply from 69.147.125.65: bytes=1400 time=41ms TTL=50

Ping statistics for 69.147.125.65:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 36ms, Maximum = 41ms, Average = 37ms

C:\>ping -l 1492 -f yahoo.com

Pinging yahoo.com [69.147.125.65] with 1492 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 69.147.125.65:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\>ping linkedin.com

Pinging linkedin.com [216.52.242.86] with 32 bytes of data:

Reply from 216.52.242.86: bytes=32 time=66ms TTL=241
Reply from 216.52.242.86: bytes=32 time=70ms TTL=241
Reply from 216.52.242.86: bytes=32 time=67ms TTL=241
Reply from 216.52.242.86: bytes=32 time=67ms TTL=241

Ping statistics for 216.52.242.86:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 66ms, Maximum = 70ms, Average = 67ms

C:\>ping -l 1400 -f linkedin.com

Pinging linkedin.com [216.52.242.86] with 1400 bytes of data:

Reply from 216.52.242.86: bytes=1400 time=70ms TTL=241
Reply from 216.52.242.86: bytes=1400 time=69ms TTL=241
Reply from 216.52.242.86: bytes=1400 time=92ms TTL=241
Reply from 216.52.242.86: bytes=1400 time=69ms TTL=241

Ping statistics for 216.52.242.86:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 69ms, Maximum = 92ms, Average = 75ms

C:\>ping -l 1492 -f linkedin.com

Pinging linkedin.com [216.52.242.86] with 1492 bytes of data:

Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.

Ping statistics for 216.52.242.86:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

MediacomDallas

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 10324
    • View Profile
Re: Sites not rendering correctly
« Reply #3 on: July 11, 2011, 04:14:49 PM »
Thank you. I have one more thing I would like you to try.

tracert yahoo.com and tracert linkedin.com

Silvermane

  • Jr. Member
  • **
  • Posts: 90
    • View Profile
Re: Sites not rendering correctly
« Reply #4 on: July 11, 2011, 04:24:46 PM »
C:\>tracert yahoo.com

Tracing route to yahoo.com [69.147.125.65]
over a maximum of 30 hops:

  1     2 ms    <1 ms     1 ms  192.168.123.1
  2     9 ms     8 ms     8 ms  10.6.5.1
  3    22 ms    18 ms    18 ms  172.30.28.249
  4    14 ms    13 ms    14 ms  172.30.31.70
  5    13 ms    11 ms    15 ms  172.30.31.73
  6    27 ms    50 ms    27 ms  12.86.140.141
  7    21 ms    19 ms    18 ms  cr83.attga.ip.att.net [12.122.141.134]
  8     *        *        *     Request timed out.
  9    21 ms    20 ms    23 ms  attga01jt.ip.att.net [12.122.80.185]
 10   244 ms    37 ms    41 ms  192.205.37.82
 11    58 ms    64 ms    69 ms  Yahoo.Te3-3.1189.ar4.DCA3.gblx.net [64.208.169.242]
 12    44 ms    40 ms    41 ms  ae-1-d150.msr2.re1.yahoo.com [216.115.108.21]
 13    36 ms    36 ms    36 ms  te-7-2.bas-a1.re1.yahoo.com [66.196.112.207]
 14    63 ms    57 ms   100 ms  ir1.fp.vip.re1.yahoo.com [69.147.125.65]

Trace complete.

C:\>tracert linkedin.com

Tracing route to linkedin.com [216.52.242.86]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.123.1
  2     9 ms     7 ms     8 ms  10.6.5.1
  3    11 ms    16 ms    11 ms  172.30.28.249
  4    12 ms    13 ms    12 ms  172.30.31.70
  5    34 ms    11 ms    12 ms  172.30.31.73
  6    29 ms    35 ms    19 ms  12-215-0-26.client.mchsi.com [12.215.0.26]
  7    69 ms    70 ms    75 ms  cr83.attga.ip.att.net [12.122.141.62]
  8     *        *        *     Request timed out.
  9    69 ms    70 ms    69 ms  cr2.dlstx.ip.att.net [12.122.28.174]
 10    71 ms    94 ms    73 ms  cr2.la2ca.ip.att.net [12.122.28.178]
 11   134 ms   146 ms    64 ms  12.122.104.69
 12     *        *        *     Request timed out.
 13    66 ms    77 ms    66 ms  border1.po2-20g-bbnet2.lax008.pnap.net [216.52.255.110]
 14    66 ms    69 ms   102 ms  linkedin-13.border1.lax008.pnap.net [216.52.220.122]
 15    69 ms    65 ms    66 ms  news.linkedin.com [216.52.242.86]

Trace complete.

MediacomDallas

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 10324
    • View Profile
Re: Sites not rendering correctly
« Reply #5 on: July 11, 2011, 04:30:01 PM »
Thank you. I apologize for the ongoing problems here.

Silvermane

  • Jr. Member
  • **
  • Posts: 90
    • View Profile
Re: Sites not rendering correctly
« Reply #6 on: July 11, 2011, 06:30:28 PM »
Received two automated calls telling me that my problem has been fixed, when it hasn't.

MediacomChrisL

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 9315
    • View Profile
Re: Sites not rendering correctly
« Reply #7 on: July 11, 2011, 06:31:23 PM »
Those calls were about the TV issue that we have logged for you. I apologize for the confusion.

Chris

Silvermane

  • Jr. Member
  • **
  • Posts: 90
    • View Profile
Re: Sites not rendering correctly
« Reply #8 on: July 11, 2011, 06:59:20 PM »
TV issue isn't resolved either, in fact its gotten worse.....the few channels I could get are dropping out now....

MediacomChrisL

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 9315
    • View Profile
Re: Sites not rendering correctly
« Reply #9 on: July 11, 2011, 07:00:00 PM »
Okay, I will let dispatch know. Thank you.

Chris

Silvermane

  • Jr. Member
  • **
  • Posts: 90
    • View Profile
Re: Sites not rendering correctly
« Reply #10 on: July 12, 2011, 06:46:53 AM »
Any chance of getting the internet problems fixed today?

MediacomBill

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 10531
    • View Profile
Re: Sites not rendering correctly
« Reply #11 on: July 12, 2011, 07:48:43 AM »
I was out yesterday but I just saw an email regarding this issue asking for examples. I will include what you are experiencing.

Silvermane

  • Jr. Member
  • **
  • Posts: 90
    • View Profile
Re: Sites not rendering correctly
« Reply #12 on: July 12, 2011, 08:40:18 AM »


Pinging yahoo.com [98.137.149.56] with 32 bytes of data:



Reply from 98.137.149.56: bytes=32 time=77ms TTL=47

Reply from 98.137.149.56: bytes=32 time=120ms TTL=47

Reply from 98.137.149.56: bytes=32 time=75ms TTL=47

Reply from 98.137.149.56: bytes=32 time=78ms TTL=47



Ping statistics for 98.137.149.56:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 75ms, Maximum = 120ms, Average = 87ms



Pinging yahoo.com [98.137.149.56] with 1400 bytes of data:



Reply from 98.137.149.56: bytes=1400 time=78ms TTL=47

Reply from 98.137.149.56: bytes=1400 time=379ms TTL=47

Reply from 98.137.149.56: bytes=1400 time=81ms TTL=47

Reply from 98.137.149.56: bytes=1400 time=79ms TTL=47



Ping statistics for 98.137.149.56:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 78ms, Maximum = 379ms, Average = 154ms



Pinging yahoo.com [98.137.149.56] with 1492 bytes of data:



Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.



Ping statistics for 98.137.149.56:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Tracing route to yahoo.com [98.137.149.56]

over a maximum of 30 hops:



  1    <1 ms    <1 ms    <1 ms  192.168.123.1

  2     8 ms    19 ms    16 ms  10.6.5.1

  3    11 ms    19 ms     9 ms  172.30.28.249

  4    11 ms    11 ms    10 ms  172.30.31.70

  5     9 ms    10 ms    10 ms  172.30.31.77

  6    15 ms    17 ms    15 ms  12.116.20.41

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9    18 ms    18 ms    18 ms  attga01jt.ip.att.net [12.122.80.221]

 10    34 ms    19 ms    16 ms  192.205.35.90

 11    17 ms    17 ms    21 ms  ae1-40G.scr1.ATL1.gblx.net [67.16.131.197]

 12    87 ms    78 ms    74 ms  xe8-1-0-10G.scr3.SNV2.gblx.net [67.16.163.106]

 13    76 ms    81 ms    75 ms  e8-1-20G.ar5.SJC2.gblx.net [67.16.145.118]

 14    74 ms   176 ms    80 ms  YAHOO.TenGigabitEthernet2-4.1189.ar3.SJC2.gblx.net [208.48.239.254]

 15    90 ms    90 ms    90 ms  ae-1-d171.msr2.sp1.yahoo.com [216.115.107.87]

 16    90 ms    93 ms   103 ms  et-17-25.fab1-1-gdc.sp2.yahoo.com [98.136.16.19]

 17    84 ms    97 ms    99 ms  te-8-1.bas2-1-prd.sp2.yahoo.com [67.195.130.104]

 18    87 ms    77 ms    82 ms  ir1.fp.vip.sp2.yahoo.com [98.137.149.56]



Trace complete.



Pinging linkedin.com [216.52.242.86] with 32 bytes of data:



Reply from 216.52.242.86: bytes=32 time=67ms TTL=238

Reply from 216.52.242.86: bytes=32 time=65ms TTL=238

Reply from 216.52.242.86: bytes=32 time=66ms TTL=238

Reply from 216.52.242.86: bytes=32 time=65ms TTL=238



Ping statistics for 216.52.242.86:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 65ms, Maximum = 67ms, Average = 65ms



Pinging linkedin.com [216.52.242.86] with 1400 bytes of data:



Reply from 216.52.242.86: bytes=1400 time=71ms TTL=238

Reply from 216.52.242.86: bytes=1400 time=285ms TTL=238

Reply from 216.52.242.86: bytes=1400 time=459ms TTL=238

Reply from 216.52.242.86: bytes=1400 time=76ms TTL=238



Ping statistics for 216.52.242.86:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 71ms, Maximum = 459ms, Average = 222ms



Pinging linkedin.com [216.52.242.86] with 1492 bytes of data:



Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.



Ping statistics for 216.52.242.86:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Tracing route to linkedin.com [216.52.242.86]

over a maximum of 30 hops:



  1     1 ms    <1 ms    <1 ms  192.168.123.1

  2    10 ms     8 ms     9 ms  10.6.5.1

  3    18 ms    10 ms    11 ms  172.30.28.249

  4    11 ms    12 ms    12 ms  172.30.31.70

  5    11 ms    12 ms    10 ms  172.30.31.73

  6    15 ms    16 ms    15 ms  12-215-0-26.client.mchsi.com [12.215.0.26]

  7    68 ms    68 ms    88 ms  cr83.attga.ip.att.net [12.122.141.62]

  8     *        *        *     Request timed out.

  9    69 ms    71 ms    68 ms  cr2.dlstx.ip.att.net [12.122.28.174]

 10    77 ms    77 ms    79 ms  cr2.la2ca.ip.att.net [12.122.28.178]

 11    70 ms    67 ms    65 ms  12.122.104.69

 12     *        *        *     Request timed out.

 13    66 ms    66 ms    66 ms  border1.po2-20g-bbnet2.lax008.pnap.net [216.52.255.110]

 14    67 ms    70 ms    66 ms  linkedin-13.border1.lax008.pnap.net [216.52.220.122]

 15    66 ms    67 ms    67 ms  news.linkedin.com [216.52.242.86]



Trace complete.



Pinging techcrunch.com [74.200.247.59] with 32 bytes of data:



Reply from 74.200.247.59: bytes=32 time=49ms TTL=47

Reply from 74.200.247.59: bytes=32 time=43ms TTL=47

Reply from 74.200.247.59: bytes=32 time=42ms TTL=47

Reply from 74.200.247.59: bytes=32 time=73ms TTL=47



Ping statistics for 74.200.247.59:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 42ms, Maximum = 73ms, Average = 51ms



Pinging techcrunch.com [74.200.247.59] with 1400 bytes of data:



Reply from 74.200.247.59: bytes=1400 time=47ms TTL=47

Reply from 74.200.247.59: bytes=1400 time=47ms TTL=47

Reply from 74.200.247.59: bytes=1400 time=55ms TTL=47

Reply from 74.200.247.59: bytes=1400 time=50ms TTL=47



Ping statistics for 74.200.247.59:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 47ms, Maximum = 55ms, Average = 49ms



Pinging techcrunch.com [74.200.247.59] with 1492 bytes of data:



Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.



Ping statistics for 74.200.247.59:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Tracing route to techcrunch.com [74.200.247.59]

over a maximum of 30 hops:



  1    10 ms    <1 ms    <1 ms  192.168.123.1

  2     9 ms     9 ms     9 ms  10.6.5.1

  3    14 ms    29 ms    30 ms  172.30.28.249

  4    13 ms   284 ms    27 ms  172.30.31.70

  5    14 ms    12 ms    12 ms  172.30.31.77

  6    18 ms    19 ms    29 ms  12.86.140.141

  7    48 ms    44 ms    44 ms  cr84.attga.ip.att.net [12.122.140.134]

  8     *        *        *     Request timed out.

  9     *       44 ms    53 ms  cr1.nsvtn.ip.att.net [12.122.28.106]

 10    43 ms    44 ms    45 ms  cr2.nsvtn.ip.att.net [12.122.28.70]

 11    46 ms    44 ms    42 ms  cr1.cl2oh.ip.att.net [12.122.28.74]

 12    45 ms    48 ms    46 ms  cr1.cgcil.ip.att.net [12.122.2.205]

 13    53 ms    44 ms    43 ms  cgcil405me3.ip.att.net [12.122.99.13]

 14    44 ms    42 ms    44 ms  12.94.24.10

 15    74 ms    42 ms    43 ms  border5.po1-bbnet1.chg.pnap.net [64.94.32.10]

 16    46 ms    43 ms    45 ms  layeredtech-6.border5.chg.pnap.net [74.217.8.10]

 17    59 ms    48 ms    61 ms  edge10.crg.chgo.fastservers.net [74.200.241.38]

 18    42 ms    41 ms    42 ms  wordpress.com [74.200.247.59]



Trace complete.



Pinging woot.com [208.94.146.71] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 208.94.146.71:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Pinging woot.com [208.94.146.71] with 1400 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 208.94.146.71:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Pinging woot.com [208.94.146.71] with 1492 bytes of data:



Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.



Ping statistics for 208.94.146.71:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Tracing route to woot.com [208.94.146.71]

over a maximum of 30 hops:



  1    <1 ms    <1 ms    <1 ms  192.168.123.1

  2    10 ms     8 ms     *     10.6.5.1

  3    12 ms    11 ms    10 ms  172.30.28.249

  4    10 ms    20 ms    16 ms  172.30.31.70

  5    11 ms    11 ms    10 ms  172.30.31.77

  6    18 ms    17 ms    16 ms  12.86.140.141

  7     *      151 ms    27 ms  cr84.attga.ip.att.net [12.122.140.134]

  8     *        *        *     Request timed out.

  9    17 ms    26 ms    18 ms  attga04jt.ip.att.net [12.122.84.149]

 10    17 ms   133 ms    17 ms  ae15.edge5.atlanta2.level3.net [4.68.62.225]

 11    31 ms    17 ms   197 ms  vlan52.ebr2.Atlanta2.Level3.net [4.69.150.126]

 12     *        *        *     Request timed out.

 13    33 ms    37 ms    36 ms  ae-2-2.ebr1.Washington1.Level3.net [4.69.132.86]

 14    33 ms    33 ms    33 ms  ae-71-71.csw2.Washington1.Level3.net [4.69.134.134]

 15    33 ms    33 ms    33 ms  ae-22-70.car2.Washington1.Level3.net [4.69.149.68]

 16  TIGGEE-LLC.car2.Washington1.Level3.net [4.59.146.18]  reports: Destination net unreachable.



Trace complete.


MediacomBill

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 10531
    • View Profile
Re: Sites not rendering correctly
« Reply #13 on: July 12, 2011, 08:48:45 AM »
Thank you.

Silvermane

  • Jr. Member
  • **
  • Posts: 90
    • View Profile
Re: Sites not rendering correctly
« Reply #14 on: July 12, 2011, 09:35:31 AM »


Pinging meritline.com [98.129.100.93] with 32 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 98.129.100.93:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Pinging meritline.com [98.129.100.93] with 1400 bytes of data:



Request timed out.

Request timed out.

Request timed out.

Request timed out.



Ping statistics for 98.129.100.93:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Pinging meritline.com [98.129.100.93] with 1492 bytes of data:



Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.



Ping statistics for 98.129.100.93:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Tracing route to meritline.com [98.129.100.93]

over a maximum of 30 hops:



  1    <1 ms    <1 ms     1 ms  192.168.123.1

  2    12 ms     8 ms    10 ms  10.6.5.1

  3    13 ms    13 ms    11 ms  172.30.28.249

  4    12 ms    13 ms    14 ms  172.30.31.70

  5    11 ms    12 ms    13 ms  172.30.31.77

  6    67 ms    18 ms   214 ms  12.118.120.181

  7    35 ms    35 ms    37 ms  cr81.attga.ip.att.net [12.122.141.142]

  8     *        *        *     Request timed out.

  9    49 ms    35 ms    43 ms  cr2.dlstx.ip.att.net [12.122.28.174]

 10    34 ms    37 ms    33 ms  gar6.dlstx.ip.att.net [12.122.100.65]

 11    35 ms    36 ms    34 ms  12.90.228.14

 12    34 ms    37 ms    34 ms  border2.ge1-1-bbnet1.ext1a.dal.pnap.net [216.52.191.25]

 13    38 ms    37 ms    41 ms  rackmanaged-3.border2.ext1a.dal.pnap.net [63.251.32.50]

 14    35 ms    35 ms    37 ms  vlan903.core3.dfw1.rackspace.com [72.3.128.53]

 15    36 ms    39 ms    35 ms  aggr102a.dfw1.rackspace.net [72.3.129.57]

 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.


MediacomBill

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 10531
    • View Profile
Re: Sites not rendering correctly
« Reply #15 on: July 12, 2011, 09:36:22 AM »
Could you please enter this in the command prompt and let me know the results.

Telnet [spacebar] sitename [spacebar] 80

copy results

then enter

Telnet [spacebar} sitename [spacebar] 443

Thanks

Silvermane

  • Jr. Member
  • **
  • Posts: 90
    • View Profile
Re: Sites not rendering correctly
« Reply #16 on: July 12, 2011, 10:06:21 AM »
Port 80 connections seem to work fine, if slow for the sites I tried.

Port 443 either fails immediately or after a short period with the following:

Connecting To linkedin.com...Could not open connection to the host, on port 443: Connect failed
Connecting To woot.com...Could not open connection to the host, on port 443: Connect failed

MediacomBill

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 10531
    • View Profile
Re: Sites not rendering correctly
« Reply #17 on: July 12, 2011, 10:09:06 AM »
Thank you, I will pass that info on.
                                                                   

MediacomChrisL

  • Mediacom Social Media Relations Team
  • Global Moderator
  • *****
  • Posts: 9315
    • View Profile
Re: Sites not rendering correctly
« Reply #18 on: July 12, 2011, 10:39:39 AM »
This should be working now from what NOC is telling me, can we get someone to do some retests on their end?

Silvermane

  • Jr. Member
  • **
  • Posts: 90
    • View Profile
Re: Sites not rendering correctly
« Reply #19 on: July 12, 2011, 01:28:31 PM »
No, somethings still not right......site tries to complete, but takes minutes instead of seconds....see below



Pinging linkedin.com [216.52.242.86] with 32 bytes of data:



Reply from 216.52.242.86: bytes=32 time=88ms TTL=241

Reply from 216.52.242.86: bytes=32 time=87ms TTL=241

Reply from 216.52.242.86: bytes=32 time=87ms TTL=241

Reply from 216.52.242.86: bytes=32 time=72ms TTL=241



Ping statistics for 216.52.242.86:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 72ms, Maximum = 88ms, Average = 83ms



Pinging linkedin.com [216.52.242.86] with 1400 bytes of data:



Reply from 216.52.242.86: bytes=1400 time=77ms TTL=241

Reply from 216.52.242.86: bytes=1400 time=70ms TTL=241

Reply from 216.52.242.86: bytes=1400 time=70ms TTL=241

Reply from 216.52.242.86: bytes=1400 time=71ms TTL=241



Ping statistics for 216.52.242.86:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 70ms, Maximum = 77ms, Average = 72ms



Pinging linkedin.com [216.52.242.86] with 1492 bytes of data:



Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.

Packet needs to be fragmented but DF set.



Ping statistics for 216.52.242.86:

    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),



Tracing route to linkedin.com [216.52.242.86]

over a maximum of 30 hops:



  1    <1 ms    <1 ms    <1 ms  192.168.123.1

  2     9 ms    13 ms     8 ms  10.6.5.1

  3    10 ms    11 ms    17 ms  172.30.28.249

  4    12 ms    12 ms    10 ms  172.30.31.70

  5    11 ms    10 ms    12 ms  172.30.31.73

  6    18 ms    16 ms    22 ms  12-215-0-26.client.mchsi.com [12.215.0.26]

  7    67 ms    72 ms    81 ms  cr83.attga.ip.att.net [12.122.141.62]

  8    67 ms    66 ms    67 ms  cr1.attga.ip.att.net [12.123.22.109]

  9    67 ms    68 ms    89 ms  cr2.dlstx.ip.att.net [12.122.28.174]

 10    66 ms    76 ms    67 ms  cr2.la2ca.ip.att.net [12.122.28.178]

 11    65 ms   183 ms   175 ms  12.122.104.69

 12    68 ms    66 ms    66 ms  12.91.226.18

 13    69 ms    65 ms    66 ms  border1.po2-20g-bbnet2.lax008.pnap.net [216.52.255.110]

 14    69 ms    66 ms    67 ms  linkedin-13.border1.lax008.pnap.net [216.52.220.122]

 15    75 ms    70 ms    66 ms  today.linkedin.com [216.52.242.86]



Trace complete.

C:\>telnet linkedin.com 443
Connecting To linkedin.com...Could not open connection to the host, on port 443: Connect failed