Jump to content
SAU Community

Recommended Posts

Haha thats funny as (the register article). I got an email from skylines downunder saying that I had just recieved a PM from some goonie regarding ultimaterally and the usual blah blah. From address was [email protected] which appears to be one of his bullshit domains. I then checked our work server logs for any emails from ultimatereally and kimble.org and found two emails that bounced as he rctp'd to people who didnt exist. The email came from H=(plesk7.trendax.net) [207.218.248.46] which is a linux host runing sendmail. The box is hosting by ez1 or evs1 servers somewhere overseas. The host trendax doesnt exist but trendax.com does and its one of his ventures that went belly up. The servers for the site are in one subnet at ev1servers.net and it looks like the mailhosts are in another subnet at a similar location.

traceroute to plesk6.trendax.com (69.57.154.2), 30 hops max, 40 byte packets

1 FastEthernet6-0.civ-service1.Canberra.telstra.net (203.50.1.65) 0.254 ms 0.175 ms 0.162 ms

2 GigabitEthernet3-0.civ-core2.Canberra.telstra.net (203.50.10.129) 0.846 ms 0.815 ms 0.776 ms

3 GigabitEthernet2-2.dkn-core1.Canberra.telstra.net (203.50.6.126) 0.93 ms 1.021 ms 0.941 ms

4 Pos4-0.ken-core4.Sydney.telstra.net (203.50.6.121) 5.148 ms 5.123 ms 5.035 ms

5 10GigabitEthernet3-0.pad-core4.Sydney.telstra.net (203.50.6.86) 5.189 ms 5.28 ms 4.709 ms

6 GigabitEthernet2-2.syd-core01.Sydney.net.reach.com (203.50.13.38) 5.476 ms 5.319 ms 5.16 ms

7 i-12-2.wil-core01.net.reach.com (202.84.144.25) 153.613 ms 153.555 ms 153.498 ms

8 i-2-0.dal-core01.net.reach.com (202.84.143.66) 185.473 ms 185.175 ms 185.241 ms

9 i-3-1.dal01.net.reach.com (202.84.142.82) 185.718 ms 185.628 ms 185.73 ms

10 * * *

11 dllstx1wcx3-pos13-2-oc48.wcg.net (64.200.105.65) 185.763 ms 185.776 ms 185.741 ms

12 hstntx1wcx3-pos1-0-oc192.wcg.net (64.200.210.66) 190.461 ms 190.41 ms 190.521 ms

13 hstntx1wcx1-pos9-0-oc48.wcg.net (65.77.93.213) 190.718 ms 190.741 ms 190.645 ms

14 hstntx1wce2-everyonesinternet-gige.wcg.net (65.77.93.54) 200.094 ms 200.172 ms 200.288 ms

15 ivhou-207-218-245-27.ev1.net (207.218.245.27) 202.547 ms 202.384 ms 225.868 ms

16 ivhou-207-218-245-113.ev1.net (207.218.245.113) 202.512 ms 202.528 ms 202.483 ms

traceroute to 207.218.248.46 (207.218.248.46), 30 hops max, 40 byte packets

1 FastEthernet6-0.civ-service1.Canberra.telstra.net (203.50.1.65) 0.27 ms 0.177 ms 0.211 ms

2 GigabitEthernet3-0.civ-core2.Canberra.telstra.net (203.50.10.129) 0.856 ms 0.723 ms 0.707 ms

3 GigabitEthernet2-2.dkn-core1.Canberra.telstra.net (203.50.6.126) 1.021 ms 1.011 ms 0.95 ms

4 Pos4-1.ken-core4.Sydney.telstra.net (203.50.6.69) 5.077 ms 5.074 ms 5.005 ms

5 10GigabitEthernet3-0.pad-core4.Sydney.telstra.net (203.50.6.86) 5.281 ms 5.273 ms 5.169 ms

6 GigabitEthernet2-2.syd-core01.Sydney.net.reach.com (203.50.13.38) 5.28 ms 5.312 ms 5.292 ms

