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.

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?

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?)

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 have fixed the problem....

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

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