Notices

Now I'm very confused - the shares are showing up when I type df -h - but not in the file manager. I thought these were supposed to appear in the file manager.

Yes, I verified the Samba radio button, partially because I was trying NFS as well, in case I could get that working instead.

I don't think it is necessary to login to the Netware server using a Novell client before access with CIFS or NFS, particularly since I've accessed the server via NFS using a system with no Novell client available.

Omitting the Netware part of this, it looks like I am connecting to the Windows system, but am not seeing the share outside of the command line where it is not useful to me. Is there something I can do to get the share to show up in the N900 file manager and other applications?

Thanks

I'm gonna fold on this one, Linux is not my strong suit.

However, until a fix is available, Morton, er, I mean, Midnight Commander is an acceptable substitute for a few simple copy/move/delete commands given the alternative. MC would see them as mounted in their respective folders, /mnt or /media.

Wait, did you mount in /mnt? I thought the file browser used /media. I'd give it a try.

A little success!
I rebooted the phone and tried a few more times, and now the Windows mount is showing up in the file manager.

Two potential sources of problems were caused by the N900 automatically capitalizing the first letter of the username and password which appear to be case sensitive and therefore would not work. After forcing each of those to all lower case, I was able to mount successfully.

Also, after adding an entry to the Hosts file with the IP address and the name of the Windows system I was trying to connect to, the name can be used (instead of the IP address) in the Server Address line.

I mounted in /mnt based on the commands suggested in this threat. I haven't tried media yet, although if that is what WM uses, this might account for why it shows up now that I fixed the password issue.

I can connect to a Windows share correctly with WM, but am still troubleshooting why the Netware share is not working. I can mount it manually at the command line, but am not using the correct parameters for the mount point.

Perhaps someone can suggest the command line parameter that is normally inserted by WM, with regard to mapping the share so it will appear in the file manager.

These may be something related to:

/media/Remote_Filesystems/<serverpath>@<servername>

Thanks

For reasons I cannot explain, the only way I can get connected to this server is with the following command - no other name for mount point nor Wizard Mounter seem to work:

mount -t cifs //192.168.2.110/Data /media/Remote_Filesystems/ -o username=myusername,password=mypassword

The main problem here, aside from the inability to use WM, is that I don't seem to be able to mount more than one share using different names.

Thanks

The command you are using is the same that wizard-mounter uses, so if you get things mounted correctly by command line you should have it mounted correctly by wizard-mounter.
Please keep in mind that everything (well, most of) are case-sensitive.

I don't understand what you mean by "unable to mount more than one share using different names".

Unfortunately I cannot test the situation with a Netware share.

You need to create the subdirectories you want to mount on (e.g. /media/Remote_Filesystems/Data) first - they don't get created automatically.

Greetings,

Thanks Rob1n, that's one part of what I was missing.

b0unc3, the case sensitive part that caught me was the password that the N900 auto capitalized, then of course obscured with ****** characters. A stupid mistake on my part, but it would be nice if there was a way to disable the auto capitalization for some fields like passwords.

Regarding command line vs WM...

If I first create a directory called /media/Data, then enter this in the command line:

mount -t cifs //192.168.2.110/Data /media/Data/ -o username=myusername,password=mypassword

I get a share mount such that the contents of the share directory (Data) shows up in the file manager under Data, which is a intended.

This also worked with share names that corresponded to other previously existing directories such as /media/Remote_Filesystems.

Unfortunately, I can't get Wizard Mounter to work with what seem to be the same parameters that work in the command line, as these result in a "Connection Refused" error:

Server: 192.168.2.110
Remote: Data
User: myusername
Password: mypassword

Perhaps someone can see how these may be different or describe exactly what WM would output as a command with these parameters, so I can test with that syntax. There must be a switch, space, or something that differs.

One step I wasn't aware of is when WM creates a subdirectory upon successful mount, under /media/Remote_Filesystems/ that correspond to the following:

/media/Remote_Filesystems/<serverpath>@<servername>

which in this case would be

/media/Remote_Filesystems/Data@192.168.2.105

What is meant by mounting more than one share, is that I couldn't seem to specify more than one share name in the command line since I was mimiking other people's examples, and ended up using pre-existing directories by mistake. I didn't realize that I needed to manually create the corresponding subdirectories under /media/ before this would work.

The network shares on the server are actually Data, Data2, Data3, which correspond to each volume on the server.

Now that I have the following directories:

/media/Data
/media/Data2
/media/Data3

I can use these commands to mount the three shares:

mount -t cifs //192.168.2.110/Data /media/Data/ -o username=myusername,password=mypassword
mount -t cifs //192.168.2.110/Data /media/Data2/ -o username=myusername,password=mypassword
mount -t cifs //192.168.2.110/Data /media/Data3/ -o username=myusername,password=mypassword

It would obviously be preferable to be able to do this with Wizard Mounter.

Thanks!

Great that it works, I'm sure the error will be discovered soon.

I still have one question left - how did you ever get by that Connection Refused thing? Was that an error in parameters, or what?

That's just it, I can only mount these shares using these console commands. If I try to mount with WM, even with what appear to be the same parameters, I still get the "connection refused" error.

I am hoping to discover what is different regarding the commands vs. WM.