Notices

No. It's too slow.

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 :/

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.

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

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.

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

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.

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?

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 ?

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.