Konqueror->smb://<IP>/<share>->HANG!
 

Alrighty, I open up konqueror to access the shares on the Windows XP/2k computers on my network... I input 'smb://192.168.0.<comp specific 1-21>' I get the shares OK but when I try to access them konqueror hangs... It doesn't freeze... I can still stop it from trying to access the share... and the gear Icon is still moving... but nothing happens... no matter how big or small the share I'm trying to access is. What's wrong here? LISA is running... Samba too... in fact all the Win comps can access my Samba shares... but I can't access the Win shares...

I believe you need to be running a fat32 file system on your Win box to be able to access your Win files from Konq. If your running a NTFS file system on your Win box you need to add a NTFS module to konq.

Ok... Where do I get that?

I could be very wrong, but my understanding of the SMB protocol was that it was platform and format type independant. I can access fat32, NTFS, ext3, and reiserFS all from konq using SMB://<IP Address>

As for your problem, are you sure that you have the latest versions of the samba client and or the kio_samba package for KDE? If so, is your samba set up to use encrypted passwords. By default samba tries to use unencrypted passwords, while windows, by default, encrypts them.

Write back with what you find :-)

Steve

Sorry, was away for a little bit. Up Ok here's the deal. I cannot access ANY shares on the network, FAT32, NTFS, Anything. Shmeg, I can't even access the shares on the Quantum Snap Server we've got here, I mean, even the Macintrash can access those... but yeah, konqueror just hangs. I have the packages that came with RH8 and the Win XP/2K Comps can all access my Samba shares but not the other way around... the samba config file says that it's using password encryption.... Is there somewhere else I need to check... Oh, this is is off the topic but as a side note... KDE has been popping up these annoying little boxes asking me what to do with a certain internet address.... How do I make it stop doing that...

Have you tried mounting samba shares outside of KDE?

should go something like this :

open root console
'mkdir /mnt/myshare'
'mount -t smbfs -u username=foo,password=bar //windowsbox/sharename /mnt/myshare'

now you can copy to and from /mnt/myshare. If it doesn't work try using the ip address of your windows box: 'mount -t smbfs -u username=foo,password=bar //192.168.0.1/sharename /mnt/myshare'

You would obviously want to replace the username and password with something valid. Let me know how it goes.

--Steve

FINALLY! Thank-you my friend. Oh, the part "-u username=foo,password=bar" doesn't work. mount doesn't recognize the argument. Instead I remove that line and it asks me for a password after I run the command.

Cool, (that's what command lines are for :-) It would still be great to know why the kio-server for samba is locking up on you, as I find it more user friendly. I'll give it some thought once I get off of work and get back with you.

--Steve

I have similar problem as mentioned above... When I try smb://computer in Konqueror, it shows me the list of available shares, that's ok. But when I try to enter ANY share on any computer on our LAN, Konqueror just rotates its gear wheel and shows nothing. However, smbmount works perfectly, but I wanted comfort! Please help if you can. Thanks

Here's a solution. Since fstab doesn't seem to like mounting anything if there is a space in it's name, just create a script to mount all the shares you need. I've kind of gone in the direction of windows on this one. I have a directory on my desktop labeled 'My Network' and under that I have a directory for every computer and in those dirs I have a dir for their respective shares. I can simply run my script to mount all the shares to their respective folders in there. The only problem is that I can't write to any of the mounts here's a line that I use in my script:

mount -t smbfs -o username=<user>,password=<pass> '//<IP>/<Share>' '//home/Daniel/Desktop/My Netowrk/<Comp>/<Share>'

works but I can't write to the share...

Yes, this solution came to my mind too. There is only one problem: what if I know the name of the computer (or IP) but I don't know the name of the share? Yes, i know about the "smbclient -L", but I wanted a little bit complex solution...

Does anybody has the same problem except two of us? Do you think it's a bug or just a bad configuration?

look at the computer that the share is on. or get on a windoze comp.. it'll give you the names of the shares in Networking Neighborhood...

libsmbclient
 

Install libsmbclient, if it isn't already installed. That fixed the smb:// issue for me.

I am sorry, libsmbclient is installed.

Other issues
 

Have you tried running konqueror from a konsole to see what error messages are printed out?