Re: [Announce] wizard-mounter for fremantle
 

got it working now. i messed with the samba shares instead but i think i got a fireware update and its all good now.

a bit disappointed with the speed tho :( cant even stream movies.

Re: [Announce] wizard-mounter for fremantle
 

any oen care to tackle that monster of a question. pls don't be over whelmed i know its a lot. but to the brave soul who tries to answer it many thanks an b e unto you. I reads through a few pages and couldnt exactly figure out what it is. not much help on google searches eather

Re: [Announce] wizard-mounter for fremantle
 

It's a program to mount network file shares (either SMB/CIFS from Windows, or NFS from UNIX/Linux) on the Nokia tablets (N800/N810/N900).

Re: [Announce] wizard-mounter for fremantle
 

We all want more but I understand it's being worked on. With only one person working in spare time, patience is a virtue with open source.

I'd rather have low speed than no speed, however. If you need to move massive amounts of data, there are alternatives, like USB or other protocols that don't have the same limitations, like FTP.

Drawback being, FTP needs to copy the file over first, so you need the space and likely for the file to end first.

All and all, I like it. And checking back every few days to see if any speed has been gained.

Oh, and, there's a bug somewhere in the SMB or WM with Ubuntu SMB, or SOMETHING. I was at a friends' house, he has Ubuntu and I tried to copy over a movie N900 to PC.

Used CLI (cp), used MC (F5), and every time the file didn't play right. MD5Sum was different. Very odd. I copied it fine using the File Manager that comes with the N900.

At home, I use XP file sharing and CLI and MC both work fine. Odd indeed.

The resulting file had regular glitches in it, the movie kept skipping, we both (programmers) assumed there was some buffering flush error involved, since it seemed too regular to be flukes. The FM native to N900 worked, but the file never finished, even though the length was OK and the file played fine, MD5 was OK, but the FM froze at 99% or so and never finished (I ended up killing the transfer).

Re: [Announce] wizard-mounter for fremantle
 

There is a mistake in .deb, because two files are installed in the root directory, where they don't belong.

Re: [Announce] wizard-mounter for fremantle
 

@b0unc3 Thanks for the excellent software . Now I can log into corporate share drive with VPN and wizard mounter . One problem is the share drive is having around 70 folders under directory /corp , which takes much long time to load .

I am wondering how can I config wizard mounter to go even further directory like /corp/CTO , I tried many times but always tells me no such devices or address .

Re: [Announce] wizard-mounter for fremantle
 

@rooted : thanks to report it, I'll fix it in the next release.

@deter3 : if I understand correctly, there is no way to do that at the moment.

Re: [Announce] wizard-mounter for fremantle
 

Thanks for this. It's working just fine but the speed is a bit low.
Edit: I've tried to stream an avi file from my Desktop and it's very slugish

I also tried to manually mount using:
mount -t cifs //<server>/<path> /<your>/<local>/<path> -o user=<user>,pass=<pass>,ip=<ip of server>,direct
Recommended by this thread:
http://talk.maemo.org/showthread.php?t=38536

It was even slower. Anyone able to stream video from a mounted location?

Re: [Announce] wizard-mounter for fremantle
 

I cannot get any mounts to appear in file manager, which I expect is due to a simple syntax error on the server address or remote directory lines.

From another Windows machine, from the server called Myserver. one of the shares (DATA) is displayed as follows:

\\Myserver\DATA

Would someone please post the correct syntax for the entries required to properly configure Wizard Mounter? For example:

Server Address: 192.168.1.5
Remote Directory: downloads

the above from a previous post does not work, as the server address seems to require the leading // forward slashes. Does the remote directory line require a full path, forward or back slash(es) etc?

Thanks

Re: [Announce] wizard-mounter for fremantle
 

Please scan back to my post and try the "net use" command from a Windows machine as typed. If it works, then WM needs to have this:

Server: MyServer (make sure it works by PING)
Remote: DATA
User: username
Password: password

Does the WM say "mounted successfully"? If not, different problem. Also, you might need for the share to have a user and pass for it to work correctly.

So:

a) make sure you can mount via NET USE from another Windows machine, WITH user/pass

b) ping from the N900, make sure you get a reply (you might need root access for ping - don't remember)

c) if all goes well, from NET USE \\PC\SHARE /user:USER pass you should have your four parameters.

