I know block checkers wont worked, but ...... - Printable Version -Shoutbox (https://shoutbox.menthix.net) +-- Forum: MsgHelp Archive (/forumdisplay.php?fid=58) +--- Forum: Skype & Technology (/forumdisplay.php?fid=9) +---- Forum: Skype & Live Messenger (/forumdisplay.php?fid=10) +----- Thread: I know block checkers wont worked, but ...... (/showthread.php?tid=35212) I know block checkers wont worked, but ...... by saintgtril on 12-04-2004 at 06:03 AM
Hi guys, RE: I know block checkers wont worked, but ...... by Mnjul on 12-04-2004 at 06:08 AM
You need to google for a port scanner, but this may not work as: RE: I know block checkers wont worked, but ...... by leito on 12-04-2004 at 06:21 AM Maybe you could buy "Hacking for Dummies April 2004" I'm reading it right now, and talks about port scanning, and as Mnjul said, it won't work on many many cases, because many of us are behind a router, or a DSL NAT. (In which my IP address is not public) RE: I know block checkers wont worked, but ...... by RaceProUK on 12-05-2004 at 03:44 PM
quote:This won't work, and I'll tell you why: 1863 is the server port. In a bit more detail: When a client makes a connection to the server, the OS hands it a random port above 1023. The client uses this random port to initiate a connection to the remote server on 1863. I just did a 'netstat -o' on the command line, and Messenger is using two local ports: 1827 and 3609. 1827 is the Messenger connection, and 3609 is an HTTP connection. Port numbers are defined for incoming connections only, hence the name given to the first 1024 ports: the service range. Port 1024 up is the client range. As with all computery things, counting starts from zero. |