Re: suse 9.1 and samba problems (protocol died etc)

From: AC (aec$news_at_candt.demon.co.uk)
Date: 06/04/04 

Date: Fri, 4 Jun 2004 21:32:27 +0100

In article <G0H7FTBw22vAJAJV@candt.demon.co.uk>, AC
<aec$news@candt.demon.co.uk> writes
>In article <criNSCChY5uAJAyq@candt.demon.co.uk>, AC
><aec$news@candt.demon.co.uk> writes
>>> error: Konquerer
>>>> Internal error. Please send a full bug report at http://bugs.kde.org
>>>> Unknown error condition in stat: Network is unreachable
>>>>
>>>
>>>I had the some problem. If you go into YaST, Network Sevices, Samba Client
>>>make make sure the is nothing in the Domain or Workgroup. If there is,
>>>clear it and click Finnish. One I had done that, I was able to access my
>>>Windows shares using the 'Network Browsing' desktop Icon.
>>
>>Thanks! great!
>>is this a 'bug'? it seems a bit counter intuitive that when I am using a
>>workgroup, that this samba client field should *not* contain the
>>workgroup name that it actually invites?
>>--
>>AlanC
>
>
>This did not *completely* solve all my problems with using the Local
>Network icon, and a search came up with a thread in
>www.linuxquestions.org for which I am greatly indebted.
>
>The thread begins from rimcrazy (post #1) - a *very* similar problem and
>experience to mine..... and ends with an elegant workaround in (post
>#25) - extracts below:
>
>
>http://www.linuxquestions.org/questions/showthread.php?s=&threadid=18111
>7&perpage=15&pagenumber=1
>
>suse 9.1 and samba problems:
>
>======================================================
>ID: rimcrazy
>suse 9.1 and samba problems ( post #1)
>
>In trying to get samba up and accessible through Konquer I'm running
>into some problems.
>First let me preface that I am no Samba wizard by any stretch of the
>imagination. When I installed Suse 9.0 on my machine before Samba just
>came up and ran no problem. Then I did an install of everything. With
>9.1 I modified
>the install and did most but not all of the modules (I left out Gnome
>and KDE development as well as some of the networking stuff and apache
>as I did not think I'd need it.). I have a simple home network with no
>server, just a few win2k machines and my Linux laptop. (Inspiron 5000).
>When I open up Konquer and click on the Network button I get the
>following message:
>Note -'s inserted as I can't yet post url's
>
>Internal Error
>Please send a full bug report at http-:-/-/-bugs.kde.org
>Unknown error condition in stat: Network is unreachable
>
>If I go to the address tab and type in:
>
>smb-:-/-/-enfusiasm-/
>
>I get folders for both machines on my network (enfusiasm is the name of
>my local workgroup), opus (suse laptop) and dilbert (win2k desktop). If
>I then try to open up dilbert I get a prompt for the username and
>password which I fill in and then I get the following error message:
>
>The process for the smb-:-/-/dilbert protocol died unexpectedly.
>
>If I try to expand (click the + button on Local Network) in Konquer I
>get
>
>Can't find parent item smb-:-/ in the tree. Internal error.
>
>I opened up YAST and under system looked under run level and the smb and
>smbfs process are both enabled. They are both set to run levels 3 and 5.
>When I go to expert mode smb is running but smbfs is not. If I try to
>start smbfs I get the following message:
>
>/etc/init.d/smbfs start returned 6 (program is not configured):
>Mount SMB File System ..unused
>
>Now I'm not sure that I need smbfs to be running for what I want to
>accomplish (see my windows machines from my linux box) but this is what
>I've checked into so far.
>
>Any help would be appreciated.
>
>Phil
>======================================================
>
>[snip some excellent posts from dedicated persistent people]
>
>=========================================
>ID:
>gacott
>
> Come on, it's a bug ( post #25)
>I found an easy workaround, and one that was probably meant to be how it
>all worked.
>Kcontrol/network settings/local network browsing
>Place you client info there
>reboot/restart the client
>done.
>Works perfectly.
>Garret
>=========================================
>
>
>Again, my thanks to this group and the posters above!
>
>(PS - hopefully this will get some update fix in time? It seems to be
>tripping a lot of people up?)

For thread completeness I should continue -

Spoke a bit too soon, it worked for a time, but later still gave
problems. I see from discussion at:
http://bugs.kde.org/show_bug.cgi?id=79506
(extract below) that it seems as if a samba recent version is available
now from:

====================================================================
------- Additional Comment #16 From Stephan Kulow 2004-06-02 09:20 ----- 

-- 
For those using SUSE 9.1, update from http://de.samba.org/samba/ftp/Bina
ry_Packages/SuSE/3.0/i386/9.1/ 
====================================================================
and this contains:
Parent Directory        14-May-2004 19:39      -  
 ldapsmb-1.31-0.4.i58..> 14-May-2004 19:37    40k  
 libsmbclient-3.0.4-1..> 14-May-2004 19:37   526k  
 libsmbclient-devel-3..> 14-May-2004 19:37   572k  
 samba-3.0.4-1.2.i586..> 14-May-2004 19:37   6.9M  
 samba-client-3.0.4-1..> 14-May-2004 19:37   5.6M  
 samba-doc-3.0.4-1.2...> 14-May-2004 19:37  10.8M  
 samba-pdb-3.0.4-1.2...> 14-May-2004 19:37    49k  
 samba-python-3.0.4-1..> 14-May-2004 19:37   4.4M  
 samba-winbind-3.0.4-..> 14-May-2004 19:37   1.3M  
which looks like samba version 3.04.? where as with Suse 9.1 I seem to
have installed samba version 3.0.2a-SUSE, so it is credibly a desirable
direction for me.
The bad news is that as a linux & suse newb it is a struggle (and risk)
for me to install something like this - (I will post a Q in a new thread
'newb install new samba?')
-- 
AC