Jump to content
SAU Community

Recommended Posts

I can't do the tracert's here at work for security reasons but I can tell you that its no faster at work (using a completely different ISP) than at home.

I'll do a few tracerts tonight and let you know.

Maybe it is the Internode servers? But why is everything else quicker?

Strange one this one.

  • Replies 56
  • Created
  • Last Reply

Top Posters In This Topic

it took 20+ seconds for this reply to load lol..

C:\>tracert www.skylinesaustralia.com

Tracing route to www.skylinesaustralia.com [209.62.28.18]

over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms my router [10.0.0.1]

2 116 ms 69 ms 69 ms loop0.lns2.bne1.internode.on.net [150.101.180.194]

3 69 ms 69 ms 69 ms gi0-3.cor2.bne1.internode.on.net [150.101.180.115]

4 266 ms 265 ms 265 ms pos4-2.bdr1.syd6.internode.on.net [203.16.212.13]

5 266 ms 265 ms 266 ms pos4-0.bdr1.lax1.internode.on.net [203.16.213.189]

6 344 ms 435 ms 475 ms ge-7-11.car3.LosAngeles1.Level3.net [4.71.32.61]

7 301 ms 302 ms 301 ms ae-1-53.edge3.LosAngeles1.Level3.net [4.68.102.84]

8 299 ms 298 ms 299 ms savvis-level3-10ge.LosAngeles1.Level3.net [4.68.110.94]

9 * 268 ms 348 ms cr1-pos-0-3-5-0-losangeles.savvis.net [208.172.44.105]

10 299 ms 299 ms 300 ms dcr2-so-3-3-0.dallas.savvis.net [204.70.192.246]

11 329 ms 327 ms 328 ms cr2-tengige0-7-5-0.dallas.savvis.net [204.70.196.29]

12 307 ms 307 ms 308 ms 208.172.139.134

13 344 ms 344 ms 337 ms gphou2-209-85-0-105.ev1servers.net [209.85.0.105]

14 333 ms 333 ms 333 ms www.skylinesaustralia.com [209.62.28.18]

Trace complete.

C:\Documents and Settings\Jonathan>

ok, and to www.disney.com :

C:\>tracert www.disney.com

Tracing route to disney.com [199.181.132.250]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms my router [10.0.0.1]

2 70 ms 70 ms 69 ms loop0.lns2.bne1.internode.on.net [150.101.180.194]

3 70 ms 69 ms 69 ms gi0-3.cor2.bne1.internode.on.net [150.101.180.115]

4 299 ms 299 ms 298 ms pos2-0.bdr1.syd6.internode.on.net [150.101.180.237]

5 266 ms 266 ms 265 ms pos4-0.bdr1.lax1.internode.on.net [203.16.213.189]

6 268 ms 268 ms 268 ms sl-st20-la-8-0-0.sprintlink.net [144.223.44.9]

7 264 ms 263 ms 264 ms sl-bb21-ana-13-0.sprintlink.net [144.232.20.66]

8 299 ms 298 ms 299 ms sl-bb23-ana-13-0.sprintlink.net [144.232.1.186]

9 277 ms 278 ms 277 ms sl-bb25-sj-9-0.sprintlink.net [144.232.20.159]

10 304 ms 304 ms 304 ms sl-bb22-sj-12-0.sprintlink.net [144.232.3.209]

11 322 ms 322 ms 322 ms sl-bb23-tac-14-0.sprintlink.net [144.232.20.9]

12 296 ms 295 ms 295 ms sl-bb22-tac-9-0.sprintlink.net [144.232.17.181]

13 300 ms 299 ms 299 ms sl-bb20-sea-0-0.sprintlink.net [144.232.9.150]

14 301 ms 299 ms 300 ms sl-gw11-sea-7-0.sprintlink.net [144.232.6.126]

15 327 ms 327 ms 325 ms sl-disne-3-0.sprintlink.net [144.232.219.254]

16 * * * Request timed out.

17 * * * Request timed out.

18 301 ms 301 ms 301 ms www.disney.com [199.181.132.250]

