Re: Port scanner questions
Quote:
Originally posted here by Phonedog911
1. when i scan my ip or my friend's ip(he knew about it) with -sS it doesnt return anything, but if i use -sT, it finds open ports. why is that? we're both comcast users.
Either your nmap setup is broken in that it can't send /receive raw packets correctly, or you are using some network configuration which is preventing -sS working. I suspect you are a Windows user, therefore I'm going for the former, as this often seems to happen on Winnmap (although when I've installed it following the instructions correctly, I've never had a problem)
Quote:
2. when i scanned my ip it found port 80, 1080, 119, etc. open. my setup is modem---> router---> mycomp, othercomps. why does it think these ports are open? is it showing that my router has these ports open or is it possible that its scanning the gateway im connect thru at my isp?
You scanned your own IP address? Depends via what mechanism. You have a router. If this router does NAT, expect ALL PORT SCANS to FAIL. You could even DoS yourself.
Never scan through a NAT router, it really won't make accurate results.
Bear in mind, that your ISP may have transparent proxying / their own NAT types (transparent proxying involves NAT at some level) - this will interfere with scans that go through that setup. Mine does this for port 80 only, so even an IP address which I know to be unroutable, will still show 80 open.
If you scan through NAT, expect inaccurate results, or trouble. Never scan through a NAT without permission from the NAT router's manager - it may cause problems.
If you know from experience that there is a specific type of NAT that you can avoid, use the scanner options to avoid the NAT - for instance, if you know your ISP transparently proxies TCP port 80, avoid ever scanning that port.
Quote:
3. what exactly happens when u scan a network thats behind a router? does it scan the router or what?
Depends if NAT is involved.
If the router is *JUST* a plain router, then it scans as normal. In a sense, every network is behind a router (unless it's a totally isolated LAN).
If it does NAT, then you typically CANNOT scan the hosts behind the router, because you can't route packets to their IPs, which are in private space.
Quote:
4. when i do an ipconfig, it says this at the top:
Code:
Connection-specific DNS Suffix . : ce1.client2.attbi.com
. what is that and what does it mean?
That's the DNS domain name you're in.
Slarty