Try listing the shares available on my server

[Raymond]

Hello,

I try configuring Samba to share with XP.

My hostname = suse

so when I use:

smbclient -L suse

I get:

added interface ip= xxx.xxx.xxx.xxx(ISP ipnr)
added interface ip= 192.168.1.1
error connecting to xxx.xxx.xxx.xxx:139 (ISP ipnr) (connection refused)
Connection to suse failed

I don't get a list of shared files on the linux box.

What could be the problem?

Any help is welcome.

My linux box is a firewall between WWW and a Lan (with 1 XP machine).
The Linux box has two NIC (etho and eth1).
etho (to the internet) eth1 (to lan).

Now I want to share files between Linux and XP.
The outside world may not see my shared files.

So this is my situation, if you want to know more info, please ask, because I don't know what you wanna know.

regards

Ray

[cowanrl]

I'd say there is a chance that your firewall is interfering with smbclient. If the hostname of suse resolves to the xxx.xxx.xxx.xxx address, try using smbclient -L localhost or smbclient -L 192.168.1.1.

If that doesn't help and you haven't already done so, you might try restricting Samba to one interface only. Since you are wanting to allow access to your Samba shares only from your internal LAN, I'm going to assume that eth1 has the IP address of 192.168.1.1. Try adding these lines to your smb.conf file:

interfaces = eth1 127.0.0.1
bind interfaces only = yes

That will restrict Samba access to only eth1 and the internal loopback address. Restart Samba and then see if smbclient -L 192.168.1.1 or localhost works. Remember, if suse resolves to xxx.xxx.xxx.xxx, smbclient may not work if you use it because you are restricting access on that interface.

If that doesn't help, you may have to relax your firewall a bit on eth1 if you have it set up. I know Samba uses TCP port 139 and UDP port 137, plus some others. You may have to allow access to those ports on eth1.
I don't have my reference with me for Samba and I can't remember all of the ports.

Hope this helps.