|
-
July 3rd, 2003, 06:15 AM
#16
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.
...This Space For Rent.
-[WebCarnage]
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|