How to find where (on earth) an I.P is!

There are several ways to locate the area an I.p. adress is in.
The most usefull way is to use a program.
The best programs are shareware and are here:
Neotrace (no link)
Visualroute www.visualroute.com
they will track it down to the city.

you can also do this in your computer in ms-dos mode (and slightly modified for linux)
tracert iphere
it will give you a list of "hops" or locations
THESE ARE THE SERVERS YOUR CONNECTION PASSES THROUGH!
using these urls+ips you can see what isp they use, and then maybe establish a closer location than a city maybe even to an area code or a zip code.

I hope you've enjoyed this short tutorial. If you have any questions please reply and I will try to answer them.

Funny you forgot to mention that you can only trace the IP back to the city the ISP is located in, NOT there house or real city. This leads me to question if you actually know what your talking about. But anyway... Thanks for contributing to the site.

tracing it back to an adress requires more effort, this is just a simple solution. Tracing it back to the house would require logs, calls to isps, etc. etc. with the isp you can get them to reveal the adress if your that concerned

http://neotrace.com/

Link for Neotrace....Kinda makes one wonder how much effort you put into this.

Yes it does make me wonder how much time you spent in to this as well. Btw, ISP's won't give you **** if you ask them to give you personal info about people like that. Only if you are government officials in most cases.

:)
Hey nice work. Just needs some refining and a bit more background research.
Nice to see you are showing some interest in networking. It takes time to learn,
I know, but don't get discouraged; all those post-pubescent types had more time than you to work it out and now think they can dump on you. And your spelling is not too shabby either.
Just keep learning and your posts will improve. Which means, that the content will be scrutinized even more, off course...

Go big...

Quote:

---

THESE ARE THE SERVERS YOUR CONNECTION PASSES THROUGH!

---

Not necessarily... most of the time they are routers.

Don't know if you'd consider them servers?
They are serving for a routing purpose... but in the networking sense... they are routers.

More specifically... they are normally backbone routers... not the linksys crap that you find at home.

The Duck brings up a very good point. Trace my ip and it'll tell you that I'm located in philly... when in fact I'm at least a good 45 miles from it physically.

As for time spent... I'd say less than 15 minutes...

There is much more information that *could* have been presented.

But... for a first try... you did ok. The concept is right, just needs more info.

Quote:

---

Originally posted here by phishphreek80
Not necessarily... most of the time they are routers.

Don't know if you'd consider them servers?
They are serving for a routing purpose... but in the networking sense... they are routers.

More specifically... they are normally backbone routers... not the linksys crap that you find at home.

---

I find it funny that we now have to distinguish. When I hear the word router I immediately think of Cisco, Nortel, etc.... it scares me that some people here router and think linksys or dlink.... they're crap... and a new term should be devised for them.

Quote:

---

As for time spent... I'd say less than 15 minutes...

There is much more information that *could* have been presented.

But... for a first try... you did ok. The concept is right, just needs more info.

---

less than 15 minutes? I'm going with less than 5.... I could get more information from the VR or NeoTrace readme's not to mention their websites, FAQs and help files.

Peace,
HT

Quote:

---

Btw, ISP's won't give you **** if you ask them to give you personal info about people like that.

---

TheDuck make's a strong point here, you can't trace back to an ISP and ask "Where does he live?". They're not obliged to give out that sort of personal information to someone seeking to trace an attacker or whatnot. They'll just take the IP you gave them and give them a violation of the TOS (Term's of Service). That's about as far as you'll get to knowing the person's phone number or address.

Quote:

---

I'm going with less than 5

---

'Nuff said, really. I don't think much effort was put into this and it's information was misleading as well as incorrect. But hey, who am I to talk about tutorial's :D

No one's mentioned this yet, but should this even be in a tutorial forum? Not to hurt unit321's feelings, but that was kinda a crappy tutorial. It was *ok* for a first attempt, but really, newbies shouldn't just join the site and start posting tutorials. I know a lot of people who's first attempt at a tutorial was way better.
And just so I offer some constructive criticism in this post, there's a ton of stuff that could be said about whois, rwhois, nbtstat, and other such VERY useful tools for turning an IP into a location.

EDIT:

Quote:

---

all those post-pubescent types had more time than you to work it out and now think they can dump on you

---

Exactly, we have had more time than him to figure out this stuff, which is why we're offering constructive criticism. The criticism might seem a bit harsh at first, but it will help him in the long run. And in case you didn't notice, you're the only one who hasn't added anything to this thread :).

Cheers,
cgkanchi

Am I going crazy or did I write a tutorial on tracing IP's about 2 month's ago? unit321, You should really search around to see if anyone recently posted any tutorials on the same relative subject as you.

Quote:

---

Originally posted here by The Duck
Am I going crazy or did I write a tutorial on tracing IP's about 2 month's ago? unit321, You should really search around to see if anyone recently posted any tutorials on the same relative subject as you.

---

This subject was disccused a year ago. There is nothing wrong with multiple tutorials on the same subject. If the tutorials are good, and understandable, then there should be NO limit to them. Tutorials are the exception. We already have a ton of firewall tutorials, but ive been writing one for the last month, and i will publish it on here, even though there are other tutorials on that subject. Tutorials should be seen as books. You dont just read one book on a subject, you read as many as you can!

Cheers.

Sorry. I don't think this is a tutorial. If someone wants to argue the point, please go ahead.

On the bright side he didn't say:-

"This is for noobs"
"Sorry about the spelling/grammar"
"There's more to come", (before the end of a whole page).

;)

Quote:

---

Originally posted by HTRegz
When I hear the word router I immediately think of Cisco, Nortel, etc.... it scares me that some people here router and think linksys or dlink.... they're crap... and a new term should be devised for them.

---

If I think Linksys these days, I automatically think of Cisco (Linksys is a division of Cisco). That doesn't necessarely mean that when I think of Cisco, I also think of Linksys, but in my case it's the truth (that Cisco logo is staring at me all day long). When I hear the word router, I immediately think of Cisco, and therefore of Linksys. Don't diss my thinking, HT :D

Quote:

---

Originally posted here by Tedob1
try going here:

http://www.blackcode.com/net-tools/index.php

they run a tracert using a server side script.

---