On 10/31/2003 01:48 PM, Art Fore wrote:

Have several problems that I cannot solve in the above matter.

1. When I do the samba client setup with the firewall running, I get a message that samba client detected and that port 139 must be enabled. At this time, samba cannot find the domain. I go to the firewall configuration and enable port 139. Still same thing. I have to disable the firewall in order for samba to work. Why does enabling port 139 not work or is there something I am missing?

Samba needs tcp 139 and udp 137 and 138 open, and unless my machine is misconfigured, it also needs a populated lmhosts file (it doesn't seem to use DNS at all, and I am not running winbind).

2. With Samba working, and after setting up Lisa and windows share tabs in control center network per the info on the suse dataabase, when I click the local network icon on the desktop, konqueeror opens with the smb:/ and a libsmbclient reported an error, but didn't specify what the problem is. This might indicate a severe problem with your network - but also might indicate a problem with libsmbclient. If I replace the smb:/ with lan:/ then I get a listing of all of the computers on the network. I click on the computer name, then the smb folder, I get a dialog box to login. One time would not be so bad, but every folder under that then gives another login dialog box. I would have thought the windows share config should have taken care of that. I even put the alias in the smb.conf file and setup the passwaord file per the instructions and this also does nothing. Is there any way to get it to operate so one does not always have to login for every directory?

What Windows version are you connecting to? IMO, this is Windows problem (maybe the setup). -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.