Trace complete.

hmmm...Where it jumps up to 250+ seems to be where it hits international.... So that response is probably ok.... except where it timesout at the end of disney.com

Only thing i could think of which could cause it on your end would maybe be the MTU settings, have you tried changing them?

ATM, we're hosting with EV1/theplanet, who are supposed to have one of the biggest backbones in the US, but it'll still be a tad delayed as the server's running at max load and because of the number of hops.

we as in SAU? Cause we're far from max load.

it's definitely not universal cause the site loads quite fast for me. using verizon at work and swiftel at home. even though my work connection is approx 10 times faster than home the load time of pages is not that much different unless they have lots of images.

we as in SAU? Cause we're far from max load.

hmm... wierd, we're not atm, but when I was logged in just before posting I could've sworn the load average was sitting on 3.4 or thereabouts. atho I could've misread that.

hmm... wierd, we're not atm, but when I was logged in just before posting I could've sworn the load average was sitting on 3.4 or thereabouts. atho I could've misread that.

Yeah it'll get up there occasionally when a cron or rsync is running (SAU is backed up daily to my local machine) but 3.4 is ok when you consider the CPU power available. Also MySQL uses a LOT of memory atm because I was very generous in the my.cnf.

Here is mine for you all, rarely have a drama for me.

1 2 ms 2 ms 1 ms *.*.*.*

2 21 ms 22 ms 21 ms [*.*.*.*]

3 34 ms 22 ms 21 ms gi1-2.mel-pipe-bdr1.ii.net [203.215.6.22]

4 35 ms 35 ms 57 ms gi0-15-1-3.syd-ult-core1.ii.net [203.215.20.12]

5 35 ms 35 ms 85 ms 202.139.19.33

6 192 ms 192 ms 198 ms 203.208.192.201

7 192 ms 192 ms 193 ms g11-0.core01.lax04.atlas.cogentco.com [154.54.12.221]

8 192 ms 205 ms 215 ms p0-0.core01.lax01.atlas.cogentco.com [154.54.6.241]

9 244 ms 191 ms 190 ms t3-1.mpd01.lax01.atlas.cogentco.com [154.54.2.102]

10 224 ms 224 ms 224 ms t2-2.mpd01.iah01.atlas.cogentco.com [154.54.3.37]

11 224 ms 230 ms 223 ms g2-0-0.core01.iah01.atlas.cogentco.com [154.54.2.241]

12 225 ms 240 ms 224 ms v3527.na22.b015619-0.iah01.atlas.cogentco.com [66.28.65.106]

13 224 ms 224 ms 224 ms everyones-internet.demarc.cogentco.com [38.99.215.154]

14 247 ms 225 ms 227 ms gphou2-209-85-0-105.ev1servers.net [209.85.0.105]

15 241 ms 224 ms 225 ms ev1s-209-62-28-18.ev1servers.net [209.62.28.18]

Trace complete.

Hi Christian,

Thank you for your support request with Internode.

Unfortunately a traceroute will not show very good results on the Internode network due to the way our MPLS network works. As such you need to run an extended ping test to the destination to determine latency issues.

Traceroute is only for determining the routing that packets take.

There is more information about our MPLS network available at the link below, however this is only viewable on an Internode connection.

http://www.internode.on.net/faq/internode-...-traceroute.php

Below is a ping from our servers which indicates a standard ping time of about 220ms, which is standard for connections to America.

> ping skylinesaustralia.com

PING skylinesaustralia.com (209.62.28.18): 56 data bytes

64 bytes from 209.62.28.18: icmp_seq=0 ttl=51 time=219.316 ms ...

64 bytes from 209.62.28.18: icmp_seq=74 ttl=51 time=219.219 ms

64 bytes from 209.62.28.18: icmp_seq=75 ttl=51 time=219.300 ms

64 bytes from 209.62.28.18: icmp_seq=76 ttl=51 time=217.861 ms ^C

--- skylinesaustralia.com ping statistics ---

77 packets transmitted, 77 packets received, 0% packet loss round-trip min/avg/max/stddev = 217.723/218.718/219.757/0.639 ms

