Help for 23: 23 is showing up as text only?

23 is showing up as text only?

	PayPaul December 08, 2009, 12:43 PM
	23 is showing up as text only for me. There are no photos and no graphics at all. I recently upgraded and installed JRE 6 and also installed the JaVA plugin for Mozilla. Could that be the problem or is this a bug sitewide?

	striatic December 08, 2009, 12:52 PM
	no problems here whatsoever.

	PayPaul December 08, 2009, 01:37 PM
	Gee. I'm so glad for you. What browser are you using. What I've noticed is that it's a firefox problem that may be linked to my recent installation of JAVA. I'm able to load the site properly using Netscape Navigator 9. However I'm still getting site problems with pinging and the traceroute Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\PaulW>ping www.23hq.com Pinging www.23hq.com [77.66.17.58] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 77.66.17.58: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\PaulW>tracert www.23hq.com Tracing route to www.23hq.com [77.66.17.58] over a maximum of 30 hops: 1 * * * Request timed out. 2 * * * Request timed out. 3 * * * Request timed out. 4 * * * Request timed out. 5 * * * Request timed out. 6 * * * Request timed out. 7 * * * Request timed out. 8 * * * Request timed out. 9 * * * Request timed out. 10 * * * Request timed out. 11 * * * Request timed out. 12 * * * Request timed out. 13 * * * Request timed out. 14 * * 2445 ms 77.66.17.58 Trace complete. This has to be a firefox problem that I haven't been able to resolve yet. Clearing cookies and the cache doesn't solve the issue. It would be appreciated if someone were to post an answer based upon their experience with the problem.

	striatic December 08, 2009, 01:49 PM
	sorry for trying to help the staff [and you] figure out if it is a pervasive problem or not. you did ask if it was a sitewide problem, did you not? i was using chromium, but site works fine in firefox for me too.

	PayPaul December 08, 2009, 02:08 PM
	C'mon Striatic, saying you have no problems really isn't contributing much. I asked that question about it being sitewide as a possibility. Given my pinging problems with 23 that was a reasonable assumption. What I have discovered is that it's a problem that is more associated with Firefox and perhaps JAVA as that was the most recent change I performed on the browser. If someone else is using firefox and has installed JaVA JRE 6 and the Firefox Java plugin they may have run into similar issues. I'm also running Vista 64 if that is of any further assistance in the diagnosis 23 does run quite well strangely enough using netscape navigator. I even just uploaded 5 photos pretty quickly using it. I'm hoping Staff sees my ping/traceroute record and has some constructive ideas.

	IkoTikashi December 08, 2009, 02:13 PM
	You mean you have a horrible ping, but can upload/browse using Netscape without problems? Any proxies set? Are you using a special Firefox-addon or something? Any other site slow on Firefox? I have no problems here btw :)

	striatic December 08, 2009, 02:24 PM
	if you really want to narrow it down, you can backup and move your firefox profile folder, fire up firefox and see how it performs 'clean' against the site with a fresh set of settings. if performance remains problematic, the issue is most likely unrelated to the browser and its plugin/proxy setup. if performance improves, you can move your old profile back into place and start troubleshooting its plugin/proxy setup.

	Th Clvr Mnky December 08, 2009, 02:28 PM
	Assuming your firewall is letting ICMP return packets back in, that traceroute suggests the problem is a your end. The traffic can't even get past the first router. However, given you report you can get here with some other browser, I guess this means your network cannot receive ICMP packets in order to run these utilities. Otherwise, I'd suggest that any content you are seeing is your browser rendering cached content while it waits for fresh data to be returned. I have no idea what is going on, if this is the case. AFAIK, there is no need for Java on 23. It's all HTML and Javascript frameworks. FF 3.5.5 works ok from SW Ontario (slowest hop is the New York router to what looks like a German router.)

	PayPaul December 08, 2009, 02:54 PM
	I did some troubleshooting of Firefox using it in Safe Mode. To do that you go to Start>Programs>Mozilla>Firefox Safe Mode. When in safe mode you check the box marked "Disable Add-ons" for the next time you restart firefox. When I restarted firefox normally I enable Adblock first. On restart the problem appeared again. So I went into its settings and discovered a bad filter. I disabled that and now all pages load correctly. It's good to know it wasn't JAVA and this may be of some help to those others who may experience this problem in future. I'm going to have to try and upload to here using firefox but I believe Netscape may be the solution for that. Thank you all for your contributions and suggestions.

	PayPaul December 08, 2009, 03:38 PM
	I made a comparison between pinging and doing a traceroute to flickr and 23hq. This time 23 pinged properly. But the speeds of connection are incredibly slow. Why would that be? My uploads to flickr work fine and are at a reasonable speed. Here's the contents of those ping and traceroute requests: Microsoft Windows [Version 6.0.6001] Copyright (c) 2006 Microsoft Corporation. All rights reserved. C:\Users\PaulW>ping www.flickr.com Pinging www.flickr.com [68.142.214.24] with 32 bytes of data: Reply from 68.142.214.24: bytes=32 time=103ms TTL=57 Reply from 68.142.214.24: bytes=32 time=66ms TTL=57 Reply from 68.142.214.24: bytes=32 time=101ms TTL=57 Reply from 68.142.214.24: bytes=32 time=75ms TTL=57 Ping statistics for 68.142.214.24: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 66ms, Maximum = 103ms, Average = 86ms C:\Users\PaulW>tracert www.flickr.com Tracing route to www.flickr.com [68.142.214.24] over a maximum of 30 hops: 1 40 ms 19 ms 18 ms 10.32.160.1 2 20 ms 18 ms 18 ms 130.81.7.221 3 45 ms 39 ms 18 ms 130.81.20.24 4 186 ms 230 ms 67 ms 130.81.19.111 5 177 ms 58 ms 23 ms 130.81.17.177 6 64 ms 135 ms 24 ms 130.81.15.170 7 26 ms 43 ms 110 ms 216.115.102.172 8 189 ms 54 ms 154 ms 216.115.101.145 9 241 ms 64 ms 137 ms 216.115.96.60 10 182 ms 234 ms 86 ms 216.115.102.137 11 206 ms 141 ms 72 ms 216.115.104.107 12 1055 ms 813 ms 965 ms 68.142.209.5 13 75 ms 76 ms 123 ms 68.142.214.24 Trace complete. C:\Users\PaulW>Ping www.23hq.com Ping request could not find host www.23hq.com. Please check the name and try aga in. C:\Users\PaulW>ping www.23hq.com Ping request could not find host www.23hq.com. Please check the name and try aga in. C:\Users\PaulW>ping www.23hq.com Pinging www.23hq.com [77.66.17.58] with 32 bytes of data: Reply from 77.66.17.58: bytes=32 time=237ms TTL=53 Reply from 77.66.17.58: bytes=32 time=105ms TTL=53 Reply from 77.66.17.58: bytes=32 time=378ms TTL=53 Reply from 77.66.17.58: bytes=32 time=110ms TTL=53 Ping statistics for 77.66.17.58: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 105ms, Maximum = 378ms, Average = 207ms C:\Users\PaulW>tracert www.23hq.com Tracing route to www.23hq.com [77.66.17.58] over a maximum of 30 hops: 1 28 ms 18 ms 17 ms 10.32.160.1 2 72 ms 202 ms 226 ms 130.81.7.241 3 150 ms 17 ms 21 ms 130.81.20.26 4 72 ms 133 ms 151 ms 152.63.9.249 5 133 ms 59 ms 18 ms 152.63.20.53 6 25 ms 18 ms 22 ms 157.130.60.14 7 249 ms 162 ms 317 ms 80.91.253.101 8 163 ms 98 ms 258 ms 213.248.64.21 9 * * * Request timed out. 10 165 ms * * 213.248.95.30 11 101 ms 324 ms 97 ms 217.116.255.81 12 * 164 ms * 217.116.255.42 13 128 ms 104 ms 174 ms 77.66.17.58 Trace complete. As you can see the connection speed for flickr is at maximum time frame of 103 ms whereas the maximum time frame for 23 is 378 ms. Any ideas? I seriously doubt it's my router.

	IkoTikashi December 08, 2009, 03:55 PM
	Could it be that 23-servers are located in DK, and flickr-servers in the US?

	PayPaul December 08, 2009, 09:25 PM
	It does have a lot to do with it. If I ping a site in the US or perhaps the UK the speeds are pretty decent. I tried pinging a site in Russia and it was quite dismal. I also noticed that when I'm doing a trace route other sites such as 23, flickr or newegg refuse to load at all. Strangely the russian site I was doing tracert on loaded just fine. Weird.

	Th Clvr Mnky December 09, 2009, 12:15 AM
	Your first few hops to 23 are pretty brutal. Looks like your provider, or their provider (&etc.) routes to W. Europe using a pretty slow link. You can raise this with your ISP. Good ones will listen to you about this stuff. Though in this case you appear to connect with Verizon, who are not known for their ability to move traffic quickly outside of the US.

Please note: Photos posted in this photogroup are visible to all visitors − even if individual photos are marked as private.

Help for 23

23 is showing up as text only?

Discuss 23

Help for 23

About 23

Popular photos right now