I am setting up a "back-end" network, which consists solely of my laptop, which is running winME. My linux machine is connected to my DSL line on the external eth device, and the laptop is on a crossover cable on the internal eth device. I have set up what I believed to be a pretty logical Samba configuration using SWAT. The problem is as follows:
I will refer to the computers as Samba and Linux.

1. Windows cannot connect to Samba, saying Linux is not accessible.

2. smbclient -L Linux gives me:

session request to LOBSTER failed (Not listening for calling name)
session request to *SMBSERVER failed (Not listening for calling name)

3. smbclient -L 127.0.0.1 gives me a login for the samba server.

Under /etc/hosts I have (altered to protect the innocent)
127.0.0.1 localhost
192.168.1.1 Linux.localnetwork Linux
192.168.1.2 Windows.localnetwork Windows

I can get more specific if anyone has any suggestions or follow ups. Any help appreciated. Thanks in advance.

Matt

Also, just to correct my own mistake, substitute Samba for Windows in the /etc/hosts file. I forgot what names I was using while writing the post.

Matt

Ok let me completely rephrase now that I have read my post and seen that it makes no sense whatsoever. Sorry about this.

The problem is that the Windows computer cannot connect to the Samba/Linux computer, and also that the Samba/Linux computer cannot connect to itself, unless I refer to it as 127.0.0.1

I hope that makes more sense.

Well first off, check your iptables configuration to make sure the ports that SMB use are not blocked. It would help to post your smb.conf file here as well. I assume that basic connectivity tests between the machine (ping) work correctly as well. It's nearly always something simple, check the name of the workgroup in your smb.conf and make sure the laptop wg is the same. Just some opening suggestions.