Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have a situation where I need to execute (via WINE) a mail application which is stored on a Win2K3 shared folder. I can connect to the remote folder and find the file I need to execute, but the path "smb://username@server/TargetFolder" is not in a valid format for WINE.
Is there a way to map such a path to a standard file system path (i.e. "/samba/TargetFolder") - kind of like setting up a mapped drive in Windows?
Ok, I create a mount point at /mnt/target using mkdir.
Next, I issue the following:
mount -t smbfs -o usernane=arzer,password=thepassword //computer/targetshare /mnt/target
The shell responds:
mount: wrong fs type, bad option, bad superblock on //computer/targetshare,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
Seems like you spelled the shared location wrong? take a look at smbmount for ex. When i have mounted a CD-ROM an stuff manually i have sometimes gotten that message usually meaning i have tryed to for example mount the wrong devices file, /dev/cdrom instead if /dev/hdd for example. Though, try smbmount.
Quote:
Originally Posted by arzer
Thanks,
Ok, I create a mount point at /mnt/target using mkdir.
Next, I issue the following:
mount -t smbfs -o usernane=arzer,password=thepassword //computer/targetshare /mnt/target
The shell responds:
mount: wrong fs type, bad option, bad superblock on //computer/targetshare,
missing codepage or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.