ncpfs allows you to mount volumes of NetWare servers under Linux and to print to NetWare print queues and spool NetWare print queues to the Linux printing system.
| Tags | Filesystems |
|---|---|
| Licenses | GPL |
Recent releases


Changes: This release adds small bugfixes in pam_ncp_auth.


Changes: Small bugfixes were made to the build process and print tools, and all NDS-aware tools were extended to take the default name context from the configuration file.


Changes: Greatly enhandced pam authentication module and NDS support added to couple of utilities. Fixed compatibility with NDS keys generated by newer Novell Clients, and fixed kernel endianess issues on bigendian machines.
Islamic toolbar for watching Islamic TV channels, listen Islamic radio, Islamic Search engine and more..
- All comments
Recent commentsfile size limit
Please, tell me how to avoid fize size limit of 2Gb in ncpfs?
Will be lfs support added in further versions of ncpfs, like in smbfs?
Re: ncpmount: No such device in mount(2)
> ncpmount: No such device in
> mount(2)
> The same exact ncpmount command works on
> a different system configuration, so I
> know the target filesystem is valid. In
> my case I am beginning to suspect the
> kernel modifications that were done for
> optimizing to my notebook hardware. (the
> stock kernel seems to work)
I just had the same error message, and I solved it by compiling NCP file system ability into the kernel.
printing to NDS queues
The evil Netware adminstrators where I work recently deleted all the bindery print queues and left only NDS queues. Neither pqlist nor nprint seem to find them. Are they not "NDS aware" like ncpmount? Will they ever be?
Thanks.
pserver
This is a great project. ncpmount and nprint are working perfect! But when I try to start pserver I get the error
Could not attach to queue W: Unknown Server error (0x89EA)
What could be a reason for this? I am using a 4.2 Netware Server.
Re: ncpmount: No such device in mount(2)
>
> %
> % ncpmount: No such device in mount(2)
> %
>
>
> That error can appear if you are trying
> to mount a mountpoint on the filesystem
> without specifying the target filesystem
> you want to mount.
The same exact ncpmount command works on a different system configuration, so I know the target filesystem is valid. In my case I am beginning to suspect the kernel modifications that were done for optimizing to my notebook hardware. (the stock kernel seems to work)
About forums, I've found lots of Q&A about ncpfs and ipx over at http://www.linuxquestions.org (http://www.linuxquestions.org) so that's where I've been going lately for help and solace. ;-)