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

And I thought I messed something up. I am experiencing the exact same behavior after upgrading to SuSE 9.1 Pro. I am doing a little research on it and will post any results I come up with. In the meantime, if anyone knows why this is happening please post a clue and save us some time...

Find anything yet??? Still poking around. Loaded 9.0 on my desktop to see if in looking at differences in setup were making a difference. Nothing yet.

Phil

Hi I am running SuSE 9.1 and am having the same Samba related errors as described above. Also I installed Fedora core 2 test3 and had the exact same error. Now both the above distros are running a version of the 2.6 kernel. But if I load a distro such as Mepis or PCLinux (both running versions of the older 2.4 kernel) everything works fine. So , again I am no linux expert buy any means, but it seems something with the newer distroa running the 2.6 kernel (and maybe SE linux ) is having local network/samba issues.

Oh and I have installed Linnneighborhood as well , thinking it might be some KDE related issue , but then I can see the other windows computers in my network (only via IP) but then I cannot mount the folder. So there are some serious issues here.

I have the same issue as listed above. My other PC running 9.0 is also fine, as well as a RH9 station my co-worker is running. Fairly odd situation, it allows browsing of the parent domain, but as soon as I access a child ...

The process for smb://servername protocol died unexpectedly

I think this may qualify as an official bug, anyone know how to report it?

Now this is strange. I installed 9.1 on an Optiplex GX-270 this morning and Samba is working fine. I did install the YaST configurators for SMB and SMB-client, which I didn't do before. I will check my settings and match them when I get home. This is weird...

No, this is not a bug. I've been messing around with some simple setups, not using any of the autocofig files. I'm convinced this has something to do with permissions, users and passwords. Probably all three. Just noticed that if you go into Konquer and look in home directory, right click on and get it's properties. There is a tab for sharing. If you go into this and select the settings you are requested to log in as root. Then you get a dialog box to allow sharing or not. I selected sharing and now my test directory is visiable from the windows side. Now from the windows side it will not let me in as it asks for a login but does not see me as a valid user on the server. This has to be id's/passwords or something of the like. Need another cup of joe and dig a little more........

It worked fine in 9.0 and does not work for many in 9.1

I may be from the Windows community, but I am thinking this is what constitutes a "bug" because it does not work as designed.

A normal user should have default access to Windows networks under Samba Client/Server, especially after they enter their username and password to authenticate against the domain controller.

Not to flame Linux, but I have been using it for more than a month as an evaluation for deployment. So Far I have discovered 172 separate issues that would be a problem under an NT4 domain environment and/or for Windows users (95% of the world). I am willing to bet that about 40% of these are legit, while 60% are things I simply have not learned yet. Still it is a lot of short commings.

I didn't think your reply was a flame. I'm just saying I don't think it is a bug. A bug to me infer's the code is written improperly. I'm guessing the code is clean but I DO think there is a problem in the default setup as configured in the SuSE 9.1 Pro distro. Where? Who the hell knows. This is driving me nuts. I've googled this and seems there are a LOT of people having this problem with no clear solution in sight. In SuSE 9.0 window shares worked right out of the box, without doing a single thing. In 9.1, this appears to be a major pain in the ass. I've run tcpdumps and all of the protocol an traffic look correct. I've "thought" that I've changed configuration so passwords should not be required but to no avail. The only success (minor as it may seem) is that now my windows machines at least "see" my linux machines. Hardware is fine. I can ping all day long and as I mentioned, the tcpdumps look correct. If there is a bug I'm guessing it is in Konquerer.

Well I wasn't really flaming it ... anything that have fewer security holes than Windoze is great by me. So far I mostly just wish I knew more and was able to work from the development side. I guess in time that will come.

Back on topic, I have tried logging in as root also with no difference, so they must have may a change for the install. If I figure it out (I kind of have to) I'll post.

Interesting twist. I made a simple smb.conf file to try and debug things.

phil@opus:~/bin> cat /etc/samba/smb.conf
# Samba config file created using SWAT
# from 0.0.0.0 (0.0.0.0)
# Date: 2004/05/14 20:36:12

# Global parameters
[global]
workgroup = ENFUSIASM
# os level = 20
# netbios name = opus
# debug level = 3
# encrypt passwords = yes
# security = user
# browseable = yes

[test]
comment = Test Directory
# valid users = %S
path = /home/phil/test
read only = No
guest ok = no

I was using webmin to create samba user accounts but just to be redundant I went ahead
and added an account for myself with:

smbpasswd -a phil

After a stop/restart on the samba servers lo and behold from the win side I could see everything
I put on my linux machine (opus). From the Konqueror side however still the same crap. Just for sag I logged out and went back in using Gnome. Nautilus found everything. Kind of weird in that it made me login every time I went down the tree (that is probably a share/level thing) but it saw everything. Point is Samba is working. Now I agree with you, it may be a bug but it would be in Konqueror not samba. Still could be set up issue. I'm about 10 mins from bagging 9.1. I don't need this kind of grief and having a 2.6 kernel is just not that big a deal for my setup. If anybody else finds anything I'd be interested.

Just to add my tuppence worth...

I too am having exactly the trouble mentioned in this thread with a SuSE 9.1 installation. But I also had this proble mwhen I built my small Slackware server (which would also prompt me continually for user name and password when I attempted to access a share from my windows box)

In the case of my Slackware box this was simply down to the "windows style password muning" being set wrongly on the Slackware box so which I managed to fix by changing a setting in the samba config file (smb.conf)

So... I think this is a similar problem and once I remember the exact details I'll try and fix this on my SuSE box and, assuming I fix things, will post a proper reply here.

However this will be later as I've got to nip out for the afternoon !

Same problem here but partly solved.
If you enter user name and password the process will die and the address in konqueror will be something like (in my case the windows machine has the name "shuttle and the share is "c"):
smb://wolfgang@shuttle/c/

Now if you change it to smb://shuttle/c/ in the same window you will be presented the share. But that's it already. I cannot copy a file to my linux machine.

Still trying...

Same problem here but partly solved.
If you enter user name and password the process will die and the address in konqueror will be something like (in my case the windows machine has the name "shuttle and the share is "c"):
smb://wolfgang@shuttle/c/

Same problem here with 9.1, and I have found a workaround

I installed the SMB Share Browser program Smb4K from http://smb4k.berlios.de/
and it connects to my Windows machines without any problems.

You may want to install the latest and greatest 0.4.0 from sources. However, the ready-made 0.3.2 SuSE 9.0 rpm which can be found in the binaries download section installed without a hitch and works quite well with my 9.1. I just needed to suid root smbmnt and smbumount.

This is funny, because Smb4K opens the shares in konqueror and they work, even though trying to open the shares straight from konq doesn't.

I too had the same problem with konq. I tried smb4k mentioned above and it works just fine. It'd be nice to know why that fixed it tho.