I do not know if this will be of any assistance or not. But it might be worth a try and at least check. Since port 135 is only used by MS I would suspect it has to do with MS boxes. So if you are running Samba then make sure it is not binding to your outside world interface. If it is binding then it is acting just like an NT server would. I set my Samba machines to only bind on my internal network interfaces by the following lines in the global section of the smb.conf file. interfaces = eth1 bind interfaces only = True Use whatever interfaces you need to bind with for your services. But do not add the outside interface. Restart Samba. James On Monday 29 September 2003 01:34, Tom Nielsen wrote:
I'm with verizon "business" dsl. I've been having a problem lately with my firewall getting hammered by someone, or some people, on verizon. It almost appears that I'm getting a denial of service attack, but I think it's just somone sniffing...a lot. Example:
Sep 28 22:31:31 linux kernel: SuSE-FW-DROP-DEFAULT IN=eth0 OUT= MAC=00:50:da:0b:71:ce:00:02:3b:00:ab:32:08:00 SRC=4.3.91.228 DST=4.3.48.25 LEN=48 TOS=0x00 PREC=0x00 TTL=120 ID=34984 DF PROTO=TCP SPT=3578 DPT=135 WINDOW=64240 RES=0x00 SYN URGP=0 OPT (020405B401010402)
It's really bugging me and is causing problems getting and receiving email. Anyone know what I can do?
Tom