China DOS Union

Do you really have to go through this much trouble to check a QQ friend's IP address? Wouldn't it be enough just to patch QQ? True, that's very simple, but what if it's a newly released QQ version and the "patch" hasn't been made yet? Then use software like IpSniper. But what if you don't have it on hand and you urgently need to check it? You could use other software, for example... all right, after all that, it still comes down to using somebody else's software, so why not try DOS commands instead? It's simple, convenient, and very environmentally friendly (unlike application software, which has to be installed separately and takes up hard disk space, and also uses the same resources when running).

　　Enough chatter, let's begin. First, use sweet talk, sugar-coated shells, and similar weapons to "invite" the person whose IP address you want to know into QQ's "two-person world." Next, in the DOS window (under Win9x it's called DOS; under Win2000 it's called the command prompt), enter the following command:

　　netstat -n

　　You will see:

　　Active Connections
　　Proto 　　Local Address 　　Foreign Address 　　　State
　　TCP 　202.109.34.78:1200 　202.121.139.35:61555 　ESTABLISHED
　　TCP 　202.109.34.78:2694 　202.109.72.40:6667 　　ESTABLISHED
　　TCP 　202.109.34.78:4869 　211.202.1.227:23 　　　ESTABLISHED

　　Good grief, so many IPs! Which one is the one we're looking for? Don't worry, keep reading. Now we exit the "two-person world," then enter this once more under DOS:

　　netstat -n

　　You will see:

　　Active Connections
　　Proto 　　Local Address 　　　Foreign Address 　　　State
　　TCP 　　202.109.34.78:1200 　202.121.139.35:61555 　TIME_WAIT
　　TCP 　　202.109.34.78:2694 　202.109.72.40:6667 　　ESTABLISHED
　　TCP 　　202.109.34.78:4869 　211.202.1.227:23 　　　ESTABLISHED

　　Can you see the difference between the two times? No? Look carefully and you'll find:

　　Originally: TCP 202.109.34.78:1200 202.121.139.35:61555 ESTABLISHED
　　Now: TCP 202.109.34.78:1200 202.121.139.35:61555 TIME_WAIT

　　All right, now you should know, right? That's right! The IP of the person chatting with you is: 202.101.139.35! But how do we know that? My friend, when you are in the "two-person world" and sending messages, a connection must naturally be created between the two of you (through the UDP protocol), so at that time it is naturally "ESTABLISHED" (judging by the result of your netstat -n command); after exiting the "two-person world," the connection is broken, so naturally it becomes "TIME_WAIT."

　　Very simple, right? This method doesn't use a single external program (netstat is an external command included with Windows). Isn't it just as simple and convenient, and also environmentally friendly, as I said earlier? Why not give it a try!

Excerpted from Pacific Network

What do you want to check someone else's IP for? Surely you're not planning to ~~~~~~~~?

Nothing really. If you're an expert, of course you should know it.