Re: windows messenger spam
From: Michael Bednarek (mb@tgm.com.au)
Date: 11/05/02
- Next message: Karl Levinson [x y] mvp: "Re: Logon Password Problem."
- Previous message: Karl Levinson [x y] mvp: "Re: scheduled task logon failure"
- In reply to: Torgeir Bakken (MVP): "Re: windows messenger spam"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: mb@tgm.com.au (Michael Bednarek) Date: 4 Nov 2002 17:06:48 -0800
"Torgeir Bakken (MVP)" <Torgeir.Bakken-spam@hydro.com> wrote in message news:<3DBFAF01.6421B719@hydro.com>...
> Adam wrote:
>
> > I would like to make notice of this and would like to know
> > if anyone can tell me how to disable the windows
> > messenging service so that ads like this are not accepted
> > by computers.
>
> Hi
>
> Properly configure a firewall is what you should do. Block access to ports 135,
> 137-139, and 445.
>
> Windows Messages
> http://www.jmu.edu/computing/security/info/winmsg.shtml
>
> myNetWatchman Alert - Windows PopUP SPAM
> http://www.mynetwatchman.com/kb/security/articles/popupspam/
>
> Wired: Spam Masquerades as Admin Alerts
> http://www.wired.com/news/technology/0,1282,55795,00.html
I always had ports 137-139 blocked, and I still get these pop-ups.
I'm a bit reluctant to block port 135 because it seems to be needed
for Exchange. Similarly, I think port 445 is used during logon over
our VPN.
Does anybody have any experience running an NT network where ports
135/445 are blocked at the firewall?
- Next message: Karl Levinson [x y] mvp: "Re: Logon Password Problem."
- Previous message: Karl Levinson [x y] mvp: "Re: scheduled task logon failure"
- In reply to: Torgeir Bakken (MVP): "Re: windows messenger spam"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|