OK, I am on Xubuntu so no 'Connect to Places', but I do remember I could do this with the FTP option. (hence my original question of trying to mount it with curlftpfs)
I do not have /proc/fs/cifs/ so cannot perform the echo 0 > ... command (which I have tried before with success on Ubuntu) Because I get the 'Cannot allocate memory' error, it seems to me it is making contact but the error is a windows thing. Solutions in that link Alan supplied involved doing things on the Windows machine containing the share, obviously I can't do that if it is just a NAS drive. Thanks for the help so far! Jon On Sat, Feb 20, 2010 at 10:43:52AM +0000, Markie wrote: > I have a crunchbang machine here and i use this script to mount my Freecom > NAS drive; > > #!/bin/bash > # Script to mount network drive > echo 0 > /proc/fs/cifs/LinuxExtensionsEnabled > mount -t cifs //192.168.0.2/Shared ~/HomeShare -o username=curtis > > So I would say that this is something to do with lack of memory or swap > perhaps? Hows your memory settings? "free" works on this machine to give a > memory output > > Mark > > On 20 February 2010 10:26, Dan Fish <d...@fishms.org> wrote: > > > Jon, > > Any luck with mounting the NAS from the desktop from 'Places -> connect > > to server' then choosing 'FTP (with login)'? > > > > Regards > > Dan > > > > On Sat, 2010-02-20 at 00:50 +0000, Jon Reynolds wrote: > > > Thanks for the link, but I think I can't solve my problem like that as > > > this is a NAS drive, not another machine's share. > > > > > > So am still a bit dumbfounded. > > > > > > Thanks again > > > > > > Jon > > > > > > On Fri, Feb 19, 2010 at 04:00:00PM +0000, Alan Pope wrote: > > > > Hi, > > > > > > > > Googling for the error... > > > > > > > > On 19 February 2010 15:45, Jon Reynolds <maill...@jcrdevelopments.com> > > wrote: > > > > > ? ?j...@jonr-laptop:~$ sudo mount -t cifs > > > > > //192.168.0.3/PUBLIC/media/fnd/ > > > > > ? ?-o username=jonr > > > > > ? ?mount: Cannot allocate memory > > > > > > > > > > > > > > > http://linux.derkeiler.com/Newsgroups/comp.os.linux.networking/2006-10/msg00629.html > > > > > > > > "This is not a Linux problem, but the Windows machine is the one that > > is > > > > causing it and refusing to allow the mount. I found this by running > > tail > > > > on the messages file in one term and then running the command in > > another > > > > terminal window, then watching the tail command to see what errors were > > > > generated by the mount commmand." > > > > > > > > Lots more info at the above link.. > > > > > > > > Cheers, > > > > Al. > > > > > > > > -- > > > > ubuntu-uk@lists.ubuntu.com > > > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk > > > > https://wiki.ubuntu.com/UKTeam/ > > > > > > > > > > > -- > > ubuntu-uk@lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk > > https://wiki.ubuntu.com/UKTeam/ > > > -- > ubuntu-uk@lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk > https://wiki.ubuntu.com/UKTeam/ -- ubuntu-uk@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-uk https://wiki.ubuntu.com/UKTeam/
