Sonicwall soho series firewall reporting Malformed Packet on ports 137-139, UDP every 2 minutes

Hello,

A sonicwall soho series firewall (about 5 years old.. unsure on the version/model/firmware numbers) reports and drops a "Malformed Packet" everytime Samba broadcasts a packet on UDP ports 137-139.  

The linux distribution is Red Hat Enterprise Linux ES 3.0.
The version of Samba is the latest offered from RHN.

Source IP - 192.168.1.8 (samba server) - Destination IP - 192.168.1.255 (broadcast)

I have seen on Linuxquestions.org that others have had this problem when combining Sonicwall and Samba.  However there were no solutions offered.  Furthermore, Sonicwall's whitepapers does not have any information regarding Samba/SMB.

What was tried so far:

1) I have allowed Netbios broadcasts via a checkbox in the Sonicwall configuration
2) I have created an Allow rule for any internal UDP packets on ports 137-139 originating from 192.168.1.8

My intuition says that this is not a problem with SMB but possibly a network configuration problem on the Samba server's eth0 interface - or, it is a Sonicwall mis-judgement of a SMB packet (possibly corrected in recent versions of it's firewall family).

I will post my ifconfig eth0 output as soon as I have remote access to the server.  

Let me know what extra information is needed.

Thanks in advance!

dhaureyAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
owensleftfootConnect With a Mentor Commented:
You said that sonicwall doesnt have an option for ignoring malformed packets. I was going to suggest that you allow all packets on ports 137 & 139 but I see from rereading your posts you have already tried this. The thing that gets me though is that if smoothwall is configured to allow packets to these ports, why is it examining them anyway? There may not be an option for ignoring malformed packets but are there options as to how "strict" the packet analysis is? Apart from that Im stumped. You didnt actually need help anyway - you have already tried all the things that anyone could have advised you on. It just appears to be one of those occasions where computers get the best of us :) New firewall perhaps? You could always turn an old 486 into a firewall using the excellent  http://www.smoothwall.org/
0
 
owensleftfootCommented:
I dont have any experience with sonicwall. But is there not an option to turn off checks for malformed packets?
0
 
dhaureyAuthor Commented:
Unfortunately, owensleftfoot, I did not find such an option.  
0
Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

 
owensleftfootCommented:
Like you I found a couple of references to the same problem on the net with no solutions. What version of samba does RHE 3 ship with? The latest version of samba appears to be 3-0-2a - upgrading to this version is worth a try.
0
 
dhaureyAuthor Commented:
We currently have samba-3.0.2-6.3E.  This version was downloaded directly from Red Hat Network...  I wonder what other options we have..?
0
 
dhaureyAuthor Commented:
If it were entirely up to me - we would replace the sonicwall with a soho-series Pix (like the 506).  However, hardware procurement is out of my hands.  

It is so hard to believe that so few have used Sonicwall with Samba.  

This makes me think that we are missing something.

hmm..
0
 
owensleftfootCommented:
As you said, your firewall is pretty old. Any duplication of your problem seems only to involve redhat from 9.0 on. People are either using it with an older version of redhat or are using a more up to date version of the firewall.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.