Announcement

**Skanky Burns** · April 12, 2003, 21:20

Well, I kind of guessed that I would be the only one having problems. They images normally work, but my DSL server have been having network problems for the past few days which has led to things like half the internet being unavailable, and images not showing up on Apolyton.

What I want to know is why the images actually did show up when I went to the forum cache, despite the fact that I am still having network problems.

Speaking of avatars, they all show up fine (except for Gatekeepers).

**Static Universe** · April 12, 2003, 21:58

Originally posted by Gatekeeper
Gee, Skanky, looks like you're alone on this one ... do you hear the crickets chirping?

Gatekeeper

I am having intermittent image problems as well, for about a week or so.

**ixnay** · April 12, 2003, 22:24

I've been having intermittent problems but things seem to be fine now.

**Urban Ranger** · April 13, 2003, 00:17

Originally posted by Skanky Burns
What I want to know is why the images actually did show up when I went to the forum cache, despite the fact that I am still having network problems.

Try flushing the browser's caches and restarting.

**Skanky Burns** · April 13, 2003, 01:31

No, that didn't help. Alas.

Oh, and answering previous questions:
I don't have any zoom feature. My display is 1280x1024, normal size font. I also haven't changed anything on my system in the last week that could have caused this.

**Urban Ranger** · April 13, 2003, 12:03

Try a different browser.

**Gatekeeper** · April 13, 2003, 13:49

Hmm ... that's strange why my avatar wouldn't show up for you, Skanky. It's one of the standard ones that 'Poly offers ... I think it's an F-15 jet fighter. (I haven't seen it in a while, having avatars disabled and all

.)

Gatekeeper

**Panag** · April 13, 2003, 15:05

hi ,

just close all your browser windows , empty cookies , history , open again and that should do it , .....

or just hit "refresh" , ....

have a nice day

**Urban Ranger** · April 14, 2003, 00:50

It's amusing the kind of acrobatics you have to go through to get something simple like a Web browser to work like it is supposed to be. Imagine a car that behave in the same way.

**Skanky Burns** · April 14, 2003, 02:44

Tried both of the above suggestions, they didn't work either.

The properties tab of images that don't work look something like:
"http://64.246.32.176/forums/images/smilies-xmas/uhoh.gif"
whereas pinging apolyton.net shows an IP of 64.246.32.51
I can not ping the IP address that ends with .176
Any ideas?

**MarkG** · April 14, 2003, 04:26

64.246.32.176 is a secondary ip of Settler (our server)
do you have any kind of proxy or anything like that?
can you do a traceroute to 176?

**Skanky Burns** · April 14, 2003, 06:11

Code:

Tracing route to 64.246.32.176 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1 
  2   597 ms   595 ms   788 ms  172.31.17.142 
  3   279 ms   794 ms   403 ms  172.31.50.14 
  4     *        *        *     Request timed out.
  5  1665 ms  1390 ms   609 ms  fa3-0.cor2.syd2.agile.on.net [150.101.197.115] 
  6  1205 ms  1430 ms  1642 ms  fa1-0-4.bdr1.syd2.agile.on.net [150.101.197.105] 
  7  1359 ms  1407 ms  1808 ms  ATM5-1-0-7.ken11.Sydney.telstra.net [139.130.185.145] 
  8  1720 ms  1923 ms  1209 ms  GigabitEthernet10-0.ken-core4.Sydney.telstra.net [203.50.20.1] 
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11  1892 ms  1650 ms  1539 ms  i-13-0.sjc-core01.net.reach.com [202.84.143.17] 
 12   631 ms  1064 ms   685 ms  202.84.143.249 
 13     *        *        *     Request timed out.
 14  1256 ms   838 ms  1480 ms  605.ge13-0.mpr2.pao1.us.mfnx.net [208.185.237.69] 
 15     *        *        *     Request timed out.
 16  1741 ms  1794 ms  1154 ms  so-0-0-0.mpr3.sjc2.us.mfnx.net [64.125.30.1] 
 17  1178 ms  1422 ms  1427 ms  pos2-0.mpr1.dfw2.us.mfnx.net [208.184.232.81] 
 18  1223 ms  1734 ms  1942 ms  so-3-0-0.cr1.dfw2.us.mfnx.net [216.200.127.213] 
 19  1630 ms  2177 ms  1819 ms  so-4-0-0.mpr1.iah1.us.mfnx.net [64.125.31.37] 
 20  1406 ms  1020 ms  1569 ms  216.200.251.53.ev1.com [216.200.251.53] 
 21  1144 ms  1266 ms  1856 ms  207.218.245.37 
 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.

For comparison, here is the tracert to the primary server.

Code:

Tracing route to apolyton.net [64.246.32.51]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.0.1 
  2    31 ms    32 ms    32 ms  172.31.17.142 
  3    34 ms    32 ms    32 ms  172.31.52.14 
  4     *        *        *     Request timed out.
  5    31 ms    34 ms    31 ms  fa3-0.cor2.syd2.agile.on.net [150.101.197.115] 
  6    37 ms    32 ms    34 ms  fa1-0-4.bdr1.syd2.agile.on.net [150.101.197.105] 
  7   125 ms   141 ms   138 ms  ATM5-1-0-7.ken11.Sydney.telstra.net [139.130.185.145] 
  8   155 ms   176 ms   159 ms  GigabitEthernet10-0.ken-core4.Sydney.telstra.net [203.50.20.1] 
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11   233 ms   227 ms   225 ms  i-13-0.sjc-core01.net.reach.com [202.84.143.17] 
 12   236 ms   224 ms   220 ms  202.84.143.249 
 13     *        *        *     Request timed out.
 14   251 ms   236 ms   235 ms  605.ge13-0.mpr2.pao1.us.mfnx.net [208.185.237.69] 
 15   247 ms   246 ms   247 ms  pos2-0.mpr1.pao1.us.mfnx.net [208.184.232.181] 
 16   253 ms   219 ms   226 ms  so-6-3-0.mpr3.sjc2.us.mfnx.net [208.184.233.141] 
 17   276 ms   266 ms   264 ms  pos2-0.mpr1.dfw2.us.mfnx.net [208.184.232.81] 
 18   259 ms   277 ms   266 ms  so-3-0-0.cr1.dfw2.us.mfnx.net [216.200.127.213] 
 19   271 ms   266 ms   275 ms  so-4-0-0.mpr1.iah1.us.mfnx.net [64.125.31.37] 
 20   252 ms   249 ms   312 ms  216.200.251.53.ev1.com [216.200.251.53] 
 21   257 ms   262 ms   253 ms  207.218.245.37 
 22   336 ms   269 ms   298 ms  settler.apolyton.net [64.246.32.51]

**MarkG** · April 14, 2003, 06:21

interesting
i cant figure out why it would stop at that point only for you....

i'll do some checking....

**Skanky Burns** · April 14, 2003, 06:38

No proxy or such. My router is a DSL-504 which I also use to connect to the internet.
I have made no changes to it or my computer between last week (when it was working fine) and this week.

I think the problem lies somewhere between myself and the 'Poly servers, but it is strange that one I can see fine, the other doesn't exist to me.

One quick note about the difference in seek times: I did those two tracerts at different times. Doing a fresh tracert to both servers gives near identical seek times. I still can't get to the secondary server.

**Frozzy** · April 14, 2003, 15:35

If it means anything, a server between Poly and I was unresponsive from March 10th to April 12th. Only at certain times could I get an extremely lethargic connection to IP: 64.246.32.176

If it's related then...

Announcement

Broken Images on Apolyton

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment