IIS 5 & IIS 6
Checking for open ports...
Last post Jul 02, 2009 04:00 PM by JohnnyW
Jul 02, 2009 12:07 PM|JohnnyW|LINK
I really hope someone here can help me, I'm trying to harden the security on a server used as a website, but I'm finding it hard to get straight answers :(
I've downloaded two IP scanners: NMAP (which I believe is supposed to be very good) and Angry IP Scanner (an open source scanner).
Even though I use Remote Desktop to administer our server, NMAP is saying that port 3389 is "filtered" instead of open? But if I run a scan using AngryIPScanner, it shows it as open...?
So with NMAP it says the following three ports are open:
21, 80, 2301
With AngryIP is says that the following four ports are open:
21, 80, 2301, 3389
As far as I'm concerned, AngryIP is correct... We DO have those four ports open to my IP address.
When I use a VPN to change my IP address and see what ports are open to others I get these results:
21, 80, 2301 - confusing! Exactly the same as before!
80 - correct! Or at least this is what it SHOULD be.
What's going on? Is NMAP a load of crap or am I configuring it incorrectly (hopefully a much more likely explanation).
Here are the arguments I'm passing it:
nmap -p 20,21,3389,2301,80,443,4500,110,8080,500 -v -PN 184.108.40.206
I hope someone can help!
Jul 02, 2009 03:25 PM|Rovastar|LINK
3389 is the default port for remote desktop. If you connect to your server via this you will need this.
I don't know the differences between all the port scanners you should ask on the relevant websites/forums for those products. AFAIK nmap does a good job.
Jul 02, 2009 04:00 PM|JohnnyW|LINK
I agree that Nmap is renowned for "doing the job", but should that port be open or closed considering I CAN connect to Remote Desktop over it?
Thanks for any help.