suse 9.1 and samba problems
 

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

same issue
 

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.

Same 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...

Re: same issue
 

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........

same issue
 

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.

Re: same issue
 

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.

pirisisi -

Please forgive me for not having a clue as to what I am doing here, but I am new to Linux. As per your post I downloaded 0.3.2 and I too got it working but get the same suid root smbmnt and smbumount.

I am thinking that suid is "super user ID" so I login as root and this all works like a champ. What is it that I need to do you get it working under my user account? As I have read and learned, it is a bad idea to work as root but I am really not sure what the syntax above directs me to do. Am I supposed to remain a super user all the time?

Read the FAQ. It has the answers you are looking for ;) http://smb4k.berlios.de/faq.html

The gui stuff always takes a while to work (witness Windows).
As for NT4 domains, mentioned earlier in the thread, M$ won't support the domains, or issue security patches for NT4 after September, so it's time to move on (or off Windows).

What always works, even for suse91 which I am using now, is regular old unix, command line:

mkdir /mnt ; mkdir /mnt/winboxname
mount -t smbfs -o username=someadminID //winboxname/c$ /mnt/winboxname

You will be prompted for a password. As you are mounting an administrative share (c$) of the C drive you'd better be a domain admin or a local admin of the winbox, depending on policy or the whims of Mr Bill.
You will get a bogus error. Don't worry. CD to /mnt/winboxname and look at the C drive. Copy stuff, write stuff, delete stuff, whatever. You can go into whatever gui file manager you want to use and see the remote box under that directorry (/mnt/winboxname). Do your thing.

You can modify your /etc/fstab to mount winboxes automatically, or not. If non-automatic entry is in the fstab, you just have to type: "mount /mnt/winbox" and *nix knows where to mount it, and how to mount it.
(man fstab)

It's a work-around, but until somebody figures out what broke in the GUI or in Samba config, it'll do for me just fine. I've got too much other stuff to fix to worry about something that has a work-around.

--curmudgeon

LOL, okay I am feeling pretty dumb now ... I did read it, must have missed that on the first go-round. After re-reading the FAQ I have 0.3.2 working fine, suits my needs, thanks to all for your help!

To all who have posted thanks much. I went and downloaded smb4k and installed it and it works great.
I suppose it would be nice to know what the root cause of the issue is but those days for me are long gone.
Anymore, I just want to install it and use it. I'm guessing it is either a bug in Konqueror or win2k or some
interaction between the two. Samba on SuSE is certainly running properly and from every other measurement
it is not related to anything there. Now I can print and file share and I'll leave the why's up to the wizards to
figure out.

Tnx

Hello,

Well I'm just about to download smb4k but in the meantime I discovered that when you've been prompted for a user name and password to connect to a Windows share then, when the process fails, the address in the addres bar shows "smb://user@windowshostname/".

Now if you change this to "smb://windowshostname/sharename" then you are connected as normal. So the problem would appear to be the "smb://" share string that konqueror constructs for you (I'm presuming it's knonqueror that does this)

Oh well... I'll download sm4k and fix the problem now but just thought I'd mention the workaround in case it's of use !

SuSE just released an update for the smbclient. I don't know if it corrects the issues people are having with Konqueror and SMB, but it might help. I went the way of fstab, and my network shares are as close as /mnt/archives. I still fail to see what advantage there is to using smb4k as opposed to a one line entry in fstab and having the share mounted locally.

Konq is still pooped after the updates.

You hit it on the head. In fact after installing smb4k and doing a quick top I uninstalled it or basically quit running it. I is constantly
doing something and the memory usuage slowly creeps up. Just to a mnt with fstab and fagetaboutit as they would say.

Come on, it's a bug
 

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

I have this problem too with suse 9.1. Since I am a very new linux user I am not yet confident enough to sustitute new (old) programs into 9.1. Is there any news about this prob yet?
:Pengy:

Apologies - have just tried Garret's workaround and it is pretty good - thanks

(is this a suse issue or a samba etc or konq or what?)

Apologies
 

Glad it worked for you.

It looks like a SuSE issue to me, especially since the fix is Konq based.

Garret

