Kshitij Velhal (kvelhal@gmail.com) wrote something I wish to comment : (news: posted on 27-juin-05 20:17:07)

I think this is very well known issue. But still could not find a right solution for this till Now. (It's there in 9.2, 9.3 and even Fedora 3 and 4 for that matter)

I don't know if it's a weel-known issue, but I'm having difficulties to configure/use Samba too. See: http://lists.suse.com/archive/suse-linux-e/2005-Jun/1226.html I put this problem on hold for the moment (busy elsewhere).

I have firewall running with ports 137,138 UDP and 139 TCP opened.

All windows machines (2K and XP) in my home network are able to access shares and printer on my SUSE box. They can ping the box or browse the shares using DNS name ("Linux" in this case)

No Windows-seized machine here. My second computer is an Amiga 4000. ;-)

But SUSE linux box cannot access any of these machines by their DNS names. Its not possible to browse and find computers from konqueror using smb:/

However I can access the windows boxes using their IP without any problems.

If I turn off the firewall on Linux Box I can also access the windows boxes by their DNS names.

I am not able to figure out which firewall rule is blocking nmb daemon's capability to browse the network.

I am using YaST to configure the firewall. (Not familiar with backend - iptables)

Can anybody tell me (or point me to) the solution for this problem. I am sure its just a matter of setting/modifying a rule in firewall. but not aware of what it is.

I too suspected the Firewall was the cause of the problem, as KDE often told me something like "Failed to connect, maybe blocked by a firewall". I'm not so sure anymore this is a firewall issue. I made many, many tests to try to get a working Samba network. Most of the time, I cannot even see the workgroup, but from time to time, I can go as far as to reach the shares on the remote computer before another error message pops-up ("Unexpected error", "Connection timeout", "Please report bug to http://bugs.kde.org/"). This is with the Firewall active, using Konqueror on "smb:/". I got the impression that smbclient gave better results, but it too suddenly "lost" its connection ability without any noticeable reason. These connections failure also happen with the firewall disable. I tried many configuration settings on the Samba server (my Amiga computer) with no improvements on the Linux side. And finally gave up. Now I'm wondering if either: - the Samba clients on Linux are weak when talking with non-Windows driven machines (but as it seems, you are having problems with Windows too), - there is something to tune on the client (Linux) side which is not accessible with the KDE Configuration Center nor Yast, - running a Samba server on the Linux box too is needed if you are expecting a stable Samba network. With Suse 8.0, the only way I managed to get a useable Samba connection with my Amiga was to run a Samba server on Linux too, and mount my Amiga shares using a tool called LinNeighborghood (not in 9.3 anymore). Sorry for not being more helpfull, but I'm stuck too on this issue. AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN CARNIVORE KILLER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. HvoRttxYDUM5GlLSvpyvWEFAHERpybpVVtczOjKAOlItHtlxIhEqpVJtHyCVdIMS6IAFMVHz vtA1OkcIMFVDODVqW3ypBD0EnJpxyVTzrtORHF2FytUOP5Rz1FTMaWSOlWdSjEII0pGEJvpa zJlHJMUzOyLvFDKvvVqLIVOHlqqzRnxVStRatyBabFHDFOVEHInNIlRyM5U3fOOMPuvG5t== -----END CARNIVORE KILLER----- The dark side of the American Dream a few may enjoy is that it is often build upon the nightmare many have to live with.

Kshitij Velhal (kvelhal@gmail.com) wrote something I wish to comment : (news: posted on 28-juin-05 17:33:45)

Has anybody figured out any solution for this issue?

Try a search for "Samba" or "smb" on http://bugs.kde.org/ you may find something of help. I will resume my investigations on this issue ASA I have more times.

[...]

...

Now I'm wondering if either:

- the Samba clients on Linux are weak when talking with non-Windows driven machines (but as it seems, you are having problems with Windows too),

Browsing a few bug reports on the KDE bugs site, it seems that Samba clients (kio/KDE) are at least mentioned as the source of some troubles.

...

- there is something to tune on the client (Linux) side which is not accessible with the KDE Configuration Center nor Yast, - running a Samba server on the Linux box too is needed if you are expecting a stable Samba network.

With Suse 8.0, the only way I managed to get a useable Samba connection with my Amiga was to run a Samba server on Linux too, and mount my Amiga shares using a tool called LinNeighborghood (not in 9.3 anymore).

AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN ECHELON TEASER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. IIypSSEpHMFBHjRMJFHOt25hEIVMlDypYykUlTHDvOHFVSqMWcRVxBUPHrHlyt1WUxpEtWqO AGaz2AnVvWdLxjyVpHJIyFKtnGIVDzIJtOzafbtWtzvOlvptRvOtpECcEpxJjllCytLFVLMI StIHvFETdIUKADzIODaVz0OzHS5RqRoOMDOnFFyAvV5aOvU0l3O2J35RMqD3ylx1HaF6MVVM Op3qtNVVb0FRyaGVyEltv0utqPIP== -----END ECHELON TEASER----- Now I've gone too far, where do I go now?