A300 and NFS on Windows Home Server

[torch]

Looking for some guidance. I was operating an A200 on my network accessing NFS shares located on Windows Home Server 2011. All worked with out issue. Decided to upgrade to the A300. I configured the device identical to the A200 and now when I attempt to access the files from the A300 I'm prompted for a signon and password. Tried different configurations, installed the NMT apps, etc.... No luck. I put the A200 back on line and can access the shares without problem (no signon/password required). I did notice one difference, when I put the A200 online the device is displayed in the browser under Media Players. However, the A300 is not recognized as a Media Player on the network. I believe because the A300 is not recognized as a media player on the network I can't provide the NFS share the access permissions to the device, as such without the permissions I'm prompted for signon/password. How do I get the A300 to display as a media player on the network? Thanks

[halfelite]

No, first what is your nfs permissions, when you setup NFS you either do by IP address or all allowed. Is it set to all or does the a300 have same ip address?

[torch]

(05-16-2012 02:28 AM)halfelite Wrote:  No, first what is your nfs permissions, when you setup NFS you either do by IP address or all allowed. Is it set to all or does the a300 have same ip address?

I tried the "all allowed" and now just tried the IP address. A300 still asked for signon/pw. Some additional info, the A300 is hardwired to the network. assigned a static IP address, and I can successfully ping the A300 from the Windows Server. When i start the samba service on the A300 the A300 is displayed as a computer in the network browser when I start the UPnP service the A300 shows has a media streamer in the network browser. So there is some connectivity between the A300 and the Windows Server. Thanks

[halfelite]

are you browsing to the share are adding it manually?

[torch]

(05-16-2012 04:43 AM)halfelite Wrote:  are you browsing to the share are adding it manually?

I tried both methods. No luck. Thanks

[torch]

(05-16-2012 02:43 PM)torch Wrote:  

(05-16-2012 04:43 AM)halfelite Wrote:  are you browsing to the share are adding it manually?

I tried both methods. No luck. Thanks

Just an update for anyone interested. As I stated previously my A200 worked flawlessly with the NFS shares on WHS2011 but did not work on the A300. After some trial and error I discovered the problem was due to the length of the NFS share name. On the A200 my NFS share name was "Network Video Library" it worked but not on the A300. I tried a shorter share name "netvidlib" and got past the signon/pw prompt but when I browsed to the share i received a the msg "No content found". Some progress but still not a success, so I shortened the share name to "netlib". That did the trick, my NFS share was recognized and fully accessible. Turns out that the A300 may have introduced some quirkiness in resolving the share name. Any lower case share name between 1 and 6 characters works. If you go to 7 or more lower cases letters I got the "no content" msg (completely unexplainable). If I introduced caps, spaces, or special characters I got the prompt for signon/pw. I'm not sure if this is widely known or if it's just my setup, but maybe this can help someone else. I can say this - while running SAMBA my mkv bluray rips with HD sound and video were not playable, with NFS/IP on a 10/100 nic, I achieve perfect play back.

[accident]

You should post your findings in the 300 bug section, especially since it was working on the 200.