zzy wrote: [nmap]
Did you find the nmap documentation already, for example this:
What do you drive on these two ports?
Try to find out what process opens these ports, for example using netstat.
Yours, VB.
You don't need a filtering entity, if you're just not offering network services.
Yours, VB.
It has. Just move to another ISP at a friend and compare the results. This is how you can easily enumerate that AOL is filtering ports
135,137-139,445,583 and 1025 (TCP and UDP where approciate).(The funny thing is about 583/TCP which is MSRPC-over-HTTP, that is disabled in every version of Windows and almost impossible to activate by accident. Even better, there's no RPC exploit worm spreading on this port.)
Then I know about the ISP of the test page hoster what?
Yes. Partly information. And that's it.
Nice. And moving and moving around and using different scanning pages you'll learn much about what's filtered in different regions of the net today, but less about your own box, because there may be even "opened ports" your box doesn't have but a provider is NATing. ;-)
Better do a local scan, I'd say.
Yours, VB.
No, just how broken those scanners or their frontend are. :-)
Hm... and what about your very own router (if applicable)?
You can locally scan your router and your hosts. Of course, if your router has an embedded DSL modem (for example), then this may be difficult to do.
Maybe then it's better to have a friend at the same provider, and do some scanning from his host. Then a minimum of foreign filtering will be in between.
Yours, VB.
Generally there's a big difference between scanning the WAN port with a local address, a WAN address or with a WAN address over a PPPoE connection created by the router.
Yeah, that's another point: What to do if you don't have any second host.
Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.