Note there are no forward slashes in the PC name, and the path is not supported unless it has none in WMounter, so no DATA/Me, just DATA.

Also, there are no slashes in paths for NET USE, it takes backslashes. Forward slashes make up an UNC path, the kind Explorer takes as address. Make sure the line is correctly used from the previous post. If it doesn't work, you have a server issue. Post the error code from the Windows machine and I'll dig in.

Re: [Announce] wizard-mounter for fremantle
 

No. It's too slow.

Re: [Announce] wizard-mounter for fremantle
 

The share works properly from a Windows machine, if I browse from My Network Places, click on the server, and login when prompted. There is a username and password in place for access.

Ping, which does appear to require the "sudo gainroot" command, can reach the server by its IP address only.

The net use command works properly as follows:

net use Z: \\192.168.2.110\DATA /user:USER PASSWORD

Z: is then mapped to the share

If I enter the values into WM as below with no leading slashes:

192.168.2.110
DATA

along with the correct username and password, the result is a "Connection Refused" message

So,

Server: 192.168.2.110 (the server's IP address)
Remote: DATA
User: username
Password: password

does not work so far :/

Re: [Announce] wizard-mounter for fremantle
 

Connection refused?

Either it's the bad address, the bad firewall, or the bad sharing service. You aren't sharing via W7 Homegroup? Homegroup networking is W7 only.

The fact that the names don't work suggests that there is a firewall/router between that doesn't allow for some packets to go through. Since the machine you tested is likely wired and the N900 is definitely wireless, I'm guessing there's a wireless router there - you might want to check settings.

Try to telnet (might needs installing) to the machine via 139. That should clear a few things up.

Re: [Announce] wizard-mounter for fremantle
 

All of the machines I'm testing are inside the firewall/router, although the N900 is running with a wireless connection. The N900 can access the shared media from the server, as well as connect to it via FTP, and HTTP so I haven't seen any indication that wireless should be an issue.

I unplugged the wired connection to my Windows laptop, disconnected all network shares, activated the wireless connection, then re-connected using the above net use command - the Windows laptop can connect to the share via wireless.

I am not using a Windows 7 homegroup, but rather a Netware 6.5 server offering SMB (aka CIFS) and NFS network shares. I cannot verify that NFS is working since AFAIK Windows does not include an NFS client, but have had no problems accessing the SMB share via wired or wireless connection.

Finally, if I substitute a garbage name for the Remote Directory in WM, I get the same Connection Refused message.

Is there a log, console, or any other way to see what the actual problem is?

Thanks

Re: [Announce] wizard-mounter for fremantle
 

The problem is "Connection Refused", meaning the machine you are trying to connect doesn't offer any service on the selected port.

Did you try to Telnet to port 139 on the target machine?

Also, just because 21 and 80 work doesn't mean 139 will.

Finally, Connection Refused has nothing to do with user, pass or share name. It is an IP (TCP) error that indicates that it cannot connect to the said machine because the machine has the selected port closed.

This means that the machine is reachable, in order to refuse anything, otherwise it would be a timeout.

If you get ECONNREFUSED by N900 and not by laptop I can imagine only one scenario: the laptop logs in to the Netware server before, thus allowing further services, whereas the N900 cannot.

If you have multiple machines on the network, share a folder on any one of them in an XP machine and try to connect to that. If it works, it's likely a logon issue by the Netware Client for MS Windows (which logs on before trying).

This is, again, assuming you didn't get a typo through in the IP address.

There is no more help to be given by a console. Once a SYN has been sent, the other computer replies "there is no SMB share here. Beat it." I very much doubt the router returns a faked packet so I'm pretty much sure the server denied you access.

Don't know how newer Novell works, but in older versions one needs to log on to the server before accessing anything.

I strongly recommend you set up another share on the same LAN and try that, maybe using the laptop over the wired connection, and just share "C" or something.

If it works, it's a server issue, most likely logon-first which is not going to be fixed soon by WM. If doesn't and you also get a Connection Refused, it means that a common equipment is playing tricks, and the only one there is the w-router.

ETA:

It has come to me that you might have port forwarding gone in the router, meaning that packets could be forwarded to an IP reserved for the laptop. This would get you a timeout, likely, but it might be worth digging up. Port forwarding could push your packets to a different IP, for example to the laptop when wired or wireless, getting you a ECONNREFUSED.

Re: [Announce] wizard-mounter for fremantle
 

I'm not sure I know how to telnet to a specific port; I tried to install telnet, then used the following command:

telnet 192.168.2.110:139

I get the following result"

could not resolve 192.168.2.110:138/telnet: temporary Failure in name resolution

With this command

telnet 192.168.2.110:139

it says:

Connected to 192.168.2.110
Escape character is '^]'.

Does this mean whatever is supposed to be working is okay?

(BTW, I'm cursing Nokia's decision to include a three line keyboard and no support for a bluetooth keyboard right now!)

From around version 5 at least, Novell began offering what they call "native file access" which is how they describe the ability to access files on their servers without a dedicated client. As such, protocols such as AFP, SMB/CIFS, and NFS allow Mac, Windows, and Unix machines (respectively) to access the server using the protocols that they already include, and without a Novell client.

Since it is unlikely and probably unnecessary to expect a Netware client for the N900, I was hoping to gain access to our servers using one of these other protocols. I can confirm that at least CIFS and NFS protocols work, which have allowed me to connect to the server using Windows and other systems that did not have a Netware client installed.

The problems that I am currently having seem to indicate that there are some additional parameter requirements or variations in the CIFS protocol not covered by the implementation available via WM. I've tried some of the switch options in attempts to mount manually from the console, but am not sure if I'm doing it correctly. It is not clear to me whether mounting from the command line needs to be done as root, whether there are any modules need to be installed, or what the correct syntax is for each parameter since each example I can find seems to have random variations.

I set up a share on a Windows XP system, which I can connect to using Sharity light on another system, but still cannot connect to with the N900 and WM. This time, the error message is:

[mount] Ops! An error occured:
mount: mounting //192.168.2.62/Downloads or
media/Remote_Filesystems/
Downloads@192.168.2.62 failed: Permission den

Is there some dependency or prerequisite to using WM that I may be unaware of?

As for the router, since all of these systems including the wireless connected machines, are operating inside the LAN/Firewall, there is no port forwarding as far as my understanding goes.

So at present, I can't get WM to connect to either a Windows XP share or the CIFS share on the server, so I must be missing something rather important. Do I need to use the name of the server instead of the IP, and make an addition to the HOSTS file or something?

Thanks

Re: [Announce] wizard-mounter for fremantle
 

Hi,

yes this not seems to be a firewall setting issue. The "Permission denied" error means you has entered a not valid pair of credentials (please re-check it) or the N900 is not able to gain access to the service (always a server misconfiguration, not a WM fails).
A useful thing you can do is to try to mount the remote share manually:
* open up the terminal an become root
* try the following command:
mount -t cifs //REMOTEIP/"SHARENAME" /mnt/ -o username=USER,password=PASSWORD

hopefully you will get a more clear error message.

Regards.

Re: [Announce] wizard-mounter for fremantle
 

When I enter the command as specified there is no error or confirmation - I assume the quotations are not to be included?

The command I used (aside from username and password) is:

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

I think that the other examples I have seen of this command include a share name after /mnt/

If I try to include the name of the share after /mnt/, like this:

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

I get the following error:

mounting //192.168.2.110/Data on /mnt/Data failed: No such file or directory

Is there a command that allows listing the shares offered by a server?

Re: [Announce] wizard-mounter for fremantle
 

If you receive no error from the command line, than the share is mounted correctly. You can verify it by running a df -h.
The command you are using is the same that use wizard-mounter, it's very strange if you have entered the same parameter in wizard-mouter and it fails.

P.S. : have you checked the samba radio-button ?

Re: [Announce] wizard-mounter for fremantle
 

Syntax for telnet is "telnet ip port" separated by spaces on both OSs.

"Permission denied" is a (heh) permission denied error. Your username or password is wrong or the user you specified has no access rights for that resource (did you add the user to the share?). On Windows, correct user/pass but no permission still mounts but you can't access the mounted drive or folder.

And finally, the fact that the Windows machine responds to the request (failure is a perfectly good response) leads me to believe that ports are correctly forwarded and WM is working fine.

It's probably the server. Most likely, you need to login before accessing any resources, which is AFAIK not possible with N900 at this time.

Listings on Windows are done via NET VIEW.

net view \\192.168.2.110

I think the Debian equivalent is smbclient -L hostname. Don't think it's on the device though.

Re: [Announce] wizard-mounter for fremantle
 

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

Re: [Announce] wizard-mounter for fremantle
 

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.

Re: [Announce] wizard-mounter for fremantle
 

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.

Re: [Announce] wizard-mounter for fremantle
 

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

Re: [Announce] wizard-mounter for fremantle
 

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

Re: [Announce] wizard-mounter for fremantle
 

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.

Re: [Announce] wizard-mounter for fremantle
 

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

Re: [Announce] wizard-mounter for fremantle
 

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!

Re: [Announce] wizard-mounter for fremantle
 

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?

Re: [Announce] wizard-mounter for fremantle
 

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.

Re: [Announce] wizard-mounter for fremantle
 

Bug found:
-> If the profile name has a period in it eg "Home samba 3.x", then wm has issues with displaying full name. Using that profile is impossible.
Work around: Renamed the file from the command line and replaced "." with "-" and we're back in business.

Are you looking for the first period from the beginning of the profile file name anywhere? Change the code to look reverse from the end of the file.
That should fix this.

Re: [Announce] wizard-mounter for fremantle
 

Can anyone suggest the manual command equivalent to how WM connects via nfs?

Thanks

Re: [Announce] wizard-mounter for fremantle
 

Oh, probably a space or a dot somewhere, making the module connect to localhost. On NT, \\. is local. Not sure what \\ does.

Wait, I can just try :) Spaces in the name on NT yield an error.

