Author: Canglangke / Pacific Network Institute
Do you really need to go through this much trouble to check a QQ friend's IP address? Wouldn't it be enough to just patch QQ? True, that is very simple, but what if it's a newly released QQ and the "patch" hasn't been made yet? Then use software like IpSniper. But what if you don't have it on hand and urgently need to check it? You could use other software, for example... alright, no matter how you put it, it's still somebody else's software. So why not try DOS commands? It's simple, convenient, and very environmentally friendly (unlike application software, which has to be installed separately and take up hard disk space, and also uses up the same resources when running).
Enough talk, let's officially begin. First, use sweet talk, sugar-coated shells, or similar weapons to "invite" the person whose IP address you want to know into QQ's "two-person world." Next, open a 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 exit the "two-person world," then enter this once again 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 results? Still don't see it? Look carefully, and you will notice:
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
Alright, now you should know, right? That's right! The IP of the person chatting with you is: 202.101.139.35! So how do we know that? Friends, when you're in the "two-person world" sending messages, a connection must naturally be created between the two sides (through the UDP protocol), so at that time it is naturally "ESTABLISHED" (judging from your netstat -n result); and after exiting the "two-person world," the connection is broken, so naturally it becomes "TIME_WAIT."
Pretty simple, right? This method doesn't use a single external piece of software (netstat is a Windows-built-in external command). Isn't it just as simple, convenient, and environmentally friendly as we said earlier? Why not try it now!
-------------Personal signature---------------
Casting flirtatious glances in secret means the dark night delivers you autumn spinach.
------------------------------------
==============
KO says:
Actually this article doesn't have much to do with DOS, hehe...
It just uses a DOS command. (Even so, it's a Windows DOS command, not a pure DOS command...) And it's also run in a Windows environment.
It would be better to say it's checking QQ IP numbers in a "command-line" way...
Do you really need to go through this much trouble to check a QQ friend's IP address? Wouldn't it be enough to just patch QQ? True, that is very simple, but what if it's a newly released QQ and the "patch" hasn't been made yet? Then use software like IpSniper. But what if you don't have it on hand and urgently need to check it? You could use other software, for example... alright, no matter how you put it, it's still somebody else's software. So why not try DOS commands? It's simple, convenient, and very environmentally friendly (unlike application software, which has to be installed separately and take up hard disk space, and also uses up the same resources when running).
Enough talk, let's officially begin. First, use sweet talk, sugar-coated shells, or similar weapons to "invite" the person whose IP address you want to know into QQ's "two-person world." Next, open a 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 exit the "two-person world," then enter this once again 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 results? Still don't see it? Look carefully, and you will notice:
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
Alright, now you should know, right? That's right! The IP of the person chatting with you is: 202.101.139.35! So how do we know that? Friends, when you're in the "two-person world" sending messages, a connection must naturally be created between the two sides (through the UDP protocol), so at that time it is naturally "ESTABLISHED" (judging from your netstat -n result); and after exiting the "two-person world," the connection is broken, so naturally it becomes "TIME_WAIT."
Pretty simple, right? This method doesn't use a single external piece of software (netstat is a Windows-built-in external command). Isn't it just as simple, convenient, and environmentally friendly as we said earlier? Why not try it now!
-------------Personal signature---------------
Casting flirtatious glances in secret means the dark night delivers you autumn spinach.
------------------------------------
==============
KO says:
Actually this article doesn't have much to do with DOS, hehe...
It just uses a DOS command. (Even so, it's a Windows DOS command, not a pure DOS command...) And it's also run in a Windows environment.
It would be better to say it's checking QQ IP numbers in a "command-line" way...
ko20010214
=================================
大功告成,打个Kiss!
ko20010214@MSN.com
神州优雅Q300C
Intel CeleronM 370处理器 | 256MbDDR内存
40G硬盘 | USB2.0 | IEEE 1394
13.3 ' WXGA 宽屏(16:10) | COMBO光驱
10/100M网卡 | 四合一读卡器
=================================
大功告成,打个Kiss!
ko20010214@MSN.com
神州优雅Q300C
Intel CeleronM 370处理器 | 256MbDDR内存
40G硬盘 | USB2.0 | IEEE 1394
13.3 ' WXGA 宽屏(16:10) | COMBO光驱
10/100M网卡 | 四合一读卡器



