I have been slogging through the samba installation learning how to access resources on a remote server. I went to mount a drive with smbmount only to find that the application does not exist in the current installation.
~> smbclient --version
> openSuse v11.1
> What has replaced “smbmount”?
> I have been slogging through the samba installation learning how to
> access resources on a remote server. I went to mount a drive with
> smbmount only to find that the application does not exist in the current
> ~> smbclient --version
> Version 3.2.7-11.3.2-2154-SUSE-CODE11
see: man mount.cifs for the details.
“We’re all in this together, I’m pulling for you.” Red Green
Can you browse to the share from this computer using Nautilus or Konqueror?
I do not know what you are asking. Using the “My Computer” link I can view the “Network Services” which has a pseudo-protocol of “remote:/”. I can then list all of the servers which has the “smb://” protocol. From there I can select and access a share on the target server, <sma-server1>.
I can list the shares on the server using <smbclient -L //sma-server1>, and access a share using <smbclient //sma-server1/pub-data -A …>.
What do you get when you run this command: smbtree -N?
FAQ: Attaching to legacy servers (OS/2, Windows 98/Me: I have not tried these. I am just reporting them for you. Older servers require a few extra options in the mount strings. You appear to need the security option sec=lanman in mounts for OS/2 and Windows 98/ME servers. And it seems you need the server-name option as well for 98/ME servers (servern=netbios_name)
Does that bout sum it up, or is there more?
Yes, there is more. Both the “servern” and “sec” options are required. I had dropped the servern option since it seemed to work without it, but after a reboot is was required again. Note that the servern value must be capitalized. The “nocase” option makes navigating a case-insensitive filesystem like in os/2 much easier.
Here is a complete /etc/fstab entry (text is no doubt wrapped):