Day: <span>May 2, 2002</span>

Update 12:20 AM: Now it appears that it may be a router issue. This may have been caused by a misconfiguration on the router that was masked by the fact that the server we used to use was running an earlier version of the Linux kernel…

Update 9:45PM: We’ve ruled out the firewall as the source of the trouble. The current suspect is the version of Samba that we’re using. I’m about to attempt an upgrade, and see if that fixes it. More in a little bit…

We’re still working on problems with Samba sharing to our Windows 2000 server. We’ve determined that the Windows computer can resolve the Samba server by name, so WINS and LMHOSTS are no longer variables. Now we suspect that the firewall configuration on the Linux machine is not allowing traffic across the ports required for SMB filesharing. The Linux server is using ipchains for its firewall.

Here’s a question for ipchains experts: What command would I run on the Linux command line to determine whether ports 137-139 are accessible from a specific IP address, on a different subnet than the Linux server?

I know how to do ipchains -L but I don’t fully understand how to understand the output. Also, if there’s another way to tell whether these ports are accessible, I’d like to know about it.

Please send responses to, or get in touch with me on IM:

Yahoo IM: jsavin
AOL IM: brainpanjake
ICQ: 130186778

Jake's Brainpan

Comments closed