Anyway, It's unlikely to be another PC, it probably tried local. Don't know how to open a port and test. Maybe netcat is ported?

Re: [Announce] wizard-mounter for fremantle
 

@uvatbc: thanks to report I will fix it asap

@Crashdot: The previous command line to mount samba/cifs share is exactly the same that wizard-mounter use, so I will bet the problems remain in the parameters.

BTW for mounting NFS by command line type:
mount -t nfs REMOTEIP:/SHARENAME /mnt/

Please keep in mind that in order to mount nfs you need to start the portmap service.

Re: [Announce] wizard-mounter for fremantle
 

I just found wizard mounter today, awesome app, worked first time out of box!

Thanks,
Fred

Re: [Announce] wizard-mounter for fremantle
 

Hello,
first of all sorry for my poor english, i am french (nobody is perfect ;-))
but i have the same problem than Crashdot.

So i look for the command line in your source code and i found this:
"/usr/bin/sudo /bin/mount -tcifs \"//%s/%s\" \"%s\" -ouser=\"%s\",pass=\"%s\",uid=%d,gid=%d,ip=%s\n"

so i check this command on my nokia N9OO and it works.... very strange because i have the "connection refused" error with WM.

In fact it works also with ",direct" add at the end of the command line.

But when i look in "/media/Remote_Filesystems/" i only found my directory "PUBLIC" (the one created by the command line) and no directory with a name such as (xxxx@ip_adress").
In your "mount" function you create the directory before the call to the mount command.
So maybe our problem occurs before, but i dont know for which cases you answer "connection refused".

my parameters are :
Server: 192.168.0.5
Remote: public
User: myusername
Password: mypassword

And believe me i tried so many times that i cant each time do a case sensitive mistake.

I hope you will find what's wrong with us, because i can only use your application to do the unmount (and it works). And i would like to mount with it.

Thank you for you great job,
sbernada.

Re: [Announce] wizard-mounter for fremantle
 

Perhaps we could get to the bottom of this faster if WM would agree to log all command lines, as executed, to a file so we can spot differences?

Re: [Announce] wizard-mounter for fremantle
 

get some problems after installing wizard mounter and "apt-get install kernel-module-nls-utf8 kernel-module-ntfs samba-common nfs-common"

when I want to remove it again I get the following error message:

Errors were encountered while processing:
samba-common
E: Sub-process /usr/bin/dpkg returned an error code (1)

What does it mean, and how can I remove all changes I have made when installing packages from above?

Thank you!

Re: [Announce] wizard-mounter for fremantle
 

/var/lib/dpkg/info # rm samba-common.postrm
/var/lib/dpkg/info # apt-get remove samba-common

Re: [Announce] wizard-mounter for fremantle
 

I have the folder sharing working for windows 7, however is there any way to access the folders shared through windows media player the same way the inbuilt player accesses them?