Dase

I'm passing this info along to hopefully save someone else the hours of googling it took me to figure this out. NFS support in Windows is very poorly documented. First of all, you need Windows 7 Ultimate for this to work. Lesser versions of Windows 7 don't include NFS support. My main roadblock was that every share I mapped resulted in "Access denied" errors. It turns out you need an obscure registry hack to allow Windows to authenticate properly. Here's what you need to do. 1. In Control Panel, open Programs and Features. 2. Click "Turn Windows features on or off." 3. Enable "Services for NFS" and click OK. Wait for it to install. 4. Start the registry editor. 5. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default. 6. Create two DWORD values: AnonymousUid and AnonymousGid. They both need to be set to the number zero (0). 7. Reboot. 8. Activate NFS in unRAID 5 (Settings tab) and on the Main tab click the shares you want to export. Set "Export" to Yes. I used Public security. I had to reboot my unRAID server for NFS shares to work after enabling NFS support the first time. 8. In Windows 7, map your drives with the "Map network drive" feature by using this format for the path: tower:/mnt/user/Video You can also do this from the command line: mount tower:/mnt/user/Video z: Note that for NFS shares you have to provide the full unRAID folder path, not just the final shared folder. Alas, after doing all this work I found out that my NFS transfers in Windows topped out at about 30 MB/sec. I get up to 120 MB/sec in Samba. Oh well.

It looks fine for me on the beta build (11.0.696.57 beta).

I had to stop unmenu from installing the PHP package for my 5.0 upgrade. The unraid web UI was all garbled with it active.

Are you specifying the IP addresses you want to access the NFS shares? I have this on the shares page at the top in the "Disk shares (NFS):" field: 192.168.0.1(rw) 192.168.0.2(rw) You have to do the same thing in each share's "Export (NFS):" field too. Here's the wiki topic on this: http://www.lime-technology.com/wiki/index.php?title=FAQ#How_do_I_configure_NFS_mounts.3F

That's a good question. I hope the kernel would consistently assign USB posts based on the motherboard's USB port order rather than power-on order, but I don't know for sure. Messages appear in the syslog as devices connect so you could see how that's being handled. From what I can tell, p910nd doesn't have any clue what it's connected to, other than the USB post.

It should. You can run an instance for each printer and each instance has its own port. The first is port 9100, the second port 9101, etc. Since the print drivers will be pointing to different ports there shouldn't be any conflicts.

Nice, I got this working too. Thanks for letting us in on the p910nd software! I'll attach my compiled copy. You don't have to recompile the kernel any more to enable USB printer support, since newer unRAID versions seem to already have this enabled. ----- Edit added 9/4/2015--Support for unRAID 6.x I've recompiled and attached a p910nd version that works for unRAID 6.x. unzip the file and chmod +x p910nd. The commandline stays the same, p910nd -f /dev/usb/lp0 -b. ----- To get it working, do the following. 1. Put the attached p910nd file somewhere in your flash drive's /boot folder. 2. Add two lines to /boot/config/go so it runs automatically when you boot: 1: mkdir /var/lock/subsys 2: /boot/</yourpath>/p910nd -f /dev/usblp0 -b 3. Attach your printer and reboot or manually run p910nd. Check /var/log/syslog and make sure the kernel saw your printer and that p910nd isn't showing any errors. I had to manually create the /var/lock/subsys/ folder before it would load error-free. 4. Go to www.samsung.com and download the driver for the printer. If you're using Windows, you must download the actual GDI driver, not the universal driver. 5. Install the printer driver. In Windows you'll end up with an ML-1710 printer in your Printers folder that's connected to LPT1, which won't work. 6. Click Properties on the ML-1710 printer and go to the Ports tab. Click the Add Port button. 7. Select Standard TCP/IP port and click the New Port button. 8. In the Add Port wizard, put in your unraid name or IP address. Give the port a name. Click next. The wizard will freeze for a bit. 9. On the Additional Port Information Required page, click Custom and then the Settings button. Make sure the info is correct. The port should be 9100 and the protocol should be raw. Click OK. 10. Click Next and Finish to finish the wizard. Close the Printer Ports dialog. 11. Your new port should be selected in the Printer's port list. Click the Apply button, go to the General tab and print a test page! I imagine this process would work for any printer that has a driver with raw printing and custom port support. Good luck. p910nd.zip p910nd-unRAID61.zip

I've been searching and trying to resolve this for a couple hours now. I'm sure I'm missing something simple, but here's the problem. With unRAID simple security My unRAID shares mounted in Windows 7 work fine. I can add/delete files/folders no problem. In Ubuntu, however, those same shares are read-only no matter how I mount them and I have to su to add/change/delete files/folders. What's the proper way to mount unRaid shares in Linux? I don't want to run apps that need to write to unRAID shares as su. Thanks.