Category: <span>Jake’s Brainpan</span>

I have no idea what this means, but I was just chosen as Geek of the Week for the week of May 19, 2002. Funny thing is that the site they’re pointing at is my first weblog, J-Space, which I haven’t updated since October, 1998.

It might be interesting to some that J-Space was the site I recovered from Google’s cache in Janurary of last year, after a bad hard drive crash — the second in three months. Leander Kahney wrote a story about it for Wired News, which still generates hits to both that site and this one, to this day.

(I later found a nearly up-to-date backup of the J-Space database, so I was able to fully restore it, images and all, but Google was still very helpful.)

Jake's Brainpan

Comments closed

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 jake@userland.com, or get in touch with me on IM:

Yahoo IM: jsavin
AOL IM: brainpanjake
ICQ: 130186778

Jake's Brainpan

Comments closed

Our static server is a Linux machine that runs Samba, to allow our Windows servers to create files to be served by Apache on the Linux server.

We have Windows computers in two separate subnets, which all need to be able to connect to the Linux server via Samba. The Windows computers in the same subnet can connect just fine, but the ones in the other subnet can’t.

Question for Samba experts: How do we configure Samba so that the Windows compuers in subnet A can mount a Samba share on the Linux machine that’s running in subnet B?

If you know the answer, please send email to jake@userland.com, or post a reply in my discussion group. Thanks!

Jake's Brainpan

Comments closed