NAS shows up as media device?

Ok disabled firewall rebooted and no change. NAS still showing up as media device and not as computer.

scott potterton said:

Ok disabled firewall rebooted and no change. NAS still showing up as media device and not as computer.

Well, ok. Better put the fw back on.

I am sorry I have to go now, because I only have less than 5 hrs sleep left.

I'll check back tomorrow, and jump back in if it's not solved by then.

Good night and good luck.

Thanks for all your help so far!!!

TheSchaft said:

Alrighty then! Back to see if we can get this sucker solved.

I downloaded a copy of the ANAS Model 350 User's Manual, so we can talk from the same sheet of music, assuming that is what you have.


From looking in the manual, you should be able to map the drive as \\airnas, if you have it in the default configuration.

There's a configure set of pages at \\airnas\Configure to do some configure stuff.

It is a samba server, so maybe some other forlks can chime in.

I also found the following. If you feel comfortable checking the firewall policies, you might want to look into this:


"...the problem of accessing folders shared on an NAS adaptor involves the level of authentication that Windows 7, by default, uses. It's default is to use NTLMv2 for authentication, which I believe isn't supported in either Mac OSX or Linux yet. A second problem is the Minimum Session Security for NTVLM SSP based Clients, which in Windows 7 is "require 128 bit". To resolve these issues you need to:

1. In Windows 7, open the Control Panel
2. Switch to "Classic" view
3. Double-click Administration Tools
4. Double-click Local Security Policy
5. Or Secpol.msc
6. Expand "Local Policies" and select "Security Options"
7. Alternate : Type secpol.msc to get editor up then
8. Locate "Network Security: LAN Manager Authentication Level" in the list and double-click it.
9. Change the setting from "Send NTMLv2 response only" to "Send LM & NTLM - use NTLMv2 session if negotiated"
10. Network Security: Minimum session security for NTLM SSP Based (including secure RPC) Clients
11. Change the setting from "require 128 bit" to unchecked (No Minimum)
12. Click OK

I firstly tried just changing the item '9' on it's own and got an RPC Error message saying I didn't have access to the network resourse. After then changing item '11' I was, for the 1st time, able to access the folders on my Addonics NAS Share.

After changing these Policies in the Local Security Policy Editor it's not necessary to reboot your system for them to take effect. Also you need to have Administrator Privilages to be able to make these changes to your system."

I cannot attest to whether this will work, but you can look at the policies and see how they are currently set. (Keep track of any changes you try, of course.)

When I see you're back on line, we can chat some more. I'll be away for about 2 hours (until around 6PM Central time).

Even in case it won't work for him, rep well deserved.

Brilliant approach!

Edit: I knew you were an asset to this forum from the start.
Nice to find out I was right.

TheSchaft said:

Just trying to help, same as all the folks here. :)
This problem has been bugging me, so I took a little time to sniff around.
Hope you have some samba expertise - one of my many missing areas...

You should learn to take a compliment.

TheSchaft said:

From looking at the documentation, I suspect that it is a sharing problem. I don't think it will show the folders that are not shared under normal Windows 7 folder options settings. That may be something else to look at.

Weird thing is that it worked ok for a little while, he said.

I had my router disappearing from network overview when I installed zonealarm,
that's why I asked if he could disable the firewall, but that didn't help either.

To be honest, I know absolutely nothing of the consumer NAS disks out there.
So if the problem is a setting in the NAS configuration, I am useless for the OP.
Don't have a NAS at home to figure it out.
I use a server with multiple disks.

Greetz

Good night.

Haven't seen the OP again by the way.