I have reinstalled samba (and the packages that depend on it) with no luck. Having a look at the repository, I have found that the last samba package is samba-3.0.25-19-17.pisi from May the 15th, so apparently the chage made a couple of days ago has not been propagated.

Any idea?

Thanks,

echpiel

Yesterday night I updated again, but has not been able to test the results.

If the problem persist, I will uninstall samba and reinstall it again. Do you agree, Eren?

Thanks

Yes, I noticed this. I could browse the workgroup *AND* the computer shares with no problem. The problem happens *when mounting a share* with smb4k.

Thanks for your answers. I will check which version I am running when I get home this night.

I am not suggesting that there is any problem specific to Pardus, just that something has changed that is preventing smb4k fron running properly. And, hopefully, that some change in the configuration could solve it (yet I do not know which one).

Regards,

echpiel

Hello there,

I have upgraded all the packages to the latest version and have found that smb4k has stopped working. I can browse the workgroup and the computers, but when I double-click on any share, I get the following message:

-------------
The share '//COMPUTER/C$' could not be mounted.
Read the error message under 'Details' to find out more.

Details---
mount error: could not find target server. TCP name COMPUTER/C$ not found
No ip address specified and hostname not found
---------------

It looks like it is taking the share as part of the computer name, but I am not sure. I can access to the shares without problems using 'smb://computer/c$' on konqueror.

I have tried to change some parameters to both samba and smb4k witout luck.

Does anybody have any clue about this?

Thanks,

echpiel