Thank You for your reply. \\IP_Address\etc$ gives same error. CIFS is licensed and running. We have many shares on this and they are OK. Ping is fine as well. You got the point. I logged into the oncommand system manager but I don't see etc share created. But if inside oncommand system manager I go to configuration -> Protocol -> CIFS -> auditing, it says auditing enabled and log file is at /etc/log/adtlog.evt.
So how do I access that if etc share is not created on this filer?
Can you access any other share on that controller from your Windows 7 workstation? If no, then check the SMB signing security settings on your workstation and make sure that 'requiring signing (always)' is not set to 'enabled'
If you can access other shares, then make sure that this option is set (assuming you are an Admin on the controller) 'options wafl.nt_admin_priv_map_to_root on'
Vol0 where /etc resides is typically set to Unix security style so the above option will map your windows user to 'root' on the filer assuming that your windows user account is a member of the local Administrators group on the filer.
Yes, I can access other shares on the filer from my windows 7 pc. So I set "options wafl.nt_admin_priv_map_to_root on" on the filer as I am the admin. Still not able to access the C$ or etc$ on the filer. It says network not found. I cannot see C$ or etc$ in Shares from OnCommand system manager.
For my other filer, I am able to access \\Filer_Name\C$ from my PC and if I connect to my 2nd filer through OnCommand system manager, I can see C$ and etc$ shares at the path /vol/vol0 but I cannot see that in the affected filer?
I was never able to access etc share on this particular filer. On another file, I am able to access the etc share. So should I run the CIFS setup again? Will it affect my existing shares on the filer? There are production shares on the filer.