I thought it had to be running on both server and client. You may be correct, as the "top" command does not show it running on my Pardus machine. But my experience has been to connect to the shares only when samba-client/samba-common are installed and samba is running.
I'd welcome an education on this issue, but it's a sidebar to Cnaeus' problem. I'm having no trouble connecting to the server or to printers on the network (not connected to the server).
 fixed a typo in the paragraph just above.
 I installed Mandriva 2011 RC1 yesterday. It would not connect to the server until I installed samba-client and samba-common (+ cifs-utils, and maybe nss-wins). Pardus 2011 and above appears to have only samba-server, giving service to files on network machines while advertising the Pardus machine and its shared files.
[edit2] In direct contrast to Mandriva, I installed Fedora 15 Gnome from the live CD. I punched a hole in the firewall to allow networking, including samba, and was able to connect to the server shares -- without samba-client and samba-common on the Fedora side. So, atolboo, you appear to be correct and I incorrect about whether those two packages have to be running to connect to a server sharing files.