IP Address & spoofing issues (Academic purpose)

[neel]

lmao, that's funny
I didn't read the first sentence or something... I missed that part you quoted

I'm with you on the english really, but I also learned to live with the fact not everyone speaks english 100% correctly (I make 1000 mistakes a day)... But it's like in the netherlands you have to learn 4 languages at least. Not all people have to learn any other language as their first. I could read his reply and altough everyone knows (himself included) it's not nearly perfect english, it is understandible...

[techdan]

neel,

I'm with HTRegz. This isn't a case of someone making a few mistakes. It's blatant, sloppy, intentional misuse of English.

ommy correct English

... either use a period or comma
wot what
i m "I'm" or "I am"
chattin chatting
thinkin thinking
thank u thank you
ma my

[ommy]

Well, Yes, Thank you all. Netstat -n stuff does work. i just tried it. I will try to be more clear and use gramatically correct english.
Thank you,
Ommy.

[barfly]

can i aaskkk el-hal f ??where did you learn to do that is that from when i went to high school and computers were in a DoS environment??am i true thati wished i stayed in school and messed w/ pc's to know that way you k now??HeLpp im a dropout that would like to go back in time

[crashburn181]

your getting off subject with the grammer thing

[[WebCarnage]]

ommy:

You're at quite a situation with this one. You couldn't send custom packets to the person your talking to in order to find out their ip address. Becuase you'd have to send the custom packets to a destination source, and that, would obviously be their IP to begin with.

And as for sending files and pulling up netstat. Its better if you do a "C:\netstat -n" before the file transfer, then send the person you're chatting to a file, then "C:\netstat -n" again - and compare. On the second netstat -n there should be an extra IP address, that IP address would be the one of the person you're talking too.

Now the reason you must send them a file, and not just "C:\netstat -n" to begin with, is this:

normally, this is how chat via MSN Messenger works.

You ---> MSN Server ---> Victim.

If you "C:\netstat -n" you will get the IP (and ports connected) of the MSN Server, not the victim. You establish a connection with the victim directly once you setup a file transfer, so it'll look something like this:

You --> Victim

... now you can "C:\netstat -n" and get their IP...



Hope it helped.