NASLite Network Attached Storage

Hi, new NASLite user here.

Everything related to my new NASLite-2CDD server seems to be working fine, except for the life of me, I can't get it to show up on the Windows network. I've got two disks that are mounted, and exported as RW. I can FTP to and from the disks. Telnet and HTTP works fine. SMB/CIFS is set for RW. Workgroup is named, server is named.

What am I missing?

Thanks,
Steve

Nevermind - I'd recently installed antivirus software (AVG) on all the Windows boxes and for some reason the the AVG firewall was blocking the NASLite server. Turning it off solved that problem. I don't need it anyway since I'm behind a hardware firewall. Still, it seems odd that the AVG firewall would block a NASLite server but not other Windows machines.

Steve

I use ZoneAlarm ... so am not experienced with the AVG firewall. But just like ZA ... you should be able to create a "trusted" IP for the NASLite server while re-enabling the firewall as before for everything else.

Turns out I'm not out of the woods yet. I was able to access the NASLite server for a short time after playing with my software firewall - now it's no-go again, but the symptoms are different. Now, the NASLite server is at least listed in Windows Networking (on every Windows machine), but any attempt to use it's resources results in messages explaining that the network path is unavailable or I don't have permission, etc. And I'm now convinced that it has nothing to do with the firewall issue, because even machines with no anti-virus or firewall installed (including one stripped down W2K box) can't access the NAS disks. It's as if the NASLite box is announcing it's presence to Windows networking, but no resources are shared. Weird.

Steve

Could be a domain versus workgroup issue; several issues along those lines with similar symptoms are documented on this forum. And/or also check that IP address assignment or conflicts is not an issue (as for example DHCP ranges versus fixed address assignment for NL server).

No domains involved.

And the other services (HTTP, Telnet, FTP) are working, indicating no IP address conflict, I think.

However, as a lark I just changed a couple of the Windows boxes from DHCP to fixed IPs, and boom, they are accessing the NASLite resources now.

I hesitate to say my problems are solved, but if this is all it takes, I'm happy. Don't quite understand why my brief research didn't turn up the same issue though...

Thanks,

Steve