Hi.

I've recently installed SuSE 9.1 and out of the box, it would browse for and connect to shares on a windows workstation quite happily.

I decided to have a look at the SAMBA client configuration in YAST2 and it told me that I needed to install the client. This I duly did (quite surprised, as i could already browse to W2K workstations) and now the browsing is crippled.

If I click on 'Network Browsing' on my desktop, 'Windows Network' shows up as before, but now when I select it, I get the message:

Internal Error
Please send a full bug report at http://bugs.kde.org
Unknown error condition in stat: Network is unreachable

However, if I go to the SAMBA client configuration in Yast2 and click the browse button to determine workgroups, I get a full list of all the workgroups on the network.

I have turned off the firewall altogether.

I would suggest that YAST2 doesn't use the same config file that the KDE client uses..

Probably reinstalling it has knocked the config file out and replaced it with an empty one..

Try from a command line and see if it's a global problem or a KDE problem..

do nmblookup -d 2 '*' to find computers
smbclient -L netbiosname to list shares on netbiosname
smbclient //netbiosname/share -Uusername to connect to a share on netbiosname
or mount -t smbfs -o username=name //netbiosname/share /mnt/share to mount the remote filesystem as a local filesystem

This will test 4 different parts of samba and give you an idea of what fails.
If that's all ok, start on the KDE config files, Preferences etc
(or even uninstall smbclient)

I had this problem when I installed SuSE 9.1 but it appeared to be a KDE/Samba client error - Samba itself was ok. It fixed itself a couple of weeks ago when I did a YaST online update and noticed a Samba update. If you haven't done an online update recently I recommend doing it as there appear to be a lot of fixes.

nmblookup -D 2 '*'

gave back

querying 2 on 192.168.168.255
name_query failed to find name 2
querying * on 192.168.168.255
192.168.168.254 *<00>

If I run:

smbclient -L netbiosname

I get:

connection to netbiosname failed

running suse 9.1

I'm a complete linux newbie so I appologize in advance for stupid remarks (about linux, that is)

Watch out for small letters vs CAPITALS

They are very different in *nix languages..

So, do nmblookup -d 2 '*'
small d.. to find computers. It will list their netbios names..

and smbclient -L netbiosname means use the netbios name the computer has, eg
smbclient -L bill finds shares on the computer named bill
(Use the names found with the nmblookup command)

ENJOY!

ok, thanx for explaining that little point about capitals & underscores
I got to see my shares on computer HEWLETT (yes, it's a HP)
(it first asks me for a password)

When I try the next trick:

smbclient //HEWLETT/C$ (I shared the c: drive)

It first asks me for a password, then it says:

tree connect failed: NT_STATUS_CONNECTION_DENIED

I have the feeling though, we're getting quite close

that command did work if I access the share C

what I want to do now is copy files from Windows XP to Suse Linux 9.1,
(and back again)
preferably in something GUI like Konqueror.
(and be able to do so after a reboot as well)

I know have a smb-prompt and can see the directory with 'dir'

hi I have suse 9.1 home. it can see any computer with live cd. but with normal install does not. anyway
I did smbmount. (i am away from the office I did that thing, and the office is closed until 30/8). It can see
everything. in /etc/samba is smbfstab. in that file you can do the mounting so every disk is mounted at start up.
i had no problem with fat32 disks, but I had to do it manually for ntfs (win2k). so you can have any disk in an office as part of your linux
in the place where smbfstab lies is another file called "lmhosts" there you put the address of every machine and the name
do it in the opposite way ' name - address' not 'address-name' [i cant recall what else i did, the office closed at 6/8]