I can browse the site fine, and do not notice any particularly bad connections. Should there still be issues, we would need more detail regarding the Internode customers that are having an issue before we can do any more troubleshooting.

If you have any further queries, please don't hesitate to contact us in the Helpdesk on 1300 788 233.

Kind regards,

  • 2 weeks later...

There would have been a few IPS driver errors towards the end of last week and over the weekend, but there shouldnt have been any this week. If there have been, can you tell me at approx what times?

As for the slowness, I am going to look into our DNS, but apart from that, I dont think there is anything I can do.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • Any update on this one? did you manage to get it fixed?    i'm having the same issue with my r34 and i believe its to do with the smart entry (keyless) control module but cant be sure without forking out to get a replacement  
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if something was binding the shaft from rotating properly. I got absolutely no voltage reading out of the sensor no matter how fast I turned the shaft. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if shttps://imgur.com/6TQCG3xomething was binding the shaft from rotating properly. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • perhaps i should have mentioned, I plugged the unit in before i handed over to the electronics repair shop to see what damaged had been caused and the unit worked (ac controls, rear demister etc) bar the lights behind the lcd. i would assume that the diode was only to control lighting and didnt harm anything else i got the unit back from the electronics repair shop and all is well (to a point). The lights are back on and ac controls are working. im still paranoid as i beleive the repairer just put in any zener diode he could find and admitted asking chatgpt if its compatible   i do however have another issue... sometimes when i turn the ignition on, the climate control unit now goes through a diagnostics procedure which normally occurs when you disconnect and reconnect but this may be due to the below   to top everything off, and feel free to shoot me as im just about to do it myself anyway, while i was checking the newly repaired board by plugging in the climate control unit bare without the housing, i believe i may have shorted it on the headunit surround. Climate control unit still works but now the keyless entry doesnt work along with the dome light not turning on when you open the door. to add to this tricky situation, when you start the car and remove the key ( i have a turbo timer so car remains on) the keyless entry works. the dome light also works when you switch to the on position. fuses were checked and all ok ive deduced that the short somehow has messed with the smart entry control module as that is what controls the keyless entry and dome light on door opening   you guys wouldnt happen to have any experience with that topic lmao... im only laughing as its all i can do right now my self diagnosed adhd always gets me in a situation as i have no patience and want to get everything done in shortest amount of time as possible often ignoring crucial steps such as disconnecting battery when stuffing around with electronics or even placing a simple rag over the metallic headunit surround when placing a live pcb board on top of it   FML
    • Bit of a pity we don't have good images of the back/front of the PCB ~ that said, I found a YT vid of a teardown to replace dicky clock switches, and got enough of a glimpse to realize this PCB is the front-end to a connected to what I'll call PCBA, and as such this is all digital on this PCB..ergo, battery voltage probably doesn't make an appearance here ; that is, I'd expect them to do something on PCBA wrt power conditioning for the adjustment/display/switch PCB.... ....given what's transpired..ie; some permutation of 12vdc on a 5vdc with or without correct polarity...would explain why the zener said "no" and exploded. The transistor Q5 (M33) is likely to be a digital switching transistor...that is, package has builtin bias resistors to ensure it saturates as soon as base threshold voltage is reached (minimal rise/fall time)....and wrt the question 'what else could've fried?' ....well, I know there's an MCU on this board (display, I/O at a guess), and you hope they isolated it from this scenario...I got my crayons out, it looks a bit like this...   ...not a lot to see, or rather, everything you'd like to see disappears down a via to the other side...base drive for the transistor comes from somewhere else, what this transistor is switching is somewhere else...but the zener circuit is exclusive to all this ~ it's providing a set voltage (current limited by the 1K3 resistor R19)...and disappears somewhere else down the via I marked V out ; if the errant voltage 'jumped' the diode in the millisecond before it exploded, whatever that V out via feeds may have seen a spike... ....I'll just imagine that Q5 was switched off at the time, thus no damage should've been done....but whatever that zener feeds has to be checked... HTH
×
×
  • Create New...