Re: Firewall rule closed ALL but Port UDP 137 open
From: Tracker (TheTrackers000REMOVE@yahoo.com)Date: 10/30/02
- Next message: Mike: "What if..."
- Previous message: 999: "Re: Browser security"
- In reply to: : "Re: Firewall rule closed ALL but Port UDP 137 open"
- Next in thread: : "Re: Firewall rule closed ALL but Port UDP 137 open"
- Reply: : "Re: Firewall rule closed ALL but Port UDP 137 open"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Tracker <TheTrackers000REMOVE@yahoo.com> Date: Wed, 30 Oct 2002 04:26:49 +0300
NeoSadist wrote:
> "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
>
> Uh, if you're scanning YOURSELF, it will probably show that open because you
> have norton antivirus using that port as a sort of email proxy with which to
> scan inbound emails. It's normal. If an internet-based scan shows it open,
> that's different.
> Uh, oops, that's netbios over tcp/ip. You're sharing the internet, so it's
> gonna look open.
Norton anti-virus has nothing to do with open Port 137 for file and print
sharing, nor does an email proxy run on port 137.
Sounds fishy to me.
Tracker
- Next message: Mike: "What if..."
- Previous message: 999: "Re: Browser security"
- In reply to: : "Re: Firewall rule closed ALL but Port UDP 137 open"
- Next in thread: : "Re: Firewall rule closed ALL but Port UDP 137 open"
- Reply: : "Re: Firewall rule closed ALL but Port UDP 137 open"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|