7 i-6-1.wil-core02.net.reach.com (202.84.249.201) 153.244 ms 153.384 ms 153.425 ms

8 i-2-0.dal-core01.net.reach.com (202.84.143.66) 185.327 ms 185.315 ms 185.347 ms

9 i-3-1.dal01.net.reach.com (202.84.142.82) 185.677 ms 185.872 ms 185.73 ms

10 * * *

11 dllstx1wcx3-pos13-2-oc48.wcg.net (64.200.105.65) 185.877 ms 185.778 ms 185.822 ms

12 hstntx1wcx3-pos1-0-oc192.wcg.net (64.200.210.66) 319 ms 197.289 ms 190.306 ms

13 hstntx1wcx1-pos9-0-oc48.wcg.net (65.77.93.213) 190.709 ms 190.593 ms 190.756 ms

14 hstntx1wce2-everyonesinternet-gige.wcg.net (65.77.93.54) 200.054 ms 200.207 ms 200.156 ms

15 ivhou-207-218-245-27.ev1.net (207.218.245.27) 202.481 ms 202.191 ms 202.287 ms

16 ivhou-207-218-223-108.ev1.net (207.218.223.108) 215.299 ms 215.346 ms 215.377 ms

17 londes.innohost.com (207.218.248.46) 215.133 ms 216.06 ms 215.229 ms

17 ev1s-69-57-154-2.ev1servers.net (69.57.154.2) 202.675 ms 202.557 ms 202.604 ms

https://plesk7.trendax.com:19638/

brings up a web portal that throws a 500 error

None of the above hosts are in mail-abuse or maps or any of the blacklists including spamcop.

It sounds like he's found a cheap shot way to signup forum users then randomly PM people junk (sau and sdu for starters).

He's just picking random car forums to spam his bullshit rally competition. Are all these PM's coming from the same IP's or a broad range of IP's?

Either way you should post them so others can block them and also send them off to spamcop and other maps if they aren't already in there.

That way if the same hosts are mass mailing junk it will be blocked as well (better than nothing).

  • Replies 106
  • Created
  • Last Reply

Top Posters In This Topic

and his stupid site doesnt even do anything check out http://www.ultimaterally.com/cgi-bin/application

all it does it give you a page saying thank you, it doesn't even do validation or actually use the values. also the secure login page where it asks for user/pass is just a .swf that doesnt actually do anything and it always returns invalid login regardless of what you enter

very dodgy

i dont get the point of it all?

I just got one now from JaquesvD, but strangely enough it was from SDU, not here.

I haven't been back to SDU since Christian ("Prank") opened up this site, but I haven't removed my details from there either. Oh well, I'll go there now to see if there's a similar thread that I can post to...

Strangely enough, I got the email notification of a PM from SDU, and then I got a copy of the email from the d1ckhead himself (through SDU), listed as [email protected]. Furthermore, it lists Kimble's name at the bottom of the email.

Is this how everyone else is getting theirs?

Nick T

  • 2 weeks later...

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

    • I did end up getting it sorted, as GTSBoy said, there was a corroded connection and wire that needed to be replaced. I ended up taking out the light assembly, giving everything a good clean and re-soldered the old joints, and it came out good.
    • Wow, thanks for your help guys 🙏. I really appreciate it. Thanks @Rezz, if i fail finding any new or used, full or partial set of original Stage carpets i will come back to you for sure 😉 Explenation is right there, i just missed it 🤦‍♂️. Thanks for pointing out. @soviet_merlin in the meantime, I received a reply from nengun, and i quote: "Thanks for your message and interest in Nengun. KG4900 is for the full set of floor mats, while KG4911 is only the Driver's Floor Mat. FR, RH means Front Right Hand Side. All the Full Set options are now discontinued. However, the Driver's Floor Mat options are still available according to the latest information available to us. We do not know what the differences would be, but if you only want the one mat, we can certainly see what we can find out for you". Interesting. It seems they still have some "new old stock" that Duncan mentioned 🤔. I wonder if they can provide any photos......And i also just realized that amayama have G4900 sets. I'm tempted too. 
    • 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!
×
×
  • Create New...