Thanx guys, I followed this thread and got some good pointers on how to get shares working. All I need to be able to do from this box is being able to read and write shares on winboxes. Well (thanx to smb4k) this now all works. One problem left, I saw it mentioned in one of the first post: my debbox is fine now, but I can't use my winbox to enter a share on this linuxbox? How was that fixed by you? The shares on my other box (clarkconnect 2.2, someday to become a webserver if I ever get to understand all this Samba, Apache and configuring stuff), can be read from both.

Regards

suse 9.1 and samba problems
 

Suse have fixed the problem....

Perform an "Online Update" and you'll notice SMB files being updated...

Once completed..the glitch is gone....

Fantastic - I've been following this post waiting for an answer - I'd upgraded from SuSE 9.0 to 9.1 - thought Samba server was broken not client and had to backtrack in a hurry. Guess I should have waited a bit longer to upgrade!

Im having the Username/access problems too on my machine. so any headway on this topic or a answer that would fix this plz post....

Ditto (almost)
 

I have suse 9.1 in a network with windows 98 and Unixware 2.0.
There are two shares on windows and two on Unix.
The windows shares are C: and D:.
The two on unix are public (root) and homes (/home/username).
Permissions are wide open on both unix shares.
The problem occurs on three of the four shares.
It also occurs on certain folders within the shares.
Public on unix is ok as long as you browse away from /home.
If you try to go to /home, the problem occurs.
/home is where the problem is, because if you click the homes
folder in Konqueror, it hangs on /home, not /home/username.
On windows, it happens browsing to C; or D:

I found out how to get it to kinda work, at least on my setup.
If I click on the address bar, delete the @username, and press enter, it works ok.
The problem then occurs when backing up off the share.
You can go hack up the address bar again to get going,
but the easiest way is to hit back again.

Here's the wild part -
From what I've seen so far, once you complete this procedure with any share
or subfolder, the problem for that share or subfolder goes away.

Hope this helps.

A couple of hacks that both work.

Go into the Konqueror address bar and type:

smb://yourworkgroupname/

Be sure to put the ending slash. Hit return and you samba shares should come up. Also, if you book
mark this and show the bookmark bar, then it is a non issue.

I've gone to mounting the samba shares I need the most. In particular, my tunes are on another
server and you MUST mount that directory if you want it to work in xmms.

This may point some people in the right direction. Samba3 has changed the way it passes information.

http://www.bnro.de/~schmidjo/faq/index.html#faq17

Walter

Hint: How to stop SMB from dying unexpectedly
 

I just did a clean install of 9.1 from Linux Mag cover-dvd and ran into the issue of smb dying unexpectedly when accessing SMB-shares.

Open the Control Center - Select YaST2 modules - Select Network Services - Select Samba Client

At this stage YaST is complaining that this service can't be administered because the smbwinbind-package (i think its the samba-winbind-package) is missing and it demands another look at my DVD ;) After installing this package SMB-browsing from Konqueror works as one should expect :)

Hope this works for you :)

To Correct Network Browsing: Follow steps

1. Install popt-1.7-176.3.i586.patch.rpm

http://ftp.idilis.ro/mirrors/ftp.sus.../9.1/rpm/i586/


2. Upgrade Samba from 3.02 to Samba 3.04

1 ldapsmb-1.31-0.4.i58..> 14-May-2004 19:37 40k
2 libsmbclient-3.0.4-1..> 14-May-2004 19:37 526k
3 libsmbclient-devel-3..> 14-May-2004 19:37 572k
4 samba-3.0.4-1.2.i586..> 14-May-2004 19:37 6.9M
5 samba-client-3.0.4-1..> 14-May-2004 19:37 5.6M
6 samba-doc-3.0.4-1.2...> 14-May-2004 19:37 10.8M
7 samba-pdb-3.0.4-1.2...> 14-May-2004 19:37 49k
8 samba-python-3.0.4-1..> 14-May-2004 19:37 4.4M
9 samba-winbind-3.0.4-..> 14-May-2004 19:37 1.3M

http://de.samba.org/samba/ftp/Binary.../3.0/i386/9.1/

Should be golden after this. smb4k is also a good alternative as well........

