Re: Firewall rule closed ALL but Port UDP 137 open
From: Tutaepaki (replyto@newsgroup.not.me)Date: 10/30/02
- Next message: Mike: "Re: What if..."
- Previous message: : "Re: can a hacker do this?"
- In reply to: Markus Dubois: "Firewall rule closed ALL but Port UDP 137 open"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Tutaepaki" <replyto@newsgroup.not.me> Date: Thu, 31 Oct 2002 09:01:54 +1300
"Markus Dubois" <Markus.Dubois@gmx.ch> wrote in message
news:186d15f6.0210300045.77aeba03@posting.google.com...
> Hi,
>
> on my home internet PC (Win98 Shared internet access, firewalled with
> Norton Internet Security 2002) a nmap scan shows port udp 137 open.
> Even if i make a rule on top with
> block all any any
>
> Very odd situation. There is nothing open according to my
> firewall-rule but nmap shows this open port......
>
> Why?
>
> Regards
>
> Markus
NMAP, and other port scanners don't do a very good job of scanning UDP
ports. UDP is stateless, therefore there is no response you can rely on to
indicate that the port is open. If you've set up your firewall to simply
drop
packets without sending a response, most port scaners will report the port
as open.
- Next message: Mike: "Re: What if..."
- Previous message: : "Re: can a hacker do this?"
- In reply to: Markus Dubois: "Firewall rule closed ALL but Port UDP 137 open"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