I got a stupid question - how do you start the Smb4K program? I installed the rpm (4.1.0a) but do not know how to run it. "whereis" and "locate" do not return anything for smb4k or Smb4K other than the icon file. Sorry for the off-topic post.

Absolutely no offense intended to anyone who's posted but I've used samba and correctly configured it in every version of SuSE since 9.0. I don't believe this is a bug. I've also never used a workaround, that I know of anyway.

This is what I do. I use Yast, because it's simple. On the linux computer that you want to view from Windows you need to go to the Yast samba server side configuration (I'm doing this from memory), and enter in all of your network information. Ok next you need to setup a samba user (or password) with , execute it from a terminal. I would not recommend using root for this due to security.

If your on XP I would run the network wizard from within internet connections in the control panel after executing this. Make sure your LAN address is in sync with your linux machines address, hostname, domain, workgroup, whatever.

After that it should work.

Sorry, if I left something out; like I said I'm doing all this from memory.:D

rights smb
 

In my case I could fix the problem by updating smb client and server with the online patches.
Works great.
Now I can mount network folders and access them. I wrote commands in my fstab, as i was used to in Suse 9.0. Now on Suse 9.1 I have the problems that I can acess my folders but cannot write anymore. So there must a problem with the rights? As root I can write on this folders. So where is the problem?
Furthermore I can't acces my folders on this PC from another workstation. It doesn't prompt for password. It just opens and shows the print folder.


Rock

support for smbfs filesystem needed?
 

I'm quite new to Linux and have been trying to configure Samba to see Windows shares. I'm using SuSE Pro 9.1 and have now installed all the latest online updates. I hope this is not too much of a newbie question, but I was reading in an older textbook (Dec 2002) that support for the smbfs filesystem needs to be configured into the Kernel. When I look at the /proc/filesystems I noticed that it wasn't a supported filesystem with the original installation or after the updates.

Can anyone set me straight on this one? Do I need this compiled into the Kernel? Do other people on this thread have it listed in /proc/filesystems ?

I'm about to try all the different workarounds described here on the thread. Comforting to know that it wasn't just me who was having these troubles.

regards Rob

Hey

Has anyone found a solution for this problem, I am experiencing it under Suse 9.2 , will try the smb4k workarround but also need to authenticate into the domain, not sure smb4k can help on this

cheers

A few things I've found since I made this original post.

1) First make SURE that your user ID and password on windows an in SuSE are exactly the same.
2) I've seen quirks where I don't believe your samba user ID is initialized correctly. Do the following:

phil@dilbert:~> su
Password:
dilbert:/home/phil # smbpasswd -a phil
New SMB password:
Retype new SMB password:
dilbert:/home/phil #

I added myself as a samba user and set my password the same as my windows account.

3) Open the KDE control center. Go into Network & Internet browsing. Enter in your user ID
password and Workgroup name.

4) Make sure you have shares set up on your windows machines and that they have been setup with the
same workgroup name. Fire up Konqueror and click on the network icon on the left side. If you don't see
the icon's on the left side hit F9. This is a toggle to see your services. Click on Local Network and
hopefully you should see at least two Icons, one labled All SLP Services and Windows Network. Click on
Windows Network and you should see your workgroup.

I've just switched my Window$ boxes from win2k to winxp. Now I understand why everbody is so pissed
off about SP2. There are some definite strange things going on in winxp that for the moment I haven't figured
out, but this is a Linux forum not a windoze forum so I'll just keep pluggin into what screwed up things Billy
Boy has done to me now.

A few comments on Konqueror. I'm amazed at all of the protocols that it does support. Windows Explorer is
a broken tricycle compared to this Ferrari. For grins open up Info Center (if you are using SuSE) and look under
the Protocols tab. That entire list are the different protocols you can use in Konqueror. I've used it for SSH
tunnels between my house and my son's. Works like a champ. Pretty slick tool.

Well Well,

I did the following and worked out... don't know which part of it did the trick

I installed all the 3.0.11 versions ( including LAPD )
still no browse

I went to the the YAST Control Center, Run Level Editor
I then disabled the firewall
and then disabled the SMBFS (to start it again which by the way I couldn't do)

I went back and enabled the firewall

Browsing started